What is included in Microsoft Server 2019 RDS User CAL?

RDS Access Right – Lets a named user open Remote Desktop sessions.
Per User Model – One license follows the user across any device.
Active Directory Assignment – CAL is tracked per user in Active Directory.
Application Delivery – Covers full desktops and individual published apps.
Backward Host Support – Works on Server 2019 and Server 2016 hosts.
Important – No Windows Server license or Windows Server CAL is included.
Core Capacity – A 2019 RDS CAL cannot license 2022 or 2025 hosts.

What are the main benefits of Microsoft Server 2019 RDS User CAL?

The RDS User CAL is the access license each user needs to connect to a Remote Desktop Session Host running on Windows Server 2019. It sits on top of the base server license and the standard Windows Server CAL, and it keeps multi-user remote sessions compliant once the grace period ends.

Device Freedom – User connects from laptop, desktop, or thin client.
Compliance Coverage – Keeps RDP sessions legal past the 120-day grace.
No Revocation Loss – Per user CALs are never revoked or reclaimed.
Cross-Domain Issuing – License server issues CALs across domains and forests.
Roaming Workforce – One CAL fits staff who switch machines often.
Type Conversion – Can be converted to Device CALs if needs change.

What does the Microsoft Server 2019 RDS User CAL actually do?

It grants one user the right to start a Remote Desktop session on a Windows Server 2019 Session Host. Without an RDS CAL, Windows Server only allows two simultaneous administrative RDP connections for maintenance, and any further remote sessions stop working once the 120-day grace period ends. The CAL is requested from a Remote Desktop Licensing server each time the user signs in and is then tied to that user in Active Directory. This is what turns a single server into a working multi-user remote application or desktop environment.

What is the difference between an RDS User CAL and an RDS Device CAL?

A User CAL is assigned to a person and lets that person connect from any number of devices, while a Device CAL is assigned to a machine and lets any number of people use that one device. The per user model suits cases where each employee has their own equipment or works from several devices, such as an office PC plus a home laptop. The per device model fits shift work where multiple staff share the same physical workstations. One practical difference: up to 20% of per device CALs can be revoked through the licensing manager, but per user CALs cannot be revoked at all, so size the user count carefully before buying.

Do I need a separate Windows Server license and Windows Server CAL as well?

Yes. The RDS User CAL is an additional license and does not replace either the base Windows Server 2019 license or the standard Windows Server CAL. The Windows Server CAL covers basic access to server services such as file, print, and DNS, while the RDS CAL specifically covers the Remote Desktop session itself. In practice a remote user needs both: a Windows Server CAL to reach the server and an RDS CAL to run the desktop or app remotely. Buying RDS CALs alone, expecting them to enable a server on their own, is the most common purchasing mistake with this product.

Can a 2019 RDS User CAL be used with newer Windows Server versions?

No. A Windows Server 2019 RDS CAL can only license session hosts running Windows Server 2019 or Windows Server 2016, not 2022 or 2025. RDS CAL compatibility runs backward only: newer CALs cover older hosts, but older CALs never cover newer hosts. So if you plan to move your Session Host to Server 2022 within the license lifetime, a 2019 CAL will not follow it and you would need to buy 2022 CALs. Confirm the exact Windows Server version of your RD Session Host before ordering, because the CAL version must match or exceed it.

What should users check before choosing this CAL?

Confirm three things: the Windows Server version of your Session Host, whether your environment fits the per user model, and that you have a Remote Desktop Licensing server to install the CALs on. The license server must run Windows Server 2019 or later to host 2019 RDS CALs. Per user CALs also cannot be validated in a pure workgroup, so they assume an Active Directory domain for proper assignment. If your users share fixed workstations on shifts rather than carrying their own devices, a Device CAL is usually the more economical choice.

Frequently asked questions about Microsoft Server 2019 RDS User CAL

Can per user RDS CALs be tracked in a workgroup without Active Directory?

No. Per user RDS CALs are assigned to user accounts in Active Directory and cannot be validated in a workgroup, which is why workgroup sessions get dropped. If you run without a domain, the per device CAL is the type that still works, since it is tied to hardware rather than to a directory account.

Can I convert per user RDS CALs to per device CALs later?

Yes. Installed RDS CALs can be converted between per user and per device using the Convert Licenses option in the RD Licensing Manager console or the Convert-License PowerShell cmdlet. After converting, the Session Host licensing mode must be set to match the new CAL type, or the converted CALs will not be issued.

Do external users such as contractors or clients also need an RDS CAL?

Yes. Every user who connects to the Remote Desktop environment needs an RDS CAL, with no exemption for external contractors, partners, or clients. For a large number of outside users, Microsoft offers an External Connector license as an alternative to buying individual CALs for each one.

What happens when the Remote Desktop licensing grace period ends?

Windows Server 2019 gives a 120-day grace period during which the Session Host role works without a license server. Once it ends, clients without a valid RDS CAL can no longer sign in and see an error stating that no Remote Desktop License Servers are available. Installing your RDS User CALs on an activated license server before that point prevents the lockout.