Skip to content 
PC Guides
Windows Server CAL vs RDS CAL Explained
If you’re running Windows Server and need to give users or devices access to it, you need a Client Access License (CAL). There are two distinct types relevant to Remote Desktop: the standard Windows Server CAL and the Remote Desktop Services CAL (RDS CAL). They are not interchangeable — you need both, and confusing them is one of the most common licensing mistakes in small business IT.
What is a Windows Server CAL?
A Windows Server CAL (Client Access License) is a license that grants a user or device the legal right to access Windows Server services — file sharing, print services, Active Directory, and general server resources.
Every user or device that connects to a Windows Server installation requires one. This applies even if the connection is on your internal network, not remote. Microsoft’s licensing model does not include client access in the server license itself — the server license only covers the server hardware.
What is an RDS CAL?
An RDS CAL (Remote Desktop Services Client Access License) specifically licenses the right to use Remote Desktop Services to connect to a Windows Server session. This is what allows users to log in remotely to a full Windows desktop or RemoteApp running on the server.
RDS CALs are an additional requirement on top of the standard Windows Server CAL — not a replacement for it. Think of it as a two-layer licensing requirement:
- Layer 1 — Windows Server CAL: grants access to the server
- Layer 2 — RDS CAL: grants the right to use Remote Desktop to access it
Without an RDS CAL, Windows Server only allows two simultaneous administrative remote desktop connections by default (for IT management purposes). Additional connections require RDS CALs.
Device CAL vs User CAL — which do you need?
Both Windows Server CALs and RDS CALs come in two forms: Device CAL and User CAL. Choosing the right one depends on how your organization works.
| Device CAL | User CAL | |
|---|---|---|
| Covers | One specific device | One specific user |
| Multiple users on same device | ✓ Covered by one CAL | ✗ Each user needs own CAL |
| User connecting from multiple devices | ✗ Each device needs own CAL | ✓ Covered by one CAL |
| Best for | Shift workers, shared terminals, kiosks | Remote workers, BYOD, roaming staff |
Full comparison: Windows Server CAL vs RDS CAL
| Windows Server CAL | RDS CAL | |
|---|---|---|
| What it licenses | Access to Windows Server services | Remote Desktop session access |
| Required for internal network access | Yes | No |
| Required for Remote Desktop access | Yes (both needed) | Yes (both needed) |
| Replaces the other | ✗ No | ✗ No |
| Available as Device or User CAL | ✓ Yes | ✓ Yes |
Practical example: 10-person office with remote access
Say you have a 10-person team, each using their own laptop, who need to remote into a Windows Server 2025 machine to access shared applications:
- You need: 1× Windows Server 2025 license (for the server hardware)
- You need: 10× Windows Server 2025 User CALs (one per user accessing server services)
- You need: 10× Windows Server 2025 RDS User CALs (one per user connecting via Remote Desktop)
Skip the RDS CALs and Windows Server will only allow 2 simultaneous remote desktop connections — enough for IT admins, not for your whole team.
View Windows Server 2025 RDS CAL →Windows Server 2025 CAL licensing — what’s changed
Windows Server 2025 follows the same CAL model as 2019 and 2022. There is no per-core CAL model — the core licensing applies to the server itself, and per-user or per-device CALs apply to client access. CALs from older server versions (2019, 2022) are backward compatible but not forward compatible — a 2019 CAL does not cover access to a 2025 server.