What is included in Microsoft Server 2019 RDS Device CAL?

Remote session right – Lets a device open a Remote Desktop session.
Per-device model – Licenses the machine, not the person.
Shared device use – Any user may connect from that device.
License server tracking – Issued and counted by RD Licensing.
Backward compatible – Also reaches 2016 session hosts.
Core Capacity – Cannot connect to 2022 or newer session hosts.

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

An RDS Device CAL grants one device the right to start Remote Desktop sessions on a Windows Server 2019 RD Session Host. It is licensed per machine, so any user sitting at that device is covered.

Shift friendly – One CAL covers all users per device.
Predictable counting – Tied to fixed, known endpoints.
Workgroup capable – Tracks even without Active Directory.
Lifts session cap – Removes the two-connection administrative limit.
Reusable pool – Up to 20% can be revoked.
Edition neutral – Works on Standard and Datacenter alike.

What does the Server 2019 RDS Device CAL do?

It gives a physical device the legal right to run Remote Desktop Services sessions on a Windows Server 2019 RD Session Host. A Windows Server installation only permits two administrative Remote Desktop connections on its own; once you install the RD Session Host role, every additional connecting device needs an RDS CAL. The CAL is installed on an activated RD Licensing server, which issues a temporary license on a device's first connection and a permanent one on the second. This model is built for shared hardware, where several staff use the same terminals across shifts.

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

A Device CAL licenses one machine for unlimited users, while a User CAL licenses one person for unlimited devices. Choose Device CALs when more people than devices connect, such as a call center where three shift workers share two terminals; you would buy two Device CALs instead of three User CALs. Device CALs are physically assigned to the endpoint and can be tracked in a workgroup, whereas User CALs are assigned in Active Directory and are not enforced by the license server. You can mix both types in one deployment, but using a single model keeps auditing far simpler.

Do I still need a Windows Server CAL as well?

Yes, in most setups an RDS CAL does not replace the base Windows Server CAL; the two cover different things. The standard Windows Server CAL authorizes basic network access such as file, print, and authentication services, while the RDS CAL specifically authorizes the Remote Desktop session on top of that. So a device connecting to apps published from a 2019 RD Session Host typically needs both a Windows Server Device CAL and an RDS Device CAL. Skipping the base CAL leaves the deployment out of compliance even if remote sessions appear to work.

Which Windows Server versions can a 2019 RDS CAL connect to?

A 2019 RDS CAL works with Windows Server 2019 and 2016 session hosts, but it cannot connect to a 2022 or newer RD Session Host. RDS CALs are backward compatible but never forward compatible, so the CAL version must match or exceed the server version it serves. If you plan to move session hosts to Windows Server 2022 later, a 2019 CAL will not carry over and you would need to buy 2022 CALs. The CAL itself is not edition-specific, so the same 2019 Device CAL is valid against Standard, Datacenter, or Essentials session hosts.

How many RDS Device CALs do I need?

You need one RDS Device CAL for each distinct device that opens a Remote Desktop session, regardless of how many people use that device. For example, 20 thin clients used by 60 rotating staff require 20 Device CALs, not 60. The license server enforces this count under the Per Device model and will not over-allocate, unlike the Per User model where tracking relies on the administrator. Count the actual connecting endpoints rather than headcount before buying, since the device total is what determines compliance.

What should you check before choosing the 2019 RDS Device CAL?

Confirm that your RD Session Host runs Windows Server 2019 or 2016, because a 2019 CAL cannot serve a 2022 or later host. Verify whether your environment has more devices than users; if people roam across many devices, User CALs are usually the cheaper and cleaner fit. Also confirm you have an activated RD Licensing server, since the CAL must be installed there to be issued past the 120-day grace period. Finally, plan for a separate Windows Server CAL, which the RDS CAL does not include.

Frequently asked questions about Microsoft Server 2019 RDS Device CAL

Does the RDS Device CAL require a license server?

Yes. After a 120-day grace period, connections need a valid RDS CAL issued by an activated RD Licensing server. The Device CAL is installed on that server, which then issues a temporary license on first connect and a permanent one on the second connect.

Can a 2019 RDS Device CAL be reassigned to another device?

Partly. Under the Per Device model, the license server lets you revoke up to 20% of issued Device CALs to reclaim them for replacement hardware. This helps when a device is retired, but it is not a way to cover more devices than CALs you own.

Does the Device CAL work without Active Directory?

Yes. The Per Device model can issue and track licenses in a workgroup with no domain, which is one practical reason to pick Device over User CALs in small or non-domain setups. The Per User model cannot be reliably tracked in a workgroup.