RDP Slow Disconnect with Single Apllication
Posted on 2007-11-16
First post. I stumbled from being a "Power User" to being a Network Admin for about a year now. I work on my own, and have had to learn most everything on my own as well. I've searched and tweaked and tinkered, but I can't get the RDC to close immediately on remote computers.
The single application that opens on Windows Server 2003 is a log in to an EMR (Electrronic Medical Record) located on another database server. I disconnected and relogged in immediately through RDC. If the just the RDC screen is closed, I've been able to log back in and still be logged into the application! This is not good for security. If the application is closed, then the screen hangs there for a good bit, until finally "Saving your settings....." When logged on as just a user, without the single application, it closes immediately.
I know it's possible to close the application and close the RDC screen, and sessions will end, but I need to make it completely and totally idiot proof for the ....ummm ..........physicians ......the technological gap .....is ......let's say .................very large!
Separate Terminal Services profile folders from Roaming profile folders.
Open SINGLE APPLICATION at start is set in User Profiles, (not RDP although I've tried that too)
End Session 1 minute. (I've tested this at different settings)
END DISCONNECTED SESSION is selected both in User Profile and TS Configuration.
I don't know if this is something on the end user computer, or on the Windows Server 2003? Cache issues? Do I even need to give a TS profile folder for a single application opening?