A Server 2022 Remote Desktop user CAL lets one named user open Remote Desktop Services sessions on Windows Server 2022, 2019 or 2016 session hosts from any number of devices, and this pack holds 50 of them, instant to email. It follows the person, not the device. Office PC, laptop, tablet, the computer at home. All covered by one CAL. Buy Server 2022 Remote Desktop User CALs here; we email the license right after payment.
| Detail | This pack |
|---|---|
| Product | Windows Server 2022 Remote Desktop Services User CAL |
| Quantity | 50 users |
| License type | Per user (one named user, any number of devices) |
| Works with session hosts | Windows Server 2022, 2019 and 2016 |
| License server | Windows Server 2022 or later |
| Delivery | Instant to email |
| Activation | Activates online with Microsoft servers |
What a Server 2022 Remote Desktop user CAL is
A license for one named user to open Remote Desktop sessions on an RD Session Host. It follows the person. Office PC by day, home computer at night.
It suits offices and remote teams where people move between machines.
How licensing runs behind the scenes
Remote Desktop Services is the role that publishes full desktops or single RemoteApp programs from a server. Someone connects. The session host checks with the RD license server. The license server issues a license from the installed pool.
In most small offices the licensing role runs on an existing domain member server. So we wouldn’t budget extra hardware for it.
Active Directory is part of the deal
Per-user CALs are tracked through Active Directory. In a workgroup they can’t be tracked. For a workgroup, device CALs are the ones that work.
Server 2022 Remote Desktop user CAL or device CAL
User CALs, when each person has their own devices or works from several. Device CALs, when several people share the same computers in shifts. A warehouse terminal, say, or a call center desk.
You can’t mix both modes on one session host collection.
| Item | Per user RDS CAL | Per device RDS CAL |
|---|---|---|
| Assigned to | A user account in Active Directory | A physical device |
| Works in a workgroup | Cannot be tracked in a workgroup | Yes, tracked without Active Directory |
| Temporary licenses | None | 90-day temporary CAL on first sign-in |
| Renewal | Shown as valid 60 days, then renewed on sign-in | Random period of 52 to 89 days |
| Revoking | Not possible (reassign after 90 days) | Up to 20% can be revoked |
| Best for | People who use several devices | Shared PCs used by shift workers |
The data comes from Microsoft Learn, RDS client access licenses. Want the long version? Our RDS CAL per user vs per device guide. For shared terminals, the Windows Server 2022 RDS 50 device CAL pack is the better match.
Which hosts and license servers it works with
Newer CALs cover older servers. These work with session hosts running Windows Server 2022. Hosts on 2019 and 2016 are covered as well. Sessions on Windows Server 2025 hosts are not.
The CALs go on a Remote Desktop license server running Windows Server 2022 or later.
| Server role | Windows Server 2025 | Windows Server 2022 | Windows Server 2019 | Windows Server 2016 |
|---|---|---|---|---|
| RD Session Host accepts 2022 RDS CALs | No | Yes | Yes | Yes |
| License server can hold 2022 RDS CALs | Yes | Yes | No | No |
Moving session hosts to 2025 soon? Then buy the Windows Server 2025 RDS 50 user CAL pack instead. It also covers 2022 and older hosts. The source is Microsoft’s RDS CAL compatibility tables.
What else you need
RDS CALs come on top of the regular licenses.
- Server license. For the RD Session Host itself. The Windows Server 2022 Standard key is one example, the Windows Server 2022 Datacenter key another. Older hosts on Windows Server 2019 Standard work with this pack too.
- Windows Server CALs. Base access licenses for each user or device.
- RDS CALs. This pack, for the Remote Desktop sessions.
- The licensing role. Remote Desktop Licensing on a server in the domain, activated once with Microsoft.
Two simultaneous administrative RDP sessions need no RDS CALs. Remote Desktop itself still has to be switched on, see enabling RDP on Windows Server.
The grace period
The first 120 days after deployment run as a grace period, without a license server. After that every session needs a valid RDS CAL. Users then see the “no Remote Desktop license servers available” message. Our guide to that error walks through the fix.
Before you order
- Count named users, not devices.
- Make sure there’s an Active Directory domain.
- License server on 2022 or later.
- Session hosts on 2022, 2019 or 2016.
- Base server license and Windows Server CALs in place.
Installing the 50 Server 2022 Remote Desktop user CALs
It all happens in Remote Desktop Licensing Manager, on your activated license server.
- On the license server, open Server Manager. Go to Tools, Remote Desktop Services, Remote Desktop Licensing Manager.
- Server shown as not activated? Right-click it, select Activate Server and follow the wizard.
- Right-click the server name and select Install licenses, then Next.
- Select the license program that matches your purchase. Enter the license code from our email.
- Choose product version Windows Server 2022, license type RDS Per User CAL and quantity 50.
- Finish the wizard. It contacts the Microsoft Clearinghouse and adds the licenses to the pool.
Setting the deployment to per user
- Open Server Manager, then Remote Desktop Services, then Overview.
- Under Tasks, choose Edit Deployment Properties.
- Go to RD Licensing and select Per User.
- Add your license server.
Without a full RDS deployment
Set the same values by Group Policy. The path, one level at a time:
- Computer Configuration.
- Administrative Templates.
- Windows Components.
- Remote Desktop Services.
- Remote Desktop Session Host.
- Licensing.
Reporting and troubleshooting are covered in our guide to managing CAL licenses in Windows Server 2022.
The license server doesn’t enforce per-user CALs. So run a per-user CAL report in RD Licensing Manager now and then. We’d check that the user count stays within your 50 licenses.
When someone leaves
A per-user CAL can’t be revoked. It can be reassigned after 90 days.
Server 2022 Remote Desktop user CAL snags
- A workgroup. Per-user CALs can’t be tracked there.
- A license server on 2019. It can’t hold this pack.
- More than 50 people connecting. Nothing blocks it, and it breaches the license terms.
- A collection still set to per device.
Counting users for a 50 user CAL pack
Named people, not devices, not concurrent sessions. Contractors with their own accounts count too. A few Microsoft rules to keep in mind:
- Per-user licensing isn’t enforced. The license server keeps issuing from an “overused” pool past 50, and that breaches the RDS license terms.
- Each issued per-user CAL shows a 60-day expiry and renews when the user signs in. Someone who stops signing in drops off the list.
- Reassigning a CAL to another person takes at least 90 days, special cases aside.
- Session hosts in Azure Virtual Desktop that run Windows Server need RDS CALs as well.
- A license server can issue CALs across Active Directory domains or forests, with limitations Microsoft documents separately.
More than 50 names on the list? Add a second pack, or split the shared-desk staff off onto device CALs in their own collection. The tracking report in RD Licensing Manager shows the real number.
Delivery and help
The license code is emailed instantly after payment. No account needed. You pay by card, Apple Pay or Google Pay through Stripe.
Something went wrong? We’ll help you fix it. A code that won’t install gets fixed with you or replaced. Questions about user versus device licensing, version compatibility or the install wizard go to support@hypestkey.com or the live chat. Other packs are in the Windows Server CALs category.
Delivery and help
Visa, Mastercard and other cards, Apple Pay, Google Pay, processed by Stripe. Guest checkout, prices in USD.
Instant to email: the key is sent automatically as soon as your payment is confirmed.
Check your spam folder first. Still no email? Write to support@hypestkey.com with your order number and we will resend it.
Windows Server 2022 Remote Desktop Services 50 User CAL: FAQ
How do I install RDS user CALs on Windows Server 2022?
In Remote Desktop Licensing Manager. Right-click the activated license server and select Install licenses. Choose the license program and enter the code. Then pick Windows Server 2022, RDS Per User CAL and quantity 50.
Can I use Windows Server 2022 RDS CALs with Windows Server 2019?
Yes. Newer RDS CALs cover older session hosts. So these work with hosts on 2022, 2019 and 2016. They can't license sessions on Windows Server 2025 hosts.
Which license server version do I need for 2022 RDS CALs?
Windows Server 2022 or later. A license server on 2019 or 2016 can't hold these CALs.
Should I buy user CALs or device CALs?
Depends. User CALs when each person works from their own devices or from several. Device CALs when several people share the same computers in shifts. User CALs need Active Directory for tracking.
Do I still need Windows Server CALs?
Yes. RDS CALs come on top. Every user or device accessing the server needs a Windows Server CAL. The session host needs its own server license too.
What happens before the CALs are installed?
There's a grace period. Microsoft gives 120 days after an RD Session Host is deployed. After that, users need a valid RDS CAL to sign in to a remote session.
What if a 51st person signs in?
Nothing stops them. Per-user CALs aren't enforced, and the license server hands out an overused CAL. That breaches the RDS terms, so check the per-user report in RD Licensing Manager and add a pack when needed.
Something went wrong. What now?
We'll help you fix it. Write to support@hypestkey.com or the live chat with your order number. A code that won't install gets fixed with you or replaced.




