You cannot support three concurrent Remote Desktop Protocol (RDP) sessions on Windows Server 2022 without purchasing RDS Client Access Licenses (CALs). The operating system enforces a hard limit of two simultaneous administrative connections in its default configuration. Any attempt to exceed this limit requires the installation and proper licensing of the Remote Desktop Services role, which mandates valid CALs for each user or device connecting to the server.
The Hard Limit of Two Administrative Sessions
When you install Windows Server 2022 Standard or Datacenter edition, it includes the basic Remote Desktop Services functionality by default. This feature allows administrators to manage the server remotely using the built-in RDP client. However, Microsoft strictly limits this capability to ensure that organizations purchase appropriate licensing for production use. Specifically, the server permits only two concurrent sessions for users who belong to the local Administrators group.
This restriction applies regardless of the number of physical processors or cores installed in the hardware. Whether you are running a virtual machine with four vCPUs or a bare-metal server with sixteen cores, the software layer enforces the two-session cap. If a third administrator attempts to connect while two others are already active, the connection will be rejected immediately. You will receive an error message indicating that the maximum number of connections has been reached.
It is crucial to understand that this is not a performance bottleneck or a temporary glitch. It is a deliberate licensing enforcement mechanism embedded in the kernel. Bypassing this limit through registry edits or third-party tools is not supported and often leads to system instability or security vulnerabilities. The correct path forward involves either staying within the two-session limit or implementing the full RDS infrastructure.
Why RDS CALs Are Mandatory for More Than Two Users
To support more than two concurrent users, you must install the Remote Desktop Session Host (RDSH) role service. This role transforms the server from a simple management endpoint into a full-fledged application hosting environment. Once the RDSH role is installed, the server stops enforcing the two-administrator limit and instead looks to a License Server to validate connections.
The licensing model for RDS operates on a per-user or per-device basis. A User CAL grants one specific individual access from multiple devices. A Device CAL allows multiple individuals to share a single device, such as a shift worker using a terminal. Without these licenses, the License Server will deny authentication requests after the grace period expires, typically 90 days. During this grace period, the server may allow connections, but it will display persistent warnings and eventually block new sessions entirely.
Purchasing CALs is not optional if you intend to provide remote desktop services to more than two people simultaneously. The cost of CALs varies depending on whether you choose the subscription-based license or the perpetual license option. Subscription licenses require annual payments, while perpetual licenses involve a larger upfront cost. Both options require you to activate the License Server role on a designated Windows Server instance within your domain.
Configuring the License Server Role
Setting up the licensing infrastructure involves several precise steps. First, you must add the "Remote Desktop Licensing" role service to a Windows Server 2022 machine. This can be done via Server Manager or PowerShell. Next, you need to activate the server against Microsoft’s activation servers. This step validates your volume licensing agreement or retail key. Finally, you must install the purchased CALs onto the License Server. Only after these steps are complete will the RDSH server recognize the licenses and allow additional concurrent sessions.
For detailed guidance on related configuration tasks, you might find
Configuring RDS (Terminal Server) on Win2022: Setting up UPD (UVHD) files network share useful for managing user profiles in a multi-session environment. Proper profile management is essential when scaling beyond two users to ensure data integrity and session persistence.
Common Misconceptions About Workarounds
Many administrators search for ways to bypass the two-session limit without buying licenses. Some suggest modifying the registry key
fSingleSessionPerUser or disabling the license enforcement service. These methods are dangerous misinformation. They do not remove the legal requirement for CALs and often break the underlying licensing architecture. Microsoft’s anti-piracy mechanisms are deeply integrated into the RDP stack. Attempting to circumvent them can result in unexpected reboots, failed updates, or even complete loss of remote access.
Another common misconception is that installing a second copy of Windows Server on the same hardware helps. This is not feasible because you would still face the two-session limit per OS instance. Furthermore, virtualization licensing terms usually prohibit running multiple instances of Windows Server on a single host without appropriate rights. Always adhere to the official licensing guidelines provided by Microsoft to maintain compliance and system stability.
If you are exploring other aspects of Windows licensing, understanding how core licenses work is important. For context on general licensing structures, see
Security Risks of Selling a Motherboard with a Tied Windows 10 License, which highlights the importance of tracking license ownership and transferability in enterprise environments.
Alternative Solutions for Small Teams
If purchasing RDS CALs is not feasible due to budget constraints, consider alternative remote access solutions. Tools like TeamViewer, AnyDesk, or Chrome Remote Desktop allow multiple connections without the strict licensing models of Windows Server RDS. These tools are designed for individual or small business use and often have free tiers for personal use. However, they lack the centralized management, security auditing, and integration features of native RDS.
Another option is to use Windows 10 or Windows 11 Enterprise editions. While these also have limitations, they are designed for client-side usage rather than server-side hosting. They do not support the same level of concurrent session management as Server editions. Therefore, for any serious multi-user remote desktop scenario, Windows Server 2022 with proper RDS licensing remains the industry standard.
Frequently Asked Questions
Can I increase the limit to three sessions by editing the registry?
No, editing the registry does not remove the licensing enforcement. The two-session limit is hardcoded into the Remote Desktop Services architecture. Registry changes may affect session behavior but will not authorize additional concurrent connections.
What happens if I run out of RDS CALs?
Once all CALs are assigned, no new users can establish a session. Existing sessions may continue until they disconnect, but the server will reject new login attempts. You must purchase additional CALs to restore access for new users.
Is there a grace period after installing RDSH?
Yes, Microsoft provides a 90-day grace period after installing the Remote Desktop Session Host role. During this time, the server allows connections without validating CALs. After 90 days, unlicensed connections are blocked unless a License Server is configured and activated.
Do I need a separate server for the License Server role?
Not necessarily. You can install the Remote Desktop Licensing role on the same server that hosts the Session Host role. However, best practices recommend separating these roles for redundancy and security. A dedicated License Server ensures availability even if the Session Host server goes offline.
Can I use User CALs for both admins and regular users?
Yes, User CALs cover all types of connections to the RDS environment. Whether a user is accessing a published app or a full desktop, they require a valid User CAL. The type of CAL does not change based on the user’s administrative privileges.