RE: 2003 Terminal Services

[bazola]

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

 

[m_cozzy]

sorry didnt read it all but admin tools > terminal service config > server settings > restrict each user to one session = no

 

[bazola]

Thanks for your reply mate.

Its already set to that unfortunately

Not sure what else to do!

 

[madman045]

Is there a reason why one user would log into two PC's and then two TS sessions separately? surely they would only have one pc at any one time, if its to access the two applications on their own, surely that would be two different TS boxes?

 

[bazola]

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