G
Guest
We are migrating from terminal server 2000 to 2003 (two separate servers).
Our PC's are running either win2K SP4 or XP SP2.
We are using Terminal server client to launch the applications on both
servers.
When we exit the application on the 2000 server the session terminates and
the window closes, returning the user back to the local desktop.
When we exit the application on the 2003 server the session disconnects and
we are left with a title bar and a blank screen. The only way out of the
session is to click the X to close the window. We then receive a popup box
labeled " Disconnect Windows Session" informing us that our program will
continue to run until we re-connect. When we try to re-connect the
connection hangs and must be cleared on the server.
My question... How can I recreate the windows 2000 behavior on our winows
2003 server?
Thanks
Tim Marvin
Our PC's are running either win2K SP4 or XP SP2.
We are using Terminal server client to launch the applications on both
servers.
When we exit the application on the 2000 server the session terminates and
the window closes, returning the user back to the local desktop.
When we exit the application on the 2003 server the session disconnects and
we are left with a title bar and a blank screen. The only way out of the
session is to click the X to close the window. We then receive a popup box
labeled " Disconnect Windows Session" informing us that our program will
continue to run until we re-connect. When we try to re-connect the
connection hangs and must be cleared on the server.
My question... How can I recreate the windows 2000 behavior on our winows
2003 server?
Thanks
Tim Marvin