For the past 3-4 years, we've had users with RDP shortcuts set up to point to a terminal server, either via the use of MSTSC, with the "Start the following program on connection" or via a bookmark using our Sonicwall SSLVPN 2000 device. (which uses the mstsc program as an underlying script/base program).
When users launch, the RDP session connects to one of our terminal servers, and launches only that particular program. Users do not see the Start Menu, desktop, taskbar, etc. (see image 1) When the user would exit the program, the RDP session would log itself out ... sometimes within seconds, sometimes within a minute or two.
As of last week, this auto logoff process has just stopped working. The RDP window just hangs there, with a blank blue or gray background screen, and never closes. If the user closes the window, it leaves behind a "disconnected" session on the terminal server. (see attached image #2)
Often, users need to log back in, and they go right back into that "disconnected" session (this is designed on purpose, as users often simply get disconnected and need to reconnect into their work).
I believe this stopped working properly when there was a power outage last Wednesday and many servers went through an ungraceful shutdown. I've rebooted the terminal servers, and domain controllers and have not had any luck. 2008R2 supposedly has some process called syswow64, but that is not applicable to 2003. Group Policy has not changed. I have not installed any Windows Updates either, since that power outage, nor really for a few weeks before.
Any help would be appreciated.