Windows 10: RDP restrictions in W10

Currently we have several users accessing several W7 pc's using RDP. The pc's have custom software on them, that cannot be launched via RDP. Therefore, I created a local account, set up autologin, and auto launch custom software on login. Currently we have set up a local policy to only allow 1 RDP session. If a secondary user tries to log in while the session is in use they receive an error message "An internal error has occurred" This prompt shows before the user is asked for credentials. This way the user knows someone else is using that session and they can try one of the other pc's.

I am working on replacing the W7 with W10. but when I set the policies, and log in via RDP, I am able to take over a session that is actively in use without issue. How do I prevent this in W10?

I have reviewed W10 RDP settings - no option to limit sessions, only users

I have set the "gpedit > Administrative Templates > Windows Components > Remote Desktop Session Host > Connections, and set the Limit number of connections"=1, and also "Restrict Remote Desktop Services to a single Remote Desktop Service session" = enabled.

It doesn't limit a secondary session from kicking of the previous session. It doesn't even notify the original user.

I'm not sure what I'm missing or if we can even do this anymore in W10. The only info I can find is for w7 or windows server.

Has anyone seen this before? Any advice would be appreciated. Thanks in advance.

Currently we have several users accessing several W7 pc's using RDP. The pc's have custom software on them, that cannot be launched via RDP. Therefore, I created a local account, set up autologin, and auto launch custom software on login. Currently we have set up a local policy to only allow 1 RDP session. If a secondary user tries to log in while the session is in use they receive an error message "An internal error has occurred" This prompt shows before the user is asked for credentials. This way the user knows someone else is using that session and they can try one of the other pc's.

I am working on replacing the W7 with W10. but when I set the policies, and log in via RDP, I am able to take over a session that is actively in use without issue. How do I prevent this in W10?

I have reviewed W10 RDP settings - no option to limit sessions, only users

I have set the "gpedit > Administrative Templates > Windows Components > Remote Desktop Session Host > Connections, and set the Limit number of connections"=1, and also "Restrict Remote Desktop Services to a single Remote Desktop Service session" = enabled.

It doesn't limit a secondary session from kicking of the previous session. It doesn't even notify the original user.

I'm not sure what I'm missing or if we can even do this anymore in W10. The only info I can find is for w7 or windows server.

Has anyone seen this before? Any advice would be appreciated. Thanks in advance.

:)

 

W10 sp0t

We dont need an ultimate version. The only real difference in Ultimate was extra language packs, Craplocker and maybe RDP. Though I think RDP was in the Pro versions.

 

RDP

Hi Nikki,

We can see here that you are having issues using (RDP) Remote Desktop Protocol on your computer. There are several reasons why you are experiencing this concern. To set your expectation, we will be doing some troubleshooting steps to isolate
this problem. Before we proceed, may we know the following:

• Any changes made on the computer prior to this concern?
• What troubleshooting steps have you tried so far?
• Is this the first time that you encountered this problem?
• When did you notice about this issue?
• Can you send us a screenshot with the error message that you are getting? Note: Please do not include any personal information.

 

RDP

• Any changes made on the computer prior to this concern?
  
  Initially when we received the problem there wasn't any changes made on the computer since we couldn't figure out the problem, we upgraded the pc to windows 10. It fixed the problem momentarily and then it starts again. Then we re initiated the upgrade the
  same day I wrote this post and it was fixed again and then on today the issue is back

• What troubleshooting steps have you tried so far?
  
  In the past we would delete the MS Licensing Protocol folder as suggested by so many other posts and restart the RDP connection ad administrator to rebuild it. This time around it didn't fix anything. Like I said previously we've tried to upgrade the PC and
  the fix is temporal

• Is this the first time that you encountered this problem? No

• When did you notice about this issue? I'm not sure when it started because I haven't been on this project that long but I would say within the last month based on me. Based on other conversations this has happened in the past.

• Can you send us a screenshot with the error message that you are getting? Note: Please do not include any personal information.
  
  Sure