My setup is this:
Windows 7 x64 SP1 client
Windows Server 2012 with RDWA, RDGW roles
Windows Server 2012 with RDCB role
Windows Server 2012 with RDSH role
Client is separated from the servers by a firewall, TCP 443 & UDP 3391 are permitted to the RDWA/RDGW server.
Client is able to connect to the RDSH via RDGW (RDGW auth using smartcard, RDSH auth using AD user/pass).
It makes no difference if I launch a RemoteApp or use mstsc.exe & set up the RDGW settings manually - when I log off the remote session the window goes black but does not disappear.
If I click the X button twice the window disappears, but:
- the session remains on the RDSH in the disconnected state
- the mstsc.exe process is still running (with 3 threads constantly using a trickle of CPU time)
- until the mstsc.exe process is killed, I can no longer connect from the client to the same collection/RDSH
If I skip the RDGW and connect directly to the RDSH (opening up TCP 3389 to test), authenticating using the user/pass, I donot get the problem.
Is this a known issue with RDGW connections on WS2012?