ITGuyMN
asked on
RDP Client Diconnect Problems
We have 2 Windows 2000 Professional clients that are using the MS RDP client to connect and run a applicaion on a Windows 2003 Terminal Server. The applicaion launches in its own window and seems to run just fine. However, when the user closes the applicaion (from exit button in the applicaions menu or toolbar) the session stays open and leaves an empty sessioin window. If the client reconnects they get the same empty window. The only work around we have found is to set a serverside time out on the disconnected sessions so that they dont reopen a blank window when reconnecting.
Any ideas on how to fix this issue so the client can logoff the session correctly. I have citrix ICA applicaions running on the same server that close just the way they are supposed to when the user closes the applicaion. As well, I have seen this work with other RDP clients so I am sure it is a localized problem.
I have tried to delete and recreate the RDP session file with no change. Are there any other session settings in the registry that I might be missing?
Any help would be apprieciated.
Any ideas on how to fix this issue so the client can logoff the session correctly. I have citrix ICA applicaions running on the same server that close just the way they are supposed to when the user closes the applicaion. As well, I have seen this work with other RDP clients so I am sure it is a localized problem.
I have tried to delete and recreate the RDP session file with no change. Are there any other session settings in the registry that I might be missing?
Any help would be apprieciated.
ASKER
Unfortunately this is a 2003 member server in a NT4 domain so GPO’s are really not an option at this point. Is there a specific setting that provides for the session to close (logoff) when the user closes the applicaion that is running in this mode?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You could try setting the Terminal Server to force a program start on connection using GPOs:
User Policy:
Administrative Templates\Windows Components\Terminal Services Start a program on connection
Which sets these registry entries:
HKCU\SOFTWARE\Policies\Mic
HKCU\SOFTWARE\Policies\Mic
HKCU\SOFTWARE\Policies\Mic
Machine Policy:
Administrative Templates\Windows Components\Terminal Services Start a program on connection
Which sets these registry entries:
HKLM\SOFTWARE\Policies\Mic
HKLM\SOFTWARE\Policies\Mic
Cheers
JamesDS