Changing behavior when same user logs in somewhere else

[Brad Smith]

I am running a Win2003 TS with the Win2003 RDP client on a variety of platforms (Win 2000, XP, etc).

If a user if currently logged in to a TS session on one system and someone else logs in to the same TS with the same user ID from a different system, the user that was first logged in gets kicked out with a message box:

The remote session was disconnected because another user has connected to the session

Is there a way I can prevent the same user ID from being used from a different system if it is already logged in somewhere else?

 

[Vera Noest [MVP]]

This behaviour is by design if you apply the GPO "Restrict each
user to one remote session". I agree that it would be much better
if the second connection attempt failed, or - better still - if
you were give a choice about what to do.

Since you seem to describe a situation where different users are
interfering with each others sessions, I would recommend
individual user accounts.