<h2 style="margin-top: 0px; margin-bottom: 10px;">What is included in Microsoft Server 2022 RDS Device CAL?</h2>
<p style="margin-top: 0px; margin-bottom: 0px;"><strong>Device-based licensing</strong> – Covers one device used by many users.<br /><strong>Remote session access</strong> –Legalizes RDP sessions to a 2022 session host.<br /><strong>Shift-friendly model</strong> – Ideal when staff share the same machines.<br /><strong>License server tracking</strong> – Issued and counted by RD Licensing Manager.<br /><strong>Backward compatibility</strong> – Also connects to 2019 and 2016 hosts.<br /><strong>Important</strong> – This is an add-on; base Server CALs are not included.<br /><strong>Core Capacity</strong> – One Device CAL permits unlimited users per licensed device.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">What are the main benefits of Microsoft Server 2022 RDS Device CAL?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">The RDS Device CAL is the access license that makes Remote Desktop sessions to a Windows Server 2022 session host compliant. It is assigned to a physical device, so any number of users signing in from that machine are covered by a single CAL.<br /><br /><strong>Cost control</strong> – Fewer licenses when devices outnumber the users.<br /><strong>Shared workstations</strong> – Fits shop floors, kiosks, and shift rotations.<br /><strong>Workgroup support</strong> – Tracked even without Active Directory membership.<br /><strong>Predictable counting</strong> – Device CALs cannot be over-allocated.<br /><strong>Partial recovery</strong> – Up to 20% of device CALs can be revoked.<br /><strong>Downgrade rights</strong> – Usable against 2019 and 2016 session hosts.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">What does the Microsoft Server 2022 RDS Device CAL do?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">It authorizes a specific device to open Remote Desktop Services sessions on a Windows Server 2022 session host, regardless of how many people use that device. Without an RDS CAL, Windows Server only allows two simultaneous administrative remote connections; the CAL is what lets you run real multi-user remote desktop or RemoteApp workloads. The CAL is installed on a Remote Desktop Licensing server, which issues and tracks it through RD Licensing Manager. There is a 120-day grace period during which sessions work before a license server must be in place. This makes it the correct license for thin clients, terminals, and shared PCs rather than for individual roaming users.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">What is the difference between an RDS Device CAL and an RDS User CAL?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">A Device CAL is tied to one machine and covers every user who logs in from it, while a User CAL is tied to one person in Active Directory and follows them across any number of devices. Choose Device CALs when several employees share the same workstations, such as in shift work, and User CALs when each person has their own dedicated devices. Device CALs can be tracked in a workgroup and cannot be over-allocated; User CALs require Active Directory and can be over-allocated, which puts compliance on the administrator. Device CALs also allow up to 20% to be revoked, whereas User CALs cannot be revoked at all. Counting your shared-versus-personal device ratio is the fastest way to pick the cheaper model.</p>
<table style="width: 100%; border-collapse: collapse; background-color: #efefef; margin-top: 15px; margin-bottom: 15px; font-size: 14px; line-height: 1.35;">
<tbody>
<tr><th style="border: 1px solid #ffffff; padding: 9px 8px; text-align: left; font-weight: bold; background-color: #dedede;">Feature</th><th style="border: 1px solid #ffffff; padding: 9px 8px; text-align: center; font-weight: bold; background-color: #dedede;">RDS Device CAL</th><th style="border: 1px solid #ffffff; padding: 9px 8px; text-align: center; font-weight: bold; background-color: #dedede;">RDS User CAL</th></tr>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">Assigned to</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">Device</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">User</td>
</tr>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">Works in workgroup</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;"><span style="color: #32a852; font-size: 24px; font-weight: 800; line-height: 1; display: inline-block; transform: translateY(1px);">✓</span></td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;"><span style="color: #d9534f; font-size: 24px; font-weight: 800; line-height: 1; display: inline-block; transform: translateY(1px);">✕</span></td>
</tr>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">Can be revoked</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">Up to 20%</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;"><span style="color: #d9534f; font-size: 24px; font-weight: 800; line-height: 1; display: inline-block; transform: translateY(1px);">✕</span></td>
</tr>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">Can be over-allocated</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;"><span style="color: #d9534f; font-size: 24px; font-weight: 800; line-height: 1; display: inline-block; transform: translateY(1px);">✕</span></td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;"><span style="color: #32a852; font-size: 24px; font-weight: 800; line-height: 1; display: inline-block; transform: translateY(1px);">✓</span></td>
</tr>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">Best for</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">Shared devices</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">Roaming users</td>
</tr>
</tbody>
</table>
<h3 style="margin-top: 30px; margin-bottom: 10px;">Does the RDS Device CAL replace the standard Windows Server CAL?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">No. The RDS Device CAL is an additional license that only covers Remote Desktop Services access, and it sits on top of the base Windows Server CAL that grants general access to file, print, and directory services. To run a compliant remote desktop deployment you need both: a Server CAL for the underlying access and an RDS CAL for the session host role. This is a frequent buying mistake, because Windows Server 2022 Standard already bundles a small number of base CALs but never includes RDS CALs. Confirm your base CAL coverage separately before ordering RDS Device CALs so you do not under-license the deployment.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">Which Windows Server versions can a 2022 RDS Device CAL connect to?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">A Windows Server 2022 RDS CAL can connect to session hosts running Server 2022, 2019, or 2016, but it cannot connect to a Server 2025 session host. RDS CALs are backward compatible only: a newer CAL reaches older hosts, but an older CAL never reaches a newer host. This matters if you plan to upgrade the underlying server, because moving the session host to Server 2025 would force you to buy 2025 RDS CALs. If your environment is standardized on 2022 or older, the 2022 Device CAL keeps that estate licensed without further purchases. Check your highest session-host version before buying so the CAL version matches.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">What should you check before choosing the RDS Device CAL?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">Confirm that your users share devices rather than each having their own, because the Device model only saves money when devices are fewer than users. You also need a Remote Desktop Licensing server running a compatible Windows Server version to install and issue the CALs through RD Licensing Manager. Remember the 120-day grace period: sessions run during initial setup, but after it expires every connection must hold a valid issued CAL. Verify your separate base Server CAL coverage as well, since the RDS CAL alone does not authorize general server access. For shift-based or kiosk setups, the Device CAL is usually the lower-cost and more predictable choice.</p>