one user, one session

  • Thread starter Thread starter Harry Hudini
  • Start date Start date
H

Harry Hudini

Is it possible to setup TS 2000 so that users DONT end up with loads of
sessions running ?

We used to have the server setup so that peoples sessions where closed very
quickly. We recently changed it so that, if people where disconnected and
then logged back on, their session would be left running for them. Hoever,
all that seems to have happened is that people log back on to a brand new
session, and the old session is left running. This means that people end up
with three or more sessions during the day.

I would like it so that if user A logs back on after being disconnected, he
gets reconnected to the running session for user A and doesnt get a brand
new session.

Is this possible ? its doing my head in.

Olly

--
________________________________________________
ADSSupport.net
http://www.adssupport.net
Dedicated free Active Directory ServicesT support

email: oliver.marshall@[email protected]
 
Are they logging off their session or disconnecting from
their session. Logging off their session should do the
trick and you can set up parameters to disconnect a
session if it is idle more than X minutes or hours.

Calvin
 
its not purposeful disconnections or logoffs i worry about, its ones that
come from server issues or leased line issues. These are treated like a
disconnect.

Either way though, if a session exists associated with their name, i want
them to log on to that session and NOT create a new one.

Can this be done ?
 
Heey, try this link:

terminal.servebeer.com/php/check_logon_and_connect.php

-M
 
If a user "disconnects" when they log back in they are
supposed to re-establish a connection with their existing
session if they have one. If this is not happening you
have a configuration problem somewhere. I just tested that
very scenario multiple times including pulling my network
connection and that is how it worked every time. If the
user logs off a new session starts when they log back in.
 
Admittedly, this should work, but not always. I've seen
where some people are disconnected, but their session
doesn't go into the disconnected state quick enough. The
person reconnects to the server and logs in again before
the server has a chance to move the session into the
disconnected state.

-M
 
Either in you TS-specific logon script, or in C:\winnt\system32
\usrlogon.cmd, or after this script, through a registry entry.
See details in the KB article below.
Note: this techniques does not work if you have multiple Terminal
Servers in a farm (then you will have to modify the script to
check for all connections in the farm).

195461 - How to Set Up a Logon Script Only for Terminal Server
Users
http://support.microsoft.com/?kbid=195461
 
Back
Top