Re: Reconnect to an existing session
- From: "Jeff Pitsch" <jeff@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 13 Aug 2008 09:08:06 -0400
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@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7B57005B-C9B5-4446-9A14-FD41CFB18FCB@xxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 13 aug
2008 in microsoft.public.windows.terminal_services:
I'm sorry how is this achievable?5
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@xxxxxxxxxxxxxxxxxxxxxxxxx> 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
tousers connect to it via remote desktop and I look in Task
Manager -> Users tab I see 5 sessions. I would just prefer it
Thenlet 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.
aif 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
abletime 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
restrictto 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@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 13
aug 2008 in microsoft.public.windows.terminal_services:
Forgive me if I am wrong, but does this setting not
5each 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
whosessions. I just want one session shared between everyone
actconnects.
Sorry if I am not explaining this very well.
Dav
"Rob Leitman [MSFT]" wrote:
"dav" <dav@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CF446E73-3992-48CB-9DFB-D541EBFBF596@xxxxxxxxxxxxxxxx
Hi all,
I would like to set up Window Server 2003 to basically
createslike Windows XP.
When I connect to the server via remote desktop it
connecta new session on
the server, now if I go to a different machine and
thatagain instead of
disconnecting the other remote user and logging into
asession 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
single remote session group policy to Enabled.
Rob
.
- References:
- Reconnect to an existing session
- From: dav
- Re: Reconnect to an existing session
- From: Rob Leitman [MSFT]
- Re: Reconnect to an existing session
- From: dav
- Re: Reconnect to an existing session
- From: Vera Noest [MVP]
- Re: Reconnect to an existing session
- From: dav
- Re: Reconnect to an existing session
- From: Vera Noest [MVP]
- Re: Reconnect to an existing session
- From: dav
- Re: Reconnect to an existing session
- From: Vera Noest [MVP]
- Re: Reconnect to an existing session
- From: dav
- Reconnect to an existing session
- Prev by Date: Re: Create session two apps no shell (start menu...)
- Next by Date: ts2003, users hung at black screen
- Previous by thread: Re: Reconnect to an existing session
- Next by thread: Problem - Printers are not being deleted after a user logs off.
- Index(es):
Relevant Pages
|
Loading