<h2 style="margin-top: 0px; margin-bottom: 10px;">What is included in Microsoft Server 2022 Device CAL?</h2>
<p style="margin-top: 0px; margin-bottom: 0px;"><strong>Device-based access</strong> – Licenses one device for any user logging in.<br /><strong>Core server services</strong> – Covers file shares, printing, and Active Directory.<br /><strong>Shared-device coverage</strong> – Unlimited users per licensed physical device.<br /><strong>Backward compatibility</strong> – Works with 2016, 2019, and 2022 servers.<br /><strong>Per-device counting</strong> – One CAL per endpoint, not per person.<br /><strong>Important</strong> – Remote Desktop (RDS) access and the server OS license are not included.<br /><strong>Core Capacity</strong> – Grants standard server access only, never Remote Desktop sessions.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">What are the main benefits of Microsoft Server 2022 Device CAL?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">A Device CAL is the client access license that legally permits one device to use Windows Server 2022 services such as file, print, and directory access. It is bought in addition to the server license and is counted per device rather than per user.<br /><br /><strong>Lower seat cost</strong> – Cheaper when many people share few machines.<br /><strong>Shift-friendly licensing</strong> – One license covers round-the-clock device rotation.<br /><strong>Simple device count</strong> – Match licenses to physical endpoints, not headcount.<br /><strong>Mixed-version use</strong> – Same CALs cover older 2016 and 2019 servers.<br /><strong>Predictable compliance</strong> – Fixed endpoints make audit preparation straightforward.<br /><strong>Perpetual rights</strong> – Stays valid for the Server 2022 version it covers.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">What does a Windows Server 2022 Device CAL actually do?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">A Device CAL grants one specific device the right to access Windows Server 2022 services, and any number of users on that device are then covered. The server license alone only permits installing the operating system; it does not legally authorize clients to connect to file shares, printers, or Active Directory. Microsoft requires a CAL for every device that accesses those services in Standard and Datacenter editions. This makes the Device CAL the piece that turns an installed server into one your endpoints can lawfully use. It does not grant Remote Desktop access, which needs a separate RDS CAL.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">What is the difference between a User CAL and a Device CAL?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">A User CAL licenses one person across unlimited devices, while a Device CAL licenses one device for unlimited users. The practical rule is to license whichever number is smaller in your environment. Device CALs win when several people share a fixed set of machines, such as call centers, factory floors, healthcare stations, or 24/7 shift operations. Five staff rotating through one kiosk need a single Device CAL, not five User CALs. Microsoft lets you mix both types, but keeping one model per population makes audits and seat planning far simpler.</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;">Device CAL</th><th style="border: 1px solid #ffffff; padding: 9px 8px; text-align: center; font-weight: bold; background-color: #dedede;">User CAL</th></tr>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">Licensed unit</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">Per device</td>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: center; vertical-align: middle;">Per user</td>
</tr>
<tr>
<td style="border: 1px solid #ffffff; padding: 8px; text-align: left; font-weight: bold; vertical-align: middle;">Unlimited users per device</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;">Unlimited devices per user</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 shared/shift devices</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;">Grants Remote Desktop (RDS) access</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: #d9534f; font-size: 24px; font-weight: 800; line-height: 1; display: inline-block; transform: translateY(1px);">✕</span></td>
</tr>
</tbody>
</table>
<h3 style="margin-top: 30px; margin-bottom: 10px;">Does this Device CAL let users connect through Remote Desktop?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">No. A standard Windows Server 2022 Device CAL covers basic server services like file, print, and Active Directory, but it does not authorize Remote Desktop sessions. Any regular end-user access over RDP requires a separate Remote Desktop Services (RDS) CAL on top of this license. Windows Server includes only two administrative remote connections, which are meant for server maintenance, not daily user work. If your team logs into a session host or jump box, budget for RDS CALs as well, or those connections will be out of compliance.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">Will a 2022 Device CAL work with older Windows Server versions?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">Yes. Windows Server CALs are backward compatible, so a 2022 Device CAL also covers access to Windows Server 2019 and 2016 servers. They are not forward compatible, meaning a 2022 CAL cannot be used to access a Windows Server 2025 server. This matters in mixed environments: you can standardize on 2022 CALs and stay compliant against older servers without buying separate licenses for each version. Always match the CAL version to the highest server version your devices will reach.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">What should buyers check before choosing Device CALs?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">Confirm whether your environment is device-centric or user-centric, because that decides which CAL type costs less. Count physical endpoints accessing the server against the number of distinct people: if you have 30 shared workstations used by 100 rotating staff, 30 Device CALs cover everyone. The CAL is separate from the Windows Server core license, which itself carries a 16-core minimum per server. Also verify that no one needs Remote Desktop access through these devices, since that requires additional RDS CALs not covered here.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">Frequently asked questions about Microsoft Server 2022 Device CAL</h3>
<h3 style="margin-top: 30px; margin-bottom: 10px;">Is the Windows Server operating system included with a Device CAL?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">No. A CAL is an access license only and does not include the server software. You need a separate Windows Server 2022 license, which is sold per core with a 16-core minimum per server, plus enough CALs to cover the devices that connect.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">Can I mix Device CALs and User CALs on the same server?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">Yes, Microsoft permits both types in the same environment. In practice it is cleaner to assign Device CALs to shared shift machines and User CALs to staff who roam between devices, keeping each population on a single model for simpler compliance.</p>
<h3 style="margin-top: 30px; margin-bottom: 10px;">How many Device CALs do I need?</h3>
<p style="margin-top: 0px; margin-bottom: 0px;">You need one Device CAL for every physical device that accesses the server, regardless of how many people use it. Thirty shared workstations require thirty Device CALs even if hundreds of employees rotate across them on different shifts.</p>