Windows Server 2025 RDS Device CAL Key

What is included in Windows Server 2025 RDS Device CAL?

Per-Device License – Licenses one device for any number of users.
Remote Session Rights – Authorizes Remote Desktop Session Host connections to the server.
Shared-Device Coverage – Ideal for shift workstations used by many staff.
License Tracking – Issued and tracked by the RD Licensing server.
Workgroup Support – Device CALs work without Active Directory membership.
Important – A separate Windows Server CAL and base Server license are still required.
Core Capacity – One Device CAL covers exactly one connecting device.

What are the main benefits of Windows Server 2025 RDS Device CAL?

The Windows Server 2025 RDS Device CAL grants one physical device the right to open Remote Desktop sessions on a Windows Server 2025 Remote Desktop Session Host. It is the cost-effective choice when several people share the same machine, because the license stays with the device rather than the person.

Cost Control – Cheaper when devices are fewer than users.
Shift Friendly – One CAL covers multiple users per terminal.
Enforced Compliance – Device CALs are electronically tracked and capped.
No AD Required – Usable in workgroup setups without a domain.
Partial Revocation – Up to 20% of device CALs can be revoked.
Backward Access – 2025 CALs also reach 2022, 2019, and 2016 hosts.

What does the Windows Server 2025 RDS Device CAL do?

It gives a single device permission to start Remote Desktop Services sessions on a Windows Server 2025 host running the Session Host role. When that device connects for the first time it receives a temporary CAL valid for 90 days; on the second connection the licensing server upgrades it to a permanent CAL that renews automatically on a 52 to 89 day cycle. The CAL is installed and managed through the Remote Desktop Licensing Manager on an RD Licensing server. This is the license that keeps remote sessions working after the server's built-in 120-day grace period ends.

What is the difference between a Device CAL and a User CAL for RDS?

A Device CAL is assigned to a specific machine and lets any number of users on that machine open remote sessions, while a User CAL follows one person across all their devices. Device CALs are electronically enforced, so once every installed CAL is in use the next device is refused a connection; User CALs are not enforced and rely on the administrator staying compliant. Device CALs also allow up to 20% to be revoked and can be tracked in a workgroup, whereas User CALs cannot be revoked and cannot be tracked outside Active Directory. Choose Device CALs when you have more users than shared devices, such as shift-based terminals or kiosks.

Does the RDS Device CAL replace a standard Windows Server CAL?

No. The RDS Device CAL is an additive license that sits on top of a standard Windows Server CAL, not a replacement for it. The standard Windows Server CAL covers basic access to the server such as file, print, and authentication services, while the RDS CAL specifically authorizes Remote Desktop session access. Each connecting device therefore needs both a Windows Server CAL and an RDS Device CAL, plus the underlying Windows Server 2025 license. Buyers often assume the RDS CAL alone is enough, which leads to compliance gaps during a Microsoft audit.

Which Windows Server versions does the 2025 RDS Device CAL support?

A Windows Server 2025 RDS Device CAL connects to a 2025 Session Host and is also backward compatible with 2022, 2019, and 2016 hosts. The rule does not work in reverse: older RDS CALs such as 2022 or 2019 cannot connect to a 2025 Session Host, so a 2025 host always requires 2025 CALs. The CAL must also be installed on an RD Licensing server running Windows Server 2025 or later, since a 2022 licensing server cannot host 2025 CALs. This matters when you upgrade the host before upgrading the licensing server, a common ordering mistake during migrations.

Do you still need RDS CALs with Citrix, Parallels, or Azure?

Yes. The RDS CAL requirement comes from Microsoft and applies whenever a device connects to a Windows Server running the Session Host role, regardless of which tool brokers the connection. Citrix, Parallels RAS, and similar third-party products do not include or replace the RDS CAL. In Azure the base Windows Server license is covered by the platform, but RDS CALs remain a separate requirement when the Session Host role is enabled. Plan for these CALs in any virtualized or hosted remote desktop project, not just on-premises servers.