I have some information that may be of help:
"If I ENABLE this, when my users sign into RDS at their 2nd location, does that then disconnect them from RDS at their first location, and leave them with only the 1 sessions, now on PC #2? (i.e., does the session now transfer to PC #2)" Yes. "I know the app won't re-open to the same place, more's the pity." Perhaps I'm missing something, but the user would see their previous session with any existing apps that they had opened. Has your experience been different. "If I DISABLE this, then the user should be able to start a whole brand new session on PC #2, fire up the app, and enter whatever information they got while sitting at PC #2. Correct?" Correct. We currently have this set up in one of our environments with Server 2008r2. We have this implemented with session time limits. "I don't want unlimited sessions, I want only 2 max sessions. Where I do configure this max sessions per user?" I'm not sure about this, so I'll let someone else answer this. If there isn't a policy for it, you could potentially write a script that you run on this terminal server to log the user off if a third session is detected. "And when they log out of the session on PC #2, they can saunter back and pick up right at their original PC with session #1? (presuming that they haven't timed out and been disconnected or logged off, I mean)" If the above policy is disabled (second condition case you mentioned), then yes the user would simply go back to PC1 assuming the session is still open, and the user can log back in. "I see total number of simultaneous connections to the server; is that per user, or per server? (I'm guessing per user, but I can't tell)" Are you referring to the policy named Limit number of connections in the same branch as the Restrict Remote Desktop Services users to a single Remote Desktop services session you referenced above? If so, it appears that it limits the total number of connections to the entire server, and is not specific to a user per the help information in Group Policy: Specifies whether Remote Desktop Services limits the number of simultaneous connections to the server. You can use this setting to restrict the number of Remote Desktop Services sessions that can be active on a server. If this number is exceeded, additional users who try to connect receive an error message telling them that the server is busy and to try again later. Restricting the number of sessions improves performance because fewer sessions are demanding system resources. By default, RD Session Host servers allow an unlimited number of Remote Desktop Services sessions, and Remote Desktop for Administration allows two Remote Desktop Services sessions. -Aakash Shah -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Michael Leone Sent: Wednesday, March 26, 2014 12:28 PM To: [email protected]; [email protected] Subject: [NTSysADM] Win 2012 RDS multiple simultaneous connections? I am trying to understand this. Right now, we use an industry specific application on a Citrix environment. Apparently my users will sign into Citrix, fire up the app, and help customers who come in. During such times, however, they are known to take the customer to a different location, and sign into Citrix and the app at this second location, as well (I imagine to enter in information learned while at the second location). We are now transitioning from Citrix to Win2012 RDS. So I need to be able to allow my users to do the same thing - sign into RDS at more than one location at a time, and run that app. Looking into GPO, I see where I can have "Restrict RDS users to a single RDS session" in the Remote Desktop section of the computer administrative template. If I ENABLE this, when my users sign into RDS at their 2nd location, does that then disconnect them from RDS at their first location, and leave them with only the 1 sessions, now on PC #2? (i.e., does the session now transfer to PC #2) I know the app won't re-open to the same place, more's the pity. LOL If I DISABLE this, then the user should be able to start a whole brand new session on PC #2, fire up the app, and enter whatever information they got while sitting at PC #2. Correct? - if yes, this says unlimited sessions. I don't want unlimited sessions, I want only 2 max sessions. Where I do configure this max sessions per user? And when they log out of the session on PC #2, they can saunter back and pick up right at their original PC with session #1? (presuming that they haven't timed out and been disconnected or logged off, I mean) I see total number of simultaneous connections to the server; is that per user, or per server? (I'm guessing per user, but I can't tell) Thanks for any help in clearing up this confusion.
