Do I need both a Windows CAL and an RDS CAL?
Last reviewed by the MSLicenseHub Licensing Desk.
Yes. Every Remote Desktop Services user or device needs both: a Windows Server CAL (for the underlying OS authentication) and an RDS CAL (for the Remote Desktop session). This is one of the most common compliance misses in audits — teams remember the RDS CAL and forget the base Windows CAL.
The two CALs are independent — you can buy User CALs on the Windows side and Device CALs on the RDS side, or any other combination, as long as the count works out for that user or device.
Apply this to your deployment
- Server CAL
- RDS CAL
- Version alignment
RDS User or Device CALs are additional to the underlying Windows Server access rights. Match the CAL version to the session host: an older RDS CAL cannot license access to a newer host. Check licensing-server compatibility and the deployment mode separately.
Decision checklist
| Check | What to record |
|---|---|
| Product and version | Record the full name, edition, version and part number in the quote. |
| Scope of use | Identify the user, device or deployment; count only the metric applicable to this product. |
| Evidence and support | Retain the agreement, invoice and support lifecycle date; perpetual licensing does not mean perpetual support. |
Official Microsoft terms and licensing guidance · Product support lifecycle
Practical checklist
- Every user or device that connects to a Remote Desktop Session Host needs a Windows Server CAL for base server access and an RDS CAL for the remote desktop functionality.
- RDS CALs must match or exceed the Windows Server version of the session hosts (an RDS 2019 CAL cannot serve 2022 or 2025 hosts).
- Install RDS CALs on an RD Licensing server and set the licensing mode (Per User or Per Device) to match what you bought.
- Remote administration of the server by up to two admins does not need RDS CALs.
Common mistakes to avoid
- Counting concurrent sessions instead of the users or devices that have access.
- Buying RDS CALs but forgetting the underlying Windows Server CALs.
- Leaving the deployment in the 120-day grace period without a configured licence server.
Official source: Microsoft documentation. Licensing terms change; confirm against the current Product Terms before buying.
Still unsure?
Talk to a licensing specialist for a written, signed quote tailored to your environment.
Contact sales