PCM is designed not to connect via Console Connection, this is by design.
The development team have confirmed that when a command is provided via TPAM PCM, then the “Enable Console Connection?” setting is overridden and the console connection will not be used. This is by design. Therefore, this the “Enable Console Connection?” only applies to PSM, rather than PCM.
Engineering confirmed that if you run “mstsc” or “mstsc /admin” (outside of TPAM) and specify a program within the mstsc options (for example, using Microsoft Remote Desktop Manager > Connection Settings tab). We found that if you use “Connect to console” connection with an application specified, it will be ignored and instead a full desktop is launched, when the user session limit is reached.
The issue found in the 2.4 Release Notes known issues, is not a TPAM issue, but it’s a Microsoft limitation and cannot be addressed in TPAM.
This Microsoft limitation is that, with two existing RDP sessions (non-console) you cannot connect to the third console session ID 0 with an application specified (equivalent to PCM).
In other words, with Microsoft RDP:
- RDP Session 1 as User1
- RDP Session 2 as User2
- A console RDP session 0 will start in full screen and WILL NOT launch tsadmin.exe
If a PCM session connects at this point, it will try and launch as a RDP Session ID3 and get the Microsoft licence warning.
With TPAM, PCM always connects as a RDP session (ID >1) and not the console (ID 0), regardless of the console flag, due to this limitation above. In other words, a TPAM design decision has been made to err on the side of caution and security. We wouldn't want TPAM to try and connect to the console, fail due to existing sessions, and launch a full desktop when the user has specified a PCM only command.