2003 Terminal Server Question

[BridgeRE]

We fire off an app (in the users environment in their profile), upon login to our Terminal pool when they exit the program it used to disconnect and typically reset their session. Now since I demoted these DC Terminal Servers to member servers, after clicking YES to exiting the program, it just freezes and you have to click the X for the Terminal window to close and they are locked out until the reset happens after 1 minute. What would be the reason? and can I fix it?

Thanks

 

[AIXilliterate]

I think I am doing a simpler version of what you are. We had a peer-to-peer network and recently upgraded. Idealy we would have all thin clients RDPing into the server but to save money we didn't replace the PCs that were still functioning fairly well - but I still wanted them to act like thin clients. I set the Windows XP Pro machines to have two logins - an Administrator and an User. I then wrote a batch that is in the startup file of the user's login that looks like this:

r:\staff.rdp
shutdown /l

where 'r' is the local drive and 'staff.rdp' is the RDP session with settings saved (such as removing the connection bar and using full screen under the display tab). Windows XP waits until the first line has completed and stopped running before it continues to the next line. Windows 98 doesn't. Anywho, 'shutdown /l' logs the local user off after the RDP session has logged off. This takes the user back to the Windows XP login screen.