I'm currently an intern in a forecast service of the rising in the water level of the rivers of an entire French Region. I apologise in advance for my English, I'm still improving it.

The network infrastructure of the service is as following: Everybody work on thin clients, connecting on applicative servers (with 2008 R2 on them) via RDP. These servers aren't all integrated in a domain (Well... They COULD be in one, since they have a Samba4 DS running in a corner, but my boss had a little issue trying to add all the servers in the Samba domain. It's not my task to resolve this, so screw this) nor in a server farm managed by a connection broker.

I was asked to search for means to have only some users on each server to have multiple RDP connections, with the others having only one RDP session allowed, which is a little hard without the GPO management tools of ADDS. On top of that, I'm looking for tools to send a popup to the connected sessions of the mono-session users asking if they have still work to do when some other guy tries to connect to the same session. If they're still working in this session, they click on 'Yes' and the poor dude who was attempting to connect is rejected. If they don't answer in like 30 seconds or click on 'No' then the new user takes the hand on the session.

After a week of pointless researches involving bad scripting and a misunderstanding on what was the Connection Broker service, I turn to you to ask for help.

EDIT: I forgot to specify that the thin clients run on XP Embedded, which limits the client-side scripting (if there is) to Powershell 2.0, that I was thinking of using to do most of the work.

  • Are you using remote desktop services licensing for this? You may want to call a license reseller and make sure you're in compliance here. The two "free" RDP sessions per server are for server administration only. Anything else (like end users connecting) and you need RDS licensing in most cases. – MDMarra Mar 4 '14 at 12:07
  • We use a RD licensing manager, so there's no problem on this side. – Damodread Mar 5 '14 at 15:20
  • Since I cannot specify the mono-session policy for each user group we'll have to stay at our current network configuration (one server with multi-sessions per user, one with mono-session). I discussed with my superiors (my "internship tutors") and I'll write a basic python program to do what we want for the session management on the mono-session server. (sorry for the double post, I couldn't edit the previous comment within 5 minutes) – Damodread Mar 5 '14 at 15:29

Regarding multiple sessions for the same user, this is a matter of editing a registry key, but is controlled at a machine level, not a user level... so it's multiple sessions for all users, or none of them.

On the terminal server in question, navigate to the Registry entry located at:


When the value is 1, only one session per user is allowed. When the value is 0, users can have multiple sessions.

Regarding the warning, that should be default behavior. Provided that a user has been granted privileges to log off another user's session in order to connect, the user being knocked off should get a pop up and have 30 seconds to keep from being logged off.

With XP/2003, this behavior is controlled by Group (or local) Policy under Computer/User Configuration -> Administrative Templates -> Windows Components -> Terminal Services and, in Windows Vista/2008 and up, it's under Computer/User Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services.

  • Is this behaviour included to(/in?) every edition of 2008 R2? I took a peek at the RDS policies in gpedit, and I didn't find anything corresponding to it. The closest thing I have is "Define a time limit to active sessions". Nothing about a warning to the connected user when someone connects on his session. – Damodread Mar 4 '14 at 9:47
  • So when some user takes over an active session, the connected user gets the "Too bad, someone connected to your session so you lost the connection lol" message. – Damodread Mar 4 '14 at 9:55
  • @Damodread Not sure about the disconnection without prompting... I'll take a look and do some testing here. – HopelessN00b Mar 4 '14 at 20:16

So, since I can't specify for each user to have only one session or multiple sessions, they'll have to continue to deal with 2 servers executing the same apps, 1 having multiple-sessions users, the other having mono-session users.

To control the RDP connections, I think I'll type a little software (a basic remote desktop manager) which will send the desired popup to the active sessions when someone tries to take it over before establishing the connection.

I'll have to ask to my coworkers to use this software to connect to the mono-session servers instead of the RD manager we're currently using.

Anyway, thanks for your answer HopelessN00b.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.