up vote 0 down vote favorite
share [g+] share [fb]

In a Windows Server 2003/2008 Terminal server environment each RDP-TCP session is given an ID. Starting with ID 1 for the first session and ID 2 for the next and so forth.

Is is possible to change the session ID alocation to something more unique. Instead of 1, 2, 3 ... to a randomly generated number like "123f9e19-7f4b-32ca-7d30-4cd3d529d49b"

Why? As the IDs are not very unique (1, 2, 3...) it happens that when a user disconnects and the session lives on for some reason a second user can be assigned that same ID as the server thinks that the session is closed while is it not so. This, for example, causes the second user to have the first users printer session and can print out on his printer.

link|improve this question
What?! Sorry, but you I have never seen this behavior your are describing. Are you sure something else isn't broke? Do you have multiple users with the same username? – Zoredache Nov 18 '10 at 23:12
Nope, on one Terminal Server there might be 40 users all with unique user names. The multiple sessions for same user is more common (eggheadcafe.com/software/aspnet/32328392/…), but this has happened once or twice. – user60794 Nov 18 '10 at 23:24
The issue at the link you posted isn't related to your post at all... no users are being given other users' sessions. A non-TS printer driver is keeping the printer locked to the previous session - they are getting new sessions when they log in. – Andrew Barber Nov 19 '10 at 2:05
I have to agree with the other comments. No other user is going to be connected to another users session. In addition, how are session numbers 1, 2, 3, etc. not unique? There's only one session 1... that's pretty unique if you ask me. – joeqwerty Nov 19 '10 at 12:37
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown
discard