Reconnect to an existing session

  • Thread starter Thread starter dav
  • Start date Start date
D

dav

Guest
Hi all,

I would like to set up Window Server 2003 to basically act like Windows XP.

When I connect to the server via remote desktop it creates a new session on
the server, now if I go to a different machine and connect again instead of
disconnecting the other remote user and logging into that session it creates
an entirely new session.

I would rather it handle remote connections the same way XP does.

Please help!
Dav
 
Re: Reconnect to an existing session

Then you'll have to configure the server to allow only a single
session per user. Thats actually the default, if I'm not mistaken.
You can find this setting in Terminal Services Configuration or in
a Group Policy:

Computer Configuration - Administrative templates - Windows
Components - Terminal Services
"Restrict Terminal Services Users to a single remote session"
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?ZGF2?= <dav@discussions.microsoft.com> wrote on 12 aug
2008 in microsoft.public.windows.terminal_services:

> Hi all,
>
> I would like to set up Window Server 2003 to basically act like
> Windows XP.
>
> When I connect to the server via remote desktop it creates a new
> session on the server, now if I go to a different machine and
> connect again instead of disconnecting the other remote user and
> logging into that session it creates an entirely new session.
>
> I would rather it handle remote connections the same way XP
> does.
>
> Please help!
> Dav
 
Re: Reconnect to an existing session

"dav" <dav@discussions.microsoft.com> wrote in message
news:CF446E73-3992-48CB-9DFB-D541EBFBF596@microsoft.com...
> Hi all,
>
> I would like to set up Window Server 2003 to basically act like Windows
> XP.
>
> When I connect to the server via remote desktop it creates a new session
> on
> the server, now if I go to a different machine and connect again instead
> of
> disconnecting the other remote user and logging into that session it
> creates
> an entirely new session.
>
> I would rather it handle remote connections the same way XP does.
>
> Please help!
> Dav


For Windows Server 2003, set the Restrict each user to one session option to
Yes in Terminal Services Configuration. Alternatively, set the Restrict
Terminal Services users to a single remote session group policy to Enabled.

Rob
 
Re: Reconnect to an existing session

Forgive me if I am wrong, but does this setting not restrict each user to
their own unique session?

Last time I tried this I am sure it let each user connected have a single
session, but if 5 users connected that means 5 sessions. I just want one
session shared between everyone who connects.

Sorry if I am not explaining this very well.

Dav

"Rob Leitman [MSFT]" wrote:

> "dav" <dav@discussions.microsoft.com> wrote in message
> news:CF446E73-3992-48CB-9DFB-D541EBFBF596@microsoft.com...
> > Hi all,
> >
> > I would like to set up Window Server 2003 to basically act like Windows
> > XP.
> >
> > When I connect to the server via remote desktop it creates a new session
> > on
> > the server, now if I go to a different machine and connect again instead
> > of
> > disconnecting the other remote user and logging into that session it
> > creates
> > an entirely new session.
> >
> > I would rather it handle remote connections the same way XP does.
> >
> > Please help!
> > Dav
>
>
> For Windows Server 2003, set the Restrict each user to one session option to
> Yes in Terminal Services Configuration. Alternatively, set the Restrict
> Terminal Services users to a single remote session group policy to Enabled.
>
> Rob
>
>
 
Re: Reconnect to an existing session

That's not possible, Dav. And neiher is it on XP.
You could use a single generic user account for everyone, but they
would still each have their own session, or only one at a time
could have the session.

What is it these users are supposed to do in this shared session?
Chat with each other? In your idea of this scenario, do they all
have their individual control over mouse and keyboard, or are
numerous people simultaneously trying to control the single shared
session?
Maybe if you explain what you would like your users to be able to
do, we can find a solution.


_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___


=?Utf-8?B?ZGF2?= <dav@discussions.microsoft.com> wrote on 13 aug
2008 in microsoft.public.windows.terminal_services:

> Forgive me if I am wrong, but does this setting not restrict
> each user to their own unique session?
>
> Last time I tried this I am sure it let each user connected have
> a single session, but if 5 users connected that means 5
> sessions. I just want one session shared between everyone who
> connects.
>
> Sorry if I am not explaining this very well.
>
> Dav
>
> "Rob Leitman [MSFT]" wrote:
>
>> "dav" <dav@discussions.microsoft.com> wrote in message
>> news:CF446E73-3992-48CB-9DFB-D541EBFBF596@microsoft.com...
>> > Hi all,
>> >
>> > I would like to set up Window Server 2003 to basically act
>> > like Windows XP.
>> >
>> > When I connect to the server via remote desktop it creates a
>> > new session on
>> > the server, now if I go to a different machine and connect
>> > again instead of
>> > disconnecting the other remote user and logging into that
>> > session it creates
>> > an entirely new session.
>> >
>> > I would rather it handle remote connections the same way XP
>> > does.
>> >
>> > Please help!
>> > Dav
>>
>>
>> For Windows Server 2003, set the Restrict each user to one
>> session option to Yes in Terminal Services Configuration.
>> Alternatively, set the Restrict Terminal Services users to a
>> single remote session group policy to Enabled.
>>
>> Rob
 
Re: Reconnect to an existing session

Thanks for the speedy reply,

I basically want it how I explained in the first post, so that when a user
logs on the previous user gets logged off. When I look in Task Manager ->
Users tab I only want to see one user listed regardless of how many user have
logged on / off.

Their is only the Administrator account on the machine, but if 5 users
connect to it via remote desktop and I look in Task Manager -> Users tab I
see 5 sessions. I would just prefer it to let users share the account one at
a time.

So if I log on now, then Joe Bloggs logs on after me, I get logged off and
Joe Bloggs controls the session I once had. Then if I log back on, Joe Bloggs
gets logged off and I regain control of the session.

Thanks
Dav

"Vera Noest [MVP]" wrote:

> That's not possible, Dav. And neiher is it on XP.
> You could use a single generic user account for everyone, but they
> would still each have their own session, or only one at a time
> could have the session.
>
> What is it these users are supposed to do in this shared session?
> Chat with each other? In your idea of this scenario, do they all
> have their individual control over mouse and keyboard, or are
> numerous people simultaneously trying to control the single shared
> session?
> Maybe if you explain what you would like your users to be able to
> do, we can find a solution.
>
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
>
> =?Utf-8?B?ZGF2?= <dav@discussions.microsoft.com> wrote on 13 aug
> 2008 in microsoft.public.windows.terminal_services:
>
> > Forgive me if I am wrong, but does this setting not restrict
> > each user to their own unique session?
> >
> > Last time I tried this I am sure it let each user connected have
> > a single session, but if 5 users connected that means 5
> > sessions. I just want one session shared between everyone who
> > connects.
> >
> > Sorry if I am not explaining this very well.
> >
> > Dav
> >
> > "Rob Leitman [MSFT]" wrote:
> >
> >> "dav" <dav@discussions.microsoft.com> wrote in message
> >> news:CF446E73-3992-48CB-9DFB-D541EBFBF596@microsoft.com...
> >> > Hi all,
> >> >
> >> > I would like to set up Window Server 2003 to basically act
> >> > like Windows XP.
> >> >
> >> > When I connect to the server via remote desktop it creates a
> >> > new session on
> >> > the server, now if I go to a different machine and connect
> >> > again instead of
> >> > disconnecting the other remote user and logging into that
> >> > session it creates
> >> > an entirely new session.
> >> >
> >> > I would rather it handle remote connections the same way XP
> >> > does.
> >> >
> >> > Please help!
> >> > Dav
> >>
> >>
> >> For Windows Server 2003, set the Restrict each user to one
> >> session option to Yes in Terminal Services Configuration.
> >> Alternatively, set the Restrict Terminal Services users to a
> >> single remote session group policy to Enabled.
> >>
> >> Rob
>
 
Re: Reconnect to an existing session

OK, assuming that privacy is of no concern, a combination of a
generic user account and a single session per user will do this.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?ZGF2?= <dav@discussions.microsoft.com> wrote on 13 aug
2008 in microsoft.public.windows.terminal_services:

> Thanks for the speedy reply,
>
> I basically want it how I explained in the first post, so that
> when a user logs on the previous user gets logged off. When I
> look in Task Manager -> Users tab I only want to see one user
> listed regardless of how many user have logged on / off.
>
> Their is only the Administrator account on the machine, but if 5
> users connect to it via remote desktop and I look in Task
> Manager -> Users tab I see 5 sessions. I would just prefer it to
> let users share the account one at a time.
>
> So if I log on now, then Joe Bloggs logs on after me, I get
> logged off and Joe Bloggs controls the session I once had. Then
> if I log back on, Joe Bloggs gets logged off and I regain
> control of the session.
>
> Thanks
> Dav
>
> "Vera Noest [MVP]" wrote:
>
>> That's not possible, Dav. And neiher is it on XP.
>> You could use a single generic user account for everyone, but
>> they would still each have their own session, or only one at a
>> time could have the session.
>>
>> What is it these users are supposed to do in this shared
>> session? Chat with each other? In your idea of this scenario,
>> do they all have their individual control over mouse and
>> keyboard, or are numerous people simultaneously trying to
>> control the single shared session?
>> Maybe if you explain what you would like your users to be able
>> to do, we can find a solution.
>>
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>>
>> =?Utf-8?B?ZGF2?= <dav@discussions.microsoft.com> wrote on 13
>> aug 2008 in microsoft.public.windows.terminal_services:
>>
>> > Forgive me if I am wrong, but does this setting not restrict
>> > each user to their own unique session?
>> >
>> > Last time I tried this I am sure it let each user connected
>> > have a single session, but if 5 users connected that means 5
>> > sessions. I just want one session shared between everyone who
>> > connects.
>> >
>> > Sorry if I am not explaining this very well.
>> >
>> > Dav
>> >
>> > "Rob Leitman [MSFT]" wrote:
>> >
>> >> "dav" <dav@discussions.microsoft.com> wrote in message
>> >> news:CF446E73-3992-48CB-9DFB-D541EBFBF596@microsoft.com...
>> >> > Hi all,
>> >> >
>> >> > I would like to set up Window Server 2003 to basically act
>> >> > like Windows XP.
>> >> >
>> >> > When I connect to the server via remote desktop it creates
>> >> > a new session on
>> >> > the server, now if I go to a different machine and connect
>> >> > again instead of
>> >> > disconnecting the other remote user and logging into that
>> >> > session it creates
>> >> > an entirely new session.
>> >> >
>> >> > I would rather it handle remote connections the same way
>> >> > XP does.
>> >> >
>> >> > Please help!
>> >> > Dav
>> >>
>> >>
>> >> For Windows Server 2003, set the Restrict each user to one
>> >> session option to Yes in Terminal Services Configuration.
>> >> Alternatively, set the Restrict Terminal Services users to a
>> >> single remote session group policy to Enabled.
>> >>
>> >> Rob
 
Re: Reconnect to an existing session

I'm sorry how is this achievable?

Do I need to change a setting in gpedit.msc?

Thanks
Dav

"Vera Noest [MVP]" wrote:

> OK, assuming that privacy is of no concern, a combination of a
> generic user account and a single session per user will do this.
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?ZGF2?= <dav@discussions.microsoft.com> wrote on 13 aug
> 2008 in microsoft.public.windows.terminal_services:
>
> > Thanks for the speedy reply,
> >
> > I basically want it how I explained in the first post, so that
> > when a user logs on the previous user gets logged off. When I
> > look in Task Manager -> Users tab I only want to see one user
> > listed regardless of how many user have logged on / off.
> >
> > Their is only the Administrator account on the machine, but if 5
> > users connect to it via remote desktop and I look in Task
> > Manager -> Users tab I see 5 sessions. I would just prefer it to
> > let users share the account one at a time.
> >
> > So if I log on now, then Joe Bloggs logs on after me, I get
> > logged off and Joe Bloggs controls the session I once had. Then
> > if I log back on, Joe Bloggs gets logged off and I regain
> > control of the session.
> >
> > Thanks
> > Dav
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> That's not possible, Dav. And neiher is it on XP.
> >> You could use a single generic user account for everyone, but
> >> they would still each have their own session, or only one at a
> >> time could have the session.
> >>
> >> What is it these users are supposed to do in this shared
> >> session? Chat with each other? In your idea of this scenario,
> >> do they all have their individual control over mouse and
> >> keyboard, or are numerous people simultaneously trying to
> >> control the single shared session?
> >> Maybe if you explain what you would like your users to be able
> >> to do, we can find a solution.
> >>
> >>
> >> _________________________________________________________
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> TS troubleshooting: http://ts.veranoest.net
> >> ___ please respond in newsgroup, NOT by private email ___
> >>
> >>
> >> =?Utf-8?B?ZGF2?= <dav@discussions.microsoft.com> wrote on 13
> >> aug 2008 in microsoft.public.windows.terminal_services:
> >>
> >> > Forgive me if I am wrong, but does this setting not restrict
> >> > each user to their own unique session?
> >> >
> >> > Last time I tried this I am sure it let each user connected
> >> > have a single session, but if 5 users connected that means 5
> >> > sessions. I just want one session shared between everyone who
> >> > connects.
> >> >
> >> > Sorry if I am not explaining this very well.
> >> >
> >> > Dav
> >> >
> >> > "Rob Leitman [MSFT]" wrote:
> >> >
> >> >> "dav" <dav@discussions.microsoft.com> wrote in message
> >> >> news:CF446E73-3992-48CB-9DFB-D541EBFBF596@microsoft.com...
> >> >> > Hi all,
> >> >> >
> >> >> > I would like to set up Window Server 2003 to basically act
> >> >> > like Windows XP.
> >> >> >
> >> >> > When I connect to the server via remote desktop it creates
> >> >> > a new session on
> >> >> > the server, now if I go to a different machine and connect
> >> >> > again instead of
> >> >> > disconnecting the other remote user and logging into that
> >> >> > session it creates
> >> >> > an entirely new session.
> >> >> >
> >> >> > I would rather it handle remote connections the same way
> >> >> > XP does.
> >> >> >
> >> >> > Please help!
> >> >> > Dav
> >> >>
> >> >>
> >> >> For Windows Server 2003, set the Restrict each user to one
> >> >> session option to Yes in Terminal Services Configuration.
> >> >> Alternatively, set the Restrict Terminal Services users to a
> >> >> single remote session group policy to Enabled.
> >> >>
> >> >> Rob
>
 
Re: Reconnect to an existing session

You can configure the "single session per user" setting as Rob
described, either in Terminal Services configuration or a GPO.
Then create a generic user account, say "TSuser" and hardcode it
into Terminal Services Configuration - rdp-tcp connection - Logon
settings - check "Always use the following logon information" -
fill in the username and password and *uncheck* "Always prompt for
password".

Just to satisfy my curiosity: in which scenario is this useful?
Aren't users going to be mad when they can be thrown off the TS at
totally unpredictable times?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?ZGF2?= <dav@discussions.microsoft.com> wrote on 13 aug
2008 in microsoft.public.windows.terminal_services:

> I'm sorry how is this achievable?
>
> Do I need to change a setting in gpedit.msc?
>
> Thanks
> Dav
>
> "Vera Noest [MVP]" wrote:
>
>> OK, assuming that privacy is of no concern, a combination of a
>> generic user account and a single session per user will do this.
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> =?Utf-8?B?ZGF2?= <dav@discussions.microsoft.com> wrote on 13 aug
>> 2008 in microsoft.public.windows.terminal_services:
>>
>> > Thanks for the speedy reply,
>> >
>> > I basically want it how I explained in the first post, so that
>> > when a user logs on the previous user gets logged off. When I
>> > look in Task Manager -> Users tab I only want to see one user
>> > listed regardless of how many user have logged on / off.
>> >
>> > Their is only the Administrator account on the machine, but if
5
>> > users connect to it via remote desktop and I look in Task
>> > Manager -> Users tab I see 5 sessions. I would just prefer it
to
>> > let users share the account one at a time.
>> >
>> > So if I log on now, then Joe Bloggs logs on after me, I get
>> > logged off and Joe Bloggs controls the session I once had.
Then
>> > if I log back on, Joe Bloggs gets logged off and I regain
>> > control of the session.
>> >
>> > Thanks
>> > Dav
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> That's not possible, Dav. And neiher is it on XP.
>> >> You could use a single generic user account for everyone, but
>> >> they would still each have their own session, or only one at
a
>> >> time could have the session.
>> >>
>> >> What is it these users are supposed to do in this shared
>> >> session? Chat with each other? In your idea of this scenario,
>> >> do they all have their individual control over mouse and
>> >> keyboard, or are numerous people simultaneously trying to
>> >> control the single shared session?
>> >> Maybe if you explain what you would like your users to be
able
>> >> to do, we can find a solution.
>> >>
>> >>
>> >> _________________________________________________________
>> >> Vera Noest
>> >> MCSE, CCEA, Microsoft MVP - Terminal Server
>> >> TS troubleshooting: http://ts.veranoest.net
>> >> ___ please respond in newsgroup, NOT by private email ___
>> >>
>> >>
>> >> =?Utf-8?B?ZGF2?= <dav@discussions.microsoft.com> wrote on 13
>> >> aug 2008 in microsoft.public.windows.terminal_services:
>> >>
>> >> > Forgive me if I am wrong, but does this setting not
restrict
>> >> > each user to their own unique session?
>> >> >
>> >> > Last time I tried this I am sure it let each user connected
>> >> > have a single session, but if 5 users connected that means
5
>> >> > sessions. I just want one session shared between everyone
who
>> >> > connects.
>> >> >
>> >> > Sorry if I am not explaining this very well.
>> >> >
>> >> > Dav
>> >> >
>> >> > "Rob Leitman [MSFT]" wrote:
>> >> >
>> >> >> "dav" <dav@discussions.microsoft.com> wrote in message
>> >> >> news:CF446E73-3992-48CB-9DFB-D541EBFBF596@microsoft.com...
>> >> >> > Hi all,
>> >> >> >
>> >> >> > I would like to set up Window Server 2003 to basically
act
>> >> >> > like Windows XP.
>> >> >> >
>> >> >> > When I connect to the server via remote desktop it
creates
>> >> >> > a new session on
>> >> >> > the server, now if I go to a different machine and
connect
>> >> >> > again instead of
>> >> >> > disconnecting the other remote user and logging into
that
>> >> >> > session it creates
>> >> >> > an entirely new session.
>> >> >> >
>> >> >> > I would rather it handle remote connections the same way
>> >> >> > XP does.
>> >> >> >
>> >> >> > Please help!
>> >> >> > Dav
>> >> >>
>> >> >>
>> >> >> For Windows Server 2003, set the Restrict each user to one
>> >> >> session option to Yes in Terminal Services Configuration.
>> >> >> Alternatively, set the Restrict Terminal Services users to
a
>> >> >> single remote session group policy to Enabled.
>> >> >>
>> >> >> Rob
 
Re: Reconnect to an existing session

Thank you very much, I will try that,

Well basically the server is a render server and is used just to render 3d
scenes. So all we need to connect to it for is to start the render manager
application, but the problem we have been getting is that if multiple users
connect to it the the render manager runs twice meaning other render nodes on
the network get messed up and don't know what manager to connect to as it is
set to start up automatically upon login.

Thanks
Dav


"Vera Noest [MVP]" wrote:

> You can configure the "single session per user" setting as Rob
> described, either in Terminal Services configuration or a GPO.
> Then create a generic user account, say "TSuser" and hardcode it
> into Terminal Services Configuration - rdp-tcp connection - Logon
> settings - check "Always use the following logon information" -
> fill in the username and password and *uncheck* "Always prompt for
> password".
>
> Just to satisfy my curiosity: in which scenario is this useful?
> Aren't users going to be mad when they can be thrown off the TS at
> totally unpredictable times?
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?ZGF2?= <dav@discussions.microsoft.com> wrote on 13 aug
> 2008 in microsoft.public.windows.terminal_services:
>
> > I'm sorry how is this achievable?
> >
> > Do I need to change a setting in gpedit.msc?
> >
> > Thanks
> > Dav
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> OK, assuming that privacy is of no concern, a combination of a
> >> generic user account and a single session per user will do this.
> >>
> >> _________________________________________________________
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> TS troubleshooting: http://ts.veranoest.net
> >> ___ please respond in newsgroup, NOT by private email ___
> >>
> >> =?Utf-8?B?ZGF2?= <dav@discussions.microsoft.com> wrote on 13 aug
> >> 2008 in microsoft.public.windows.terminal_services:
> >>
> >> > Thanks for the speedy reply,
> >> >
> >> > I basically want it how I explained in the first post, so that
> >> > when a user logs on the previous user gets logged off. When I
> >> > look in Task Manager -> Users tab I only want to see one user
> >> > listed regardless of how many user have logged on / off.
> >> >
> >> > Their is only the Administrator account on the machine, but if
> 5
> >> > users connect to it via remote desktop and I look in Task
> >> > Manager -> Users tab I see 5 sessions. I would just prefer it
> to
> >> > let users share the account one at a time.
> >> >
> >> > So if I log on now, then Joe Bloggs logs on after me, I get
> >> > logged off and Joe Bloggs controls the session I once had.
> Then
> >> > if I log back on, Joe Bloggs gets logged off and I regain
> >> > control of the session.
> >> >
> >> > Thanks
> >> > Dav
> >> >
> >> > "Vera Noest [MVP]" wrote:
> >> >
> >> >> That's not possible, Dav. And neiher is it on XP.
> >> >> You could use a single generic user account for everyone, but
> >> >> they would still each have their own session, or only one at
> a
> >> >> time could have the session.
> >> >>
> >> >> What is it these users are supposed to do in this shared
> >> >> session? Chat with each other? In your idea of this scenario,
> >> >> do they all have their individual control over mouse and
> >> >> keyboard, or are numerous people simultaneously trying to
> >> >> control the single shared session?
> >> >> Maybe if you explain what you would like your users to be
> able
> >> >> to do, we can find a solution.
> >> >>
> >> >>
> >> >> _________________________________________________________
> >> >> Vera Noest
> >> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> >> TS troubleshooting: http://ts.veranoest.net
> >> >> ___ please respond in newsgroup, NOT by private email ___
> >> >>
> >> >>
> >> >> =?Utf-8?B?ZGF2?= <dav@discussions.microsoft.com> wrote on 13
> >> >> aug 2008 in microsoft.public.windows.terminal_services:
> >> >>
> >> >> > Forgive me if I am wrong, but does this setting not
> restrict
> >> >> > each user to their own unique session?
> >> >> >
> >> >> > Last time I tried this I am sure it let each user connected
> >> >> > have a single session, but if 5 users connected that means
> 5
> >> >> > sessions. I just want one session shared between everyone
> who
> >> >> > connects.
> >> >> >
> >> >> > Sorry if I am not explaining this very well.
> >> >> >
> >> >> > Dav
> >> >> >
> >> >> > "Rob Leitman [MSFT]" wrote:
> >> >> >
> >> >> >> "dav" <dav@discussions.microsoft.com> wrote in message
> >> >> >> news:CF446E73-3992-48CB-9DFB-D541EBFBF596@microsoft.com...
> >> >> >> > Hi all,
> >> >> >> >
> >> >> >> > I would like to set up Window Server 2003 to basically
> act
> >> >> >> > like Windows XP.
> >> >> >> >
> >> >> >> > When I connect to the server via remote desktop it
> creates
> >> >> >> > a new session on
> >> >> >> > the server, now if I go to a different machine and
> connect
> >> >> >> > again instead of
> >> >> >> > disconnecting the other remote user and logging into
> that
> >> >> >> > session it creates
> >> >> >> > an entirely new session.
> >> >> >> >
> >> >> >> > I would rather it handle remote connections the same way
> >> >> >> > XP does.
> >> >> >> >
> >> >> >> > Please help!
> >> >> >> > Dav
> >> >> >>
> >> >> >>
> >> >> >> For Windows Server 2003, set the Restrict each user to one
> >> >> >> session option to Yes in Terminal Services Configuration.
> >> >> >> Alternatively, set the Restrict Terminal Services users to
> a
> >> >> >> single remote session group policy to Enabled.
> >> >> >>
> >> >> >> Rob
>
 
Re: Reconnect to an existing session

Your not trying to render on the terminal server are you? because that
really won't be possible.

--
Jeff Pitsch
Microsoft MVP - Terminal Services

"dav" <dav@discussions.microsoft.com> wrote in message
news:7B57005B-C9B5-4446-9A14-FD41CFB18FCB@microsoft.com...
> Thank you very much, I will try that,
>
> Well basically the server is a render server and is used just to render 3d
> scenes. So all we need to connect to it for is to start the render manager
> application, but the problem we have been getting is that if multiple
> users
> connect to it the the render manager runs twice meaning other render nodes
> on
> the network get messed up and don't know what manager to connect to as it
> is
> set to start up automatically upon login.
>
> Thanks
> Dav
>
>
> "Vera Noest [MVP]" wrote:
>
>> You can configure the "single session per user" setting as Rob
>> described, either in Terminal Services configuration or a GPO.
>> Then create a generic user account, say "TSuser" and hardcode it
>> into Terminal Services Configuration - rdp-tcp connection - Logon
>> settings - check "Always use the following logon information" -
>> fill in the username and password and *uncheck* "Always prompt for
>> password".
>>
>> Just to satisfy my curiosity: in which scenario is this useful?
>> Aren't users going to be mad when they can be thrown off the TS at
>> totally unpredictable times?
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> =?Utf-8?B?ZGF2?= <dav@discussions.microsoft.com> wrote on 13 aug
>> 2008 in microsoft.public.windows.terminal_services:
>>
>> > I'm sorry how is this achievable?
>> >
>> > Do I need to change a setting in gpedit.msc?
>> >
>> > Thanks
>> > Dav
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> OK, assuming that privacy is of no concern, a combination of a
>> >> generic user account and a single session per user will do this.
>> >>
>> >> _________________________________________________________
>> >> Vera Noest
>> >> MCSE, CCEA, Microsoft MVP - Terminal Server
>> >> TS troubleshooting: http://ts.veranoest.net
>> >> ___ please respond in newsgroup, NOT by private email ___
>> >>
>> >> =?Utf-8?B?ZGF2?= <dav@discussions.microsoft.com> wrote on 13 aug
>> >> 2008 in microsoft.public.windows.terminal_services:
>> >>
>> >> > Thanks for the speedy reply,
>> >> >
>> >> > I basically want it how I explained in the first post, so that
>> >> > when a user logs on the previous user gets logged off. When I
>> >> > look in Task Manager -> Users tab I only want to see one user
>> >> > listed regardless of how many user have logged on / off.
>> >> >
>> >> > Their is only the Administrator account on the machine, but if
>> 5
>> >> > users connect to it via remote desktop and I look in Task
>> >> > Manager -> Users tab I see 5 sessions. I would just prefer it
>> to
>> >> > let users share the account one at a time.
>> >> >
>> >> > So if I log on now, then Joe Bloggs logs on after me, I get
>> >> > logged off and Joe Bloggs controls the session I once had.
>> Then
>> >> > if I log back on, Joe Bloggs gets logged off and I regain
>> >> > control of the session.
>> >> >
>> >> > Thanks
>> >> > Dav
>> >> >
>> >> > "Vera Noest [MVP]" wrote:
>> >> >
>> >> >> That's not possible, Dav. And neiher is it on XP.
>> >> >> You could use a single generic user account for everyone, but
>> >> >> they would still each have their own session, or only one at
>> a
>> >> >> time could have the session.
>> >> >>
>> >> >> What is it these users are supposed to do in this shared
>> >> >> session? Chat with each other? In your idea of this scenario,
>> >> >> do they all have their individual control over mouse and
>> >> >> keyboard, or are numerous people simultaneously trying to
>> >> >> control the single shared session?
>> >> >> Maybe if you explain what you would like your users to be
>> able
>> >> >> to do, we can find a solution.
>> >> >>
>> >> >>
>> >> >> _________________________________________________________
>> >> >> Vera Noest
>> >> >> MCSE, CCEA, Microsoft MVP - Terminal Server
>> >> >> TS troubleshooting: http://ts.veranoest.net
>> >> >> ___ please respond in newsgroup, NOT by private email ___
>> >> >>
>> >> >>
>> >> >> =?Utf-8?B?ZGF2?= <dav@discussions.microsoft.com> wrote on 13
>> >> >> aug 2008 in microsoft.public.windows.terminal_services:
>> >> >>
>> >> >> > Forgive me if I am wrong, but does this setting not
>> restrict
>> >> >> > each user to their own unique session?
>> >> >> >
>> >> >> > Last time I tried this I am sure it let each user connected
>> >> >> > have a single session, but if 5 users connected that means
>> 5
>> >> >> > sessions. I just want one session shared between everyone
>> who
>> >> >> > connects.
>> >> >> >
>> >> >> > Sorry if I am not explaining this very well.
>> >> >> >
>> >> >> > Dav
>> >> >> >
>> >> >> > "Rob Leitman [MSFT]" wrote:
>> >> >> >
>> >> >> >> "dav" <dav@discussions.microsoft.com> wrote in message
>> >> >> >> news:CF446E73-3992-48CB-9DFB-D541EBFBF596@microsoft.com...
>> >> >> >> > Hi all,
>> >> >> >> >
>> >> >> >> > I would like to set up Window Server 2003 to basically
>> act
>> >> >> >> > like Windows XP.
>> >> >> >> >
>> >> >> >> > When I connect to the server via remote desktop it
>> creates
>> >> >> >> > a new session on
>> >> >> >> > the server, now if I go to a different machine and
>> connect
>> >> >> >> > again instead of
>> >> >> >> > disconnecting the other remote user and logging into
>> that
>> >> >> >> > session it creates
>> >> >> >> > an entirely new session.
>> >> >> >> >
>> >> >> >> > I would rather it handle remote connections the same way
>> >> >> >> > XP does.
>> >> >> >> >
>> >> >> >> > Please help!
>> >> >> >> > Dav
>> >> >> >>
>> >> >> >>
>> >> >> >> For Windows Server 2003, set the Restrict each user to one
>> >> >> >> session option to Yes in Terminal Services Configuration.
>> >> >> >> Alternatively, set the Restrict Terminal Services users to
>> a
>> >> >> >> single remote session group policy to Enabled.
>> >> >> >>
>> >> >> >> Rob
>>
 

Similar threads

K
How to terminate old session in VB.Net web based application
Replies
0
Views
898
kamal sekhar
K
J
RDP Session Causes OnStartup Call Each Time Reconnect Happens (C# and WPF)
Replies
0
Views
143
JohnV1982
J
K
How to terminate old session in VB.Net web based application
Replies
0
Views
676
kamal sekhar
K
G
where to get a product for server 2012 r2
Replies
1
Views
271
RSchwarz
RSchwarz
K
How to terminate old session in VB.Net web based application
Replies
0
Views
329
kamal sekhar
K
Back
Top