Normally, this is not a good setup. Most users will not be aware of
the disconnected sessions and will not be able to reconnect to
them. So they could have the same application open in several
sessions, and can get errors when the same document is opened in
them.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting:
http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
"seth" <(E-Mail Removed)> wrote on 30 nov 2005 in
microsoft.public.win2000.termserv.clients:
> that's your decision if you want to allow that
>
> "PCstudyBug" <(E-Mail Removed)> wrote in
> message
> news:A396221E-690F-4F69-AF81-(E-Mail Removed)...
>> Is it bad to leave it as is...to allow them as many sessions as
>> they want?
>>
>> "seth" wrote:
>>
>>> on the terminal server, go to terminal services configuration
>>> in administrative tools
>>> on the left, click on server settings
>>> on the right, change 'restrict each user to one session' to
>>> yes
>>>
>>> "PCstudyBug" <(E-Mail Removed)> wrote in
>>> message
>>> news:CB9EC688-1643-46CB-96A5-(E-Mail Removed)...
>>> > When I go into Terminal Services Manager it lists all kinds
>>> > of disconnected
>>> > connections along with the active sessions. It's strange
>>> > because sometimes
>>> > it is the same username that is listed as disconnected 2
>>> > times. Wouldn't
>>> > that username pick up the other session from where they left
>>> > off? I mean,
>>> > wouldn't each username only be listed once? Each user only
>>> > uses one machine
>>> > (they never logon to another person's PC). Thanks for any
>>> > help!