Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Terminal Server

Status
Not open for further replies.

epunk

MIS
May 10, 2006
9
ES
Hi,

I'm setting up Terminal Server on a Win2003 Standard. I've setup the TS service then installed the applications to be available through TS sessions.

I've specified a user group to allow logon to the server.

On client sides, I've setup the TS Client to launch a specific application when launching the TS session. When the user logs on, it works fine, however, when closing the application, the TS session does not automatically closes. What I mean is that the application closes, but the TS session is still active, but with nothing on the screen.

Any suggestions why?
 
How exactly did you set this up? Via Group Policy on the terminal server or some other way? Would this work if sitting at the console?
I ask because the "launch on login" functionality and closing the app doesn't necessarily mean that the TS session will end, much like sitting at the console and closing the app wouldn't log you off. If you wanted to do something like that, you can script it, but not sure how you want to approach this.
 
To launch the program automatically upon client connection, on the client side, in the Programs tab, I clicked the "launch this program when connected" tab, with the path to the executable.

So when I launch the session, it automatically opens up the application and have access to nothing else but the program. However, I've seen it done before that when you close the app, it automatically clsoes the TS session, but I just have no clue how it's done.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top