If the connection to a Windows server is not occurring as intended; please test the results when TPAM is not in use. For example, if testing outside of TPAM (with regular RDP / mstsc connection) has the same effect as connecting with TPAM, this is most likely a Windows configuration issue, and not a TPAM configuration issue.
1. On PSM "Details" tab, "Enable Console Connections" should be disabled if you wish to have more than one TPAM user connect as the same Windows account.
From gpedit.msc: Expand "Computer Configuration | Administrative Templates | Windows Components | Remote Desktop Services | Remote Desktop Session Host | Connections".
2. Review the registry setting for "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\fSingleSessionPerUser". If this is set to 0x1; then each user will only be allowed a single session.
If the fSingleSessionPerUser value does not exist, create the DWORD value 'fSingleSessionPerUser'
Open the fSingleSessionPerUser value. The possible values are:
0x0 Allow multiple sessions per user
0x1 Force each user to a single session
Quest software does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry”