Guest Bazola Posted September 28, 2008 Posted September 28, 2008 RE: 2003 Terminal services connections Hi guys Need a bit of advice if you wouldnt mind. I have setup a TS with two applications that the users need. I have locked it down with a TS GP and everything is working correctly. I have also written a GP to put an RDC connection on clients that need it to allow them to connect to the session. The issue I have is all the clients currently connect to X Domain and the terminal server is on Y. I dont want to have to create them accounts on the Y Domain to allow them to login so I wanted to utilise a single account. However I am finding if a user is logged in on one machine and I try and login as the same user on another it automatically takes over that session rather than starting a new one. If I do it off the same machine it does give me a new session as long as the other one is still connected and active. If the session is active but disconnected it puts me into the same session. I have applied the following group policies to try and get around this without success Computer Policy Windows Components/Terminal Services/Sessionshide Policy Setting Allow reconnection from original client only Enabled Set time limit for disconnected sessions Enabled End a disconnected session 10 minutes Policy Setting Sets a time limit for active but idle Terminal Services sessions Enabled Idle session limit: 30 minutes Policy Setting Terminate session when time limits are reached Enabled User Policy Windows Components/Terminal Services/Sessionshide Policy Setting Allow reconnection from original client only Enabled Set time limit for disconnected sessions Enabled End a disconnected session 10 minutes Policy Setting Sets a time limit for active but idle Terminal Services sessions Enabled Idle session limit: 30 minutes Policy Setting Terminate session when time limits are reached Enabled Any suggestions or alternative solutions would be appreciated. Cheers Baz
Guest jolteroli Posted September 28, 2008 Posted September 28, 2008 Re: 2003 Terminal services connections Re: 2003 Terminal services connections "Bazola" <Bazola@discussions.microsoft.com> schrieb im Newsbeitrag news:D514FBF5-BC26-4FB9-993E-D12E5D65E148@microsoft.com... > Hi guys > > Need a bit of advice if you wouldnt mind. I have setup a TS with two > applications that the users need. I have locked it down with a TS GP and > everything is working correctly. Well! > I have also written a GP to put an RDC > connection on clients that need it to allow them to connect to the > session. > The issue I have is all the clients currently connect to X Domain and the > terminal server is on Y. I dont want to have to create them accounts on > the Y > Domain to allow them to login so I wanted to utilise a single account. Either you preset the Domain field in the RDP file to the domain, the TS resides or you build a trust-relationship between the both domains. Don't ask me how... but it works. > However I am finding if a user is logged in on one machine and I try and > login as the same user on another it automatically takes over that session > rather than starting a new one. If I do it off the same machine it does > give > me a new session as long as the other one is still connected and active. > If > the session is active but disconnected it puts me into the same session. Have a look into the Terminal Service Configuration. There is an option to allow more than a single session per user. -jolt
Guest Bazola Posted September 28, 2008 Posted September 28, 2008 Re: 2003 Terminal services connections Re: 2003 Terminal services connections I need it to give a new session. For example one user is working off Client machine X and they are logged into the TS Session. Another user comes along logs into machine Y. They try to connect to the Terminal server session logging as with the generic account but instead of starting a new session it takes over the sesion which was started on machine X by another user. Both apps are installed on the single terminal server and all that is working correctly. Thats my Issue "jolteroli" wrote: > "Bazola" <Bazola@discussions.microsoft.com> schrieb im Newsbeitrag > news:D514FBF5-BC26-4FB9-993E-D12E5D65E148@microsoft.com... > > Hi guys > > > > Need a bit of advice if you wouldnt mind. I have setup a TS with two > > applications that the users need. I have locked it down with a TS GP and > > everything is working correctly. > > Well! > > > I have also written a GP to put an RDC > > connection on clients that need it to allow them to connect to the > > session. > > The issue I have is all the clients currently connect to X Domain and the > > terminal server is on Y. I dont want to have to create them accounts on > > the Y > > Domain to allow them to login so I wanted to utilise a single account. > > Either you preset the Domain field in the RDP file to the domain, the TS > resides or you build a trust-relationship between the both domains. Don't > ask me how... but it works. > > > However I am finding if a user is logged in on one machine and I try and > > login as the same user on another it automatically takes over that session > > rather than starting a new one. If I do it off the same machine it does > > give > > me a new session as long as the other one is still connected and active. > > If > > the session is active but disconnected it puts me into the same session. > > Have a look into the Terminal Service Configuration. There is an option to > allow more than a single session per user. > > -jolt > >
Guest jolteroli Posted September 28, 2008 Posted September 28, 2008 Re: 2003 Terminal services connections Re: 2003 Terminal services connections "Bazola" <Bazola@discussions.microsoft.com> schrieb im Newsbeitrag news:34B9E070-A180-498A-879F-BF1D959B0429@microsoft.com... >I need it to give a new session. For example one user is working off Client > machine X and they are logged into the TS Session. Another user comes > along > logs into machine Y. They try to connect to the Terminal server session > logging as with the generic account but instead of starting a new session > it > takes over the sesion which was started on machine X by another user. Both > apps are installed on the single terminal server and all that is working > correctly Method #1: Run ``tscc.msc'' and go to Server configuration on the left side. On the right one, you'll see an option to allow multiple sessions per user. Dunno if a restart is required... Method #2: Open ``regedit.exe'' and go to "HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Terminal Server". There is a DWORD with the name "fSingleSessionPerUser". The value should be self-explaining. -jolt
Recommended Posts