Remote desktop connection limitation to one session only

Muhammad Umair 0 Reputation points
2025-01-16T05:39:54.68+00:00

We have a on prem server and have allowed few users to access the server through RD connection only. What we want to do is to apply a limitation that if one user is connected to the server through the RD connection then no other user should be allowed to access the server unless first one logs out.

We had applied the below through GPO but it didn't work and still two users are able to connect the server.

https://tecadmin.net/how-to-enable-multiple-rdp-sessions-on-windows-server/

User's image

User's image

What are our other options to do it.

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,886 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
13,624 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Muhammad Umair 0 Reputation points
    2025-01-17T02:46:44.1+00:00

    Hi @Crystal-MSFT

    Are you able to assist?

    0 comments No comments

  2. Crystal-MSFT 51,701 Reputation points Microsoft Vendor
    2025-01-20T02:42:48.43+00:00

    Hi Muhammad Umair,

    Actually, this policy has nothing to do with your target. This policy is to restrict a user to a single session, object to allowing multiple sessions for a user. 

    However, multiple users still can login simultaneously, which is decided by the server Role: Remote Desktop Service. By default, a server OS can accept 2 simultaneous sessions. If we enable RDS, it allows 3 or more. For our problem, if we uninstall RDS role, it only allows 2 users. When the third user tries to login, one of the logged users should be logged off.

    Hope the above clarifies.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  3. Zunhui Han 2,865 Reputation points Microsoft Vendor
    2025-01-20T15:53:41.6966667+00:00

    Hello,

    Thank you for posting in Q&A forum.

    As the GPO setting is correctly configured. Let's try below steps to further troubleshoot the issue:

    1.After making changes, run CMD command

    gpupdate /force

    to apply the settings immediately and restart the server if necessary.

    2.Press "Win+R" and enter "rsop.msc" to review all active GPO settings and ensure there's no conflict.

    3.Check Registry Settings: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server and ensure fSingleSessionPerUser is set to 1.

    Note If you modify the registry incorrectly, you can cause serious problems. Therefore, follow these steps carefully. For additional protection, back up the registry before you modify it. For more information about how to back up and restore the registry, see How to back up and restore the registry in Windows.

    To help other customers who may be facing the same issue, please don't forget to vote if the reply is helpful.

    Best Regards

    Zunhui


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.