- Spring sale — extra 15% off with code MMK15
- Instant email delivery, 24/7
Windows Server 2019 RDS User CAL is a genuine Microsoft license that enables secure remote access to Windows Server 2019 via Remote Desktop Services for a single named user from any device. It is required for businesses using RDS Session Host, RemoteApp, or virtual desktop environments to ensure full Microsoft licensing compliance. Perfect for USA & Canada businesses, this license offers instant email delivery, easy activation, and reliable access for remote workers, hybrid teams, and multi-device users.
You'll receive your license key, an official Microsoft download link, and a 1-page activation guide.
Direct Microsoft activation
Email in under 5 minutes
Real humans, any time zone
Full money-back guarantee
A Windows Server 2019 Remote Desktop Services User CAL (Client Access License) is the Microsoft-required license that legally entitles a named individual to connect to Remote Desktop Services on a Windows Server 2019 host from any device, from any location, as many times as needed.
If your organization uses Remote Desktop Services to deliver hosted desktops, published applications, or centralized remote access to Windows Server 2019, every user who connects requires both a base Windows Server 2019 User or Device CAL and a Windows Server 2019 RDS User CAL. The RDS User CAL is the additional license that specifically covers the Remote Desktop Services session it is a legal requirement enforced during Microsoft licensing audits and cannot be substituted with any other license type.
The license key delivered by MMKeys is a genuine Microsoft RDS User CAL for Windows Server 2019, delivered to your email inbox within minutes of purchase, backed by our lifetime warranty and money-back guarantee.
Remote Desktop Services is the Windows Server role that enables multiple users to connect simultaneously to a Windows Server 2019 host and run applications or full desktop sessions in a centralized, server-hosted environment. It is the platform behind virtual desktop infrastructure, remote application delivery, work-from-home access to corporate applications, thin-client computing environments, and branch office connectivity to centralized server resources.
Microsoft licenses access to Remote Desktop Services through Client Access Licenses. Without valid RDS CALs installed and issued through an RDS License Server, Windows Server 2019 operates in a grace period of 120 days before Remote Desktop Services begins refusing connections from users beyond the two built-in administrative sessions that are always available for server management purposes.
A User CAL licenses a specific individual not a device. One Windows Server 2019 RDS User CAL covers a single named user connecting to Remote Desktop Services from any number of devices: their office workstation, their home computer, their laptop, their tablet, or any other endpoint they use to connect. There is no limit on how many devices that licensed user may connect from, and no limit on how many simultaneous sessions that user may hold across those devices.
This makes the User CAL the correct and most cost-effective choice for any user who accesses Remote Desktop Services from more than one device which describes the majority of remote workers, hybrid employees, and flexible workers in organizations of all sizes today.
Remote Desktop Services in Windows Server 2019 is built around several role services that work together to deliver a complete remote access and application delivery infrastructure.
The Remote Desktop Session Host is the server role that hosts the actual desktop sessions and published application sessions that users connect to. Session Host servers are where the applications run and where user sessions are maintained they are the compute component of the RDS deployment, and they are the servers for which RDS CALs are required.
The Remote Desktop Connection Broker manages user connections across multiple Session Host servers in a load-balanced Session Host farm, reconnects users to their existing sessions when they reconnect after a disconnection, and manages the user-to-session mapping across the deployment. Connection Broker is required in multi-Session-Host deployments and enables the scale-out of RDS capacity beyond a single server.
The Remote Desktop Gateway enables secure external access to internal Remote Desktop Services resources from outside the corporate network allowing remote users to connect to internal Session Hosts, virtual desktops, and RemoteApp published applications over HTTPS without requiring a traditional VPN connection. Gateway is the component that enables work-from-home RDS access and remote office connectivity without VPN infrastructure.
The Remote Desktop Web Access role provides a web portal where users can access published RemoteApp applications and session desktops from a browser or from the Remote Desktop client, presenting the available remote resources in a familiar web interface without requiring client-side configuration beyond the standard Remote Desktop client.
The Remote Desktop Licensing role manages and issues CAL tokens to connecting clients and tracks CAL consumption. A License Server must be present and reachable by Session Hosts for CALs to be issued. Without a License Server issuing CALs, Remote Desktop Services enters a grace period and eventually stops accepting connections beyond the two administrative sessions.
Microsoft requires RDS CALs for this architecture because Remote Desktop Services enables multiple users to share computing resources on a single server — a fundamentally different model from each user running applications on their own dedicated device. The CAL represents the per-user or per-device access right that Microsoft requires for shared server-based computing environments.
Windows Server 2019 Remote Desktop Services can be licensed either per user or per device. The two CAL types cannot be mixed on the same RDS License Server an organization must select one model for a given RDS deployment and apply it consistently.
RDS User CAL licenses a named individual. That person may connect to Remote Desktop Services from any number of devices. One CAL per person, regardless of how many endpoints they use to connect. This is the right choice for remote workers connecting from home and the office, employees who carry laptops and also use office workstations, mobile workers who connect from multiple locations and devices, and any environment where users are more mobile than the devices they use or where the number of users is smaller than the total number of devices they collectively use across the organization.
RDS Device CAL licenses a specific physical device. Any number of users may connect from that licensed device. One CAL per endpoint, regardless of how many people share it. This is the right choice for shared workstations in call centers, kiosk terminals, reception desks, manufacturing floor stations, classroom computers, and any environment where multiple users take turns using the same physical machine to connect to Remote Desktop Services — and where the number of devices is smaller than the number of users.
The practical decision rule: count the users who need RDS access and count the devices from which RDS connections will be made. License whichever number is smaller to minimize CAL cost. For most organizations with remote workers, hybrid working policies, and employees who use multiple devices, User CALs are the more cost-effective and operationally simpler choice. For shared terminal and kiosk environments, Device CALs are typically more economical.
Windows Server 2019 Remote Desktop Services builds on the foundations of Windows Server 2016 RDS with improvements in security, transport performance, virtual desktop infrastructure support, and Azure hybrid integration that benefit organizations running RDS deployments today.
Security Hardening for RDS Deployments
Windows Server 2019 ships with a meaningfully stronger default security configuration than Windows Server 2016, and these improvements benefit RDS deployments directly. SMB1 is disabled by default, removing the most commonly exploited file sharing vulnerability. The default TLS configuration is strengthened across server roles including Remote Desktop Services, with weak cipher suites disabled at the operating system level. Windows Defender is enabled by default and Windows Defender ATP integration provides behavioral threat detection for RDS Session Hosts — detecting malicious activity in RDS sessions including unusual process execution, lateral movement attempts, and credential theft behaviors that are common attack patterns in environments where Remote Desktop Services is exposed to external access.
For organizations where RDS is accessible from the internet via Remote Desktop Gateway, the default security hardening in Windows Server 2019 meaningfully reduces the attack surface of the RDS infrastructure without requiring post-installation security configuration by the administrator.
Credential Guard for RDS Session Hosts
Windows Server 2019 supports Credential Guard on hardware meeting the TPM and Virtualization-Based Security requirements protecting domain credential material including NTLM password hashes and Kerberos tickets from extraction from Session Host server memory. In RDS environments where multiple users are authenticated on the same Session Host simultaneously, protecting credential material from theft by other session users or by malicious processes running in other sessions is a meaningful security improvement. Credential Guard in Windows Server 2019 provides this protection at the operating system level without requiring changes to RDS session configuration.
Azure Virtual Desktop Integration
Windows Server 2019 Session Hosts are supported as host pool backends for Azure Virtual Desktop Microsoft’s cloud-based virtual desktop infrastructure service enabling organizations to run Windows Server 2019 RDS Session Hosts in Azure as part of an AVD deployment, providing cloud-hosted remote desktop and RemoteApp access without maintaining on-premises Session Host infrastructure. For organizations that want to move their RDS Session Host compute to the cloud while retaining Windows Server 2019 as the session operating system, AVD with Windows Server 2019 Session Hosts provides the migration path. Note that Azure Virtual Desktop licensing is separate from on-premises RDS CAL licensing.
Remote Desktop Gateway Improvements
Remote Desktop Gateway in Windows Server 2019 benefits from the transport and TLS improvements in the 2019 release, providing more reliable and secure external connectivity for remote users accessing on-premises RDS resources through the Gateway. The improved default TLS configuration means that RD Gateway connections use stronger cryptographic algorithms by default than the Windows Server 2016 equivalent, without requiring manual cipher suite configuration.
Windows Admin Center Management
Windows Admin Center in Windows Server 2019 provides improved management capabilities for Remote Desktop Services infrastructure, including monitoring of Session Host connections, session management, and performance visibility complementing the traditional Server Manager RDS management experience with a modern browser-based interface that is accessible without installing management tools on the administrator’s workstation.
Improved RemoteApp Experience
RemoteApp published applications in Windows Server 2019 benefit from the improved graphics rendering and display protocol updates in the 2019 release, providing a more seamless integration of published remote applications into the local desktop environment for end users. The improved display protocol behavior reduces visual artifacts and improves responsiveness for graphically intensive published applications compared to Windows Server 2016.
Organizations delivering hosted desktops or RemoteApp published applications any business using Remote Desktop Session Host on Windows Server 2019 to give users access to a centralized Windows desktop or to deliver specific applications as published RemoteApp programs requires RDS CALs for every connecting user. RDS User CALs are the right model when users connect from multiple devices or when managing per-user licensing is simpler than per-device tracking.
Businesses with remote and hybrid workers organizations where employees work from home some or all of the time and connect to corporate applications and desktops hosted on Windows Server 2019 Session Hosts via Remote Desktop require RDS User CALs for every person who connects. The User CAL model is ideal for hybrid workers who connect from both their home computer and their office workstation one User CAL covers both connections for the same person.
Organizations running thin-client computing environments businesses that have deployed thin-client hardware where all computing is delivered through Remote Desktop Services sessions on Windows Server 2019 Session Hosts, and where individual users roam between thin-client devices throughout the workday requiring User CALs since the same person connects from multiple thin-client endpoints.
Healthcare organizations providing remote clinical access hospitals, clinics, and healthcare networks where clinical staff access electronic health record systems, clinical imaging, and healthcare applications through Remote Desktop Services on Windows Server 2019, connecting from a variety of clinical workstations, tablets, and remote access devices. User CALs license each clinician regardless of which device they connect from.
Legal, financial, and professional services firms law firms, accounting practices, financial advisory firms, and other professional services organizations where staff access document management systems, practice management software, and financial applications through Remote Desktop Services, often connecting from multiple devices including office workstations and home computers or laptops. User CALs cover each professional regardless of connection device.
Educational institutions running Windows Server 2019 RDS universities, colleges, and school districts where faculty, staff, or students access academic applications hosted on Windows Server 2019 Session Hosts, connecting from personal devices as well as institution-provided equipment. User CALs license each person independently of device count.
IT departments upgrading from Windows Server 2016 to 2019 RDS CALs are version-specific. Organizations upgrading their RDS infrastructure from Windows Server 2016 to Windows Server 2019 must acquire Windows Server 2019 RDS CALs for all connecting users to remain compliant. Windows Server 2016 RDS CALs are not valid for connections to Windows Server 2019 RDS hosts.
MSPs managing Windows Server 2019 RDS for clients managed service providers deploying or managing Windows Server 2019 Remote Desktop Services environments for client organizations need to ensure that every end user accessing those environments is covered by a valid Windows Server 2019 RDS User CAL.
Running Remote Desktop Services on Windows Server 2019 legally requires two separate CAL types for every connecting user, purchased separately from the server operating system license.
Windows Server 2019 User CAL the base access license required for any user accessing any service on a Windows Server 2019 server, regardless of whether Remote Desktop Services is involved. This covers general server access and is required for every user connecting to Windows Server 2019 for any purpose.
Windows Server 2019 RDS User CAL the additional Remote Desktop Services-specific license required on top of the base User CAL, specifically for users accessing Remote Desktop Services sessions on Windows Server 2019. This is what the license from MMKeys provides.
Both CAL types are required. The RDS User CAL does not replace the base Windows Server 2019 User CAL — it adds to it. The Windows Server 2019 server operating system license covers the server itself. The base User CAL covers general server access. The RDS User CAL covers the Remote Desktop Services session specifically.
CALs are version-specific: Windows Server 2016 RDS User CALs are not valid for access to Windows Server 2019 RDS hosts. Windows Server 2019 RDS User CALs are backward-compatible they can be used for access to older Windows Server RDS versions including Windows Server 2016 and earlier.
RDS CALs are managed and tracked by an RDS License Server role installed on a Windows Server in the environment. The License Server issues CAL tokens to connecting clients and tracks CAL consumption against the installed CAL count. Deploying an RDS License Server and configuring your Session Hosts to point to it is a required step in any compliant RDS deployment.
Step 1 — Purchase and receive your RDS User CALs. Your license key arrives by email within minutes of payment confirmation at MMKeys. Check your spam folder if it does not appear in your primary inbox.
Step 2 — Install the Remote Desktop Licensing role. On a Windows Server 2019 server in your environment, open Server Manager, add the Remote Desktop Licensing role service under Remote Desktop Services, and complete the role installation. This server becomes your RDS License Server.
Step 3 — Activate the License Server. Open the Remote Desktop Licensing Manager console, right-click your server, and select Activate Server. Follow the activation wizard online activation completes in seconds; telephone activation is available for environments without internet access.
Step 4 — Install your RDS User CALs. In the Remote Desktop Licensing Manager, right-click your activated License Server and select Install Licenses. Enter your license key when prompted, select Windows Server 2019 as the product version and RDS Per User CAL as the license type, and complete the installation. The installed CAL count is now available for issuance to connecting users.
Step 5 — Configure Session Hosts to use your License Server. On each RDS Session Host server, open Group Policy or Local Group Policy and navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Licensing. Set the licensing mode to Per User and specify your License Server address. Apply the policy and verify that the Session Host can reach the License Server.
Step 6 — Verify licensing is working correctly. Open Remote Desktop Licensing Diagnoser on your Session Hosts to confirm that CALs are being issued correctly and that no licensing warnings or errors are present. Licensing Diagnoser reports the licensing mode, the License Server being used, and any issues with CAL issuance that require attention.
Full step-by-step activation instructions are included with every MMKeys order. Our support team is available 24 hours a day, 7 days a week if you need assistance at any stage of the deployment.
Is this a genuine Windows Server 2019 RDS User CAL? Yes. Every license sold by MMKeys is an authentic Microsoft product license. There are no shared keys, workarounds, or grey-market codes. Your RDS User CAL installs and activates through Microsoft’s official Remote Desktop Licensing infrastructure.
Do I need both a base Windows Server CAL and an RDS User CAL? Yes. Both are required. The Windows Server 2019 User CAL covers general server access for each user. The RDS User CAL covers the Remote Desktop Services session specifically. Both must be in place for every user connecting via RDS. The base Windows Server 2019 User CAL is available separately at MMKeys.
How many devices can one RDS User CAL cover? Unlimited. A User CAL licenses a specific named individual, and that person may connect from any number of devices home computer, office workstation, laptop, tablet, mobile device, or any other endpoint. There is no device limit associated with a User CAL.
Can I use Windows Server 2016 RDS CALs for Windows Server 2019? No. RDS CALs are version-specific. Windows Server 2016 RDS User CALs are not valid for connections to a Windows Server 2019 RDS host. You must purchase Windows Server 2019 RDS User CALs for users connecting to a Windows Server 2019 RDS environment. Windows Server 2019 RDS User CALs are backward-compatible with older RDS versions.
What happens if I run RDS without CALs? Windows Server 2019 provides a 120-day grace period after RDS role installation during which connections are allowed without CALs. After the grace period expires, Remote Desktop Services begins refusing user connections, permitting only the two built-in administrative sessions. Microsoft licensing audits identify CAL non-compliance independently of the technical enforcement mechanism.
Should I choose User CALs or Device CALs? Count your users who need RDS access and count the devices from which RDS connections will originate. License whichever number is smaller. User CALs are the right choice when users connect from multiple devices, when users outnumber devices, or when managing per-user licensing is operationally simpler. Device CALs are the right choice for shared workstations, kiosk terminals, and environments where multiple users share fewer devices. The two models cannot be mixed on the same RDS License Server.
Are Windows Server 2019 RDS CALs valid for Windows Server 2022 or 2025 RDS? No. RDS CALs are version-specific and match the version of the RDS host server. Windows Server 2019 RDS User CALs are valid for Windows Server 2019 RDS hosts and older. If you upgrade your Session Hosts to Windows Server 2022 or 2025, you must purchase the corresponding version of RDS CALs. Windows Server 2019 RDS CALs are backward-compatible with Windows Server 2016 and earlier RDS hosts.
Are Windows Server 2019 RDS CALs the same as Azure Virtual Desktop licenses? No. Azure Virtual Desktop uses a different licensing model based on Microsoft 365 or Windows per-user subscriptions. Windows Server 2019 RDS User CALs apply to on-premises or hosted Remote Desktop Services deployments running on Windows Server 2019 Session Hosts. If you are deploying Azure Virtual Desktop in Azure rather than on-premises RDS, consult Microsoft’s AVD licensing requirements separately.
How soon will I receive my CALs after purchase? Most MMKeys orders are delivered within minutes of payment confirmation, 24 hours a day, 7 days a week. Your email includes the license key and complete activation instructions.
What if my key does not activate? Contact MMKeys support at any time. Every license is backed by our lifetime warranty and money-back guarantee. If your key does not activate for any reason, we will resolve the issue or provide a replacement at no cost. CONTACT US
