Windows Server 2016, like other server editions, has a default limit of two simultaneous RDP sessions for administrative purposes. This can be restrictive in environments where multiple users need remote access at the same time. So, how do I allow more than 2 RDP sessions to a Windows Server 2016 machine? In this detailed guide, we’ll cover everything you need to know, from default RDP limits to enabling multiple concurrent user sessions using Remote Desktop Services (RDS).
Why Am I Limited to 2 RDP Sessions?
Out of the box, Windows Server 2016 supports two active RDP sessions for administrative use. This is meant for server management and troubleshooting by IT staff—not for multiple users accessing the server as a shared desktop environment.
If you try to initiate a third connection, you’ll receive a message saying:
“Another user is signed in. If you continue, they will be disconnected.”
This limitation is by design and can only be lifted by installing and configuring Remote Desktop Services along with Remote Desktop Client Access Licenses (RDS CALs).
Solution: Deploy Remote Desktop Services (RDS)
To support more than two concurrent sessions on Windows Server 2016, you need to install and configure Remote Desktop Services (RDS). This is Microsoft’s official solution for supporting multiple simultaneous RDP users.
Components of RDS
Here are the main components you’ll need:
- Remote Desktop Session Host (RDSH) – Hosts the user sessions.
- Remote Desktop Licensing – Manages RDS CALs.
- Remote Desktop Connection Broker (Optional) – Manages session load balancing and reconnection.
- Remote Desktop Web Access (Optional) – Allows RDP via a browser.
Step-by-Step Guide to Allow More Than 2 RDP Sessions on Windows Server 2016
Step-1: Install Remote Desktop Services Role
- Open Server Manager.
- Click Manage > Add Roles and Features.
- Choose Role-based or feature-based installation.
- Select your server and click Next.
- In the Server Roles section, check Remote Desktop Services.
- Choose to install:
- Remote Desktop Session Host
- Remote Desktop Licensing
- Complete the wizard and restart the server if required.
Step-2: Configure Remote Desktop Licensing
- Open Server Manager & go to Remote Desktop Protocol Services.
- Under Overview, click RD Licensing and Activate Server.
- Follow the activation wizard using:
- Automatic Connection (Internet)
- Or Phone/Browser Method
- Once activated, install your RDS CALs:
- You must purchase CALs for each user or device that connects.
- Use Remote Desktop Licensing Manager to add the CALs.
Step-3: Set Session Limits (Optional)
To allow more than 2 sessions, you can tweak Group Policy:
- Run gpedit.msc from the Start Menu.
- Navigate to:
pgsql Copy Personal Desktop Setting > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections
- Enable and configure the following settings:
Limit number of connections → Set a number higher than 2.
Restrict Remote Desktop Services users to a single session → Set to Disabled if you want users to open multiple sessions.
Step-4: Verify Configuration
- Open Command Prompt and type:
graphql Copy query session
This command shows active sessions and their states.
- Try connecting from multiple clients and verify that more than two sessions are allowed.
Licensing Requirements: What You Need to Know
Administrative vs. User Sessions
- The default 2-session limit applies to administrative purposes only.
- To allow multiple users for general use, you must purchase RDS CALs.
Types of CALs
There are two types of Remote Desktop CALs:
- Per User CAL – Best for companies where users access from multiple devices.
- Per Device CAL – Ideal for environments where multiple users share the same machine.
Cost
RDS CALs are sold separately from your Windows Server license. Pricing can vary based on region, reseller, and type.
Common Issues and How to Fix Them
Issue 1: “The number of connections limited”
Fix: Ensure that you’ve installed RDS roles and purchased enough RDS CALs. Check Group Policy settings to ensure the connection limit not restricted.
Issue 2: Sessions Getting Disconnected
This can happen if:
- You’re trying to use more than 2 sessions without proper licensing.
- Sessions being overridden due to Group Policy or timeouts.
Fix: Make sure session timeouts are extended in the Group Policy and that multiple sessions are allowed per user.
Issue 3: License Server Not Detected
Sometimes, the RDS Host cannot detect the license server.
Fix:
- Open gpedit.msc.
- Go to:
pgsql Copy Desktop Configuration > Administrative Templates > Windows Components > Remote Desktop Services > RD Session Host > Licensing
- Set:
- Use the specified Remote Desktop license servers → Add your license server name.
- Set the Remote Desktop licensing mode → Choose Per User or Per Device.
Best Practices for Managing RDP Sessions
- Use Connection Broker for high availability and load balancing.
- Enable NLA (Network Level Authentication) for secure logins.
- Monitor sessions using Task Manager > Users or query session command.
- Always stay compliant with Microsoft licensing to avoid penalties.
Can I Hack or Patch the Limit?
There are third-party tools and DLL patches that claim to unlock unlimited RDP sessions without licensing. However:
This is illegal and violates Microsoft’s licensing agreement. It may also expose your server to serious security risks.
Always follow Microsoft’s guidelines and use properly licensed solutions.
Final Thoughts
To allow more than 2 RDP sessions on Windows Server 2016, the official and supported way is to install Remote Desktop Services and apply valid RDS CALs. This setup ensures you’re compliant with Microsoft licensing while providing a scalable solution for your users or team.
Key takeaways:
- Default 2 RDP sessions are for admin use only.
- Install RDS to support multiple user connections.
- Licensing required for more than two users.
- Avoid unofficial patches or hacks.
With the proper RDS setup, you can turn your Windows Server 2016 into a powerful multi-user environment for remote work, app hosting, and more.
