- Spring sale — extra 15% off with code MMK15
- Instant email delivery, 24/7
Windows Server 2025 RDS Services Device CAL is a genuine perpetual license that allows one physical device to securely connect to a Server 2025 RDS Device environment. Ideal for shared workstations, thin clients, kiosks, schools, healthcare, and business environments where multiple users access the same device. This one-time purchase includes lifetime validity, no subscription, and full compatibility with Windows Server 2025 RDS deployments.
You'll receive your license key, an official Microsoft download link, and a 1-page activation guide.
Direct Microsoft activation
Email in under 5 minutes
Real humans, any time zone
Full money-back guarantee
A Windows Server 2025 RDS CAL is the per-device client access license that gives a specific physical device a desktop computer, laptop, thin client, shared workstation, kiosk terminal, or any other endpoint the legal right to connect to a Windows Server 2025 Remote Desktop Session Host and access remote desktops, published applications, and virtualized resources through an RDS session.
Once a Device CAL is assigned to a device, any number of users can connect to the RDS environment from that device without each individual user requiring their own separate license. The license stays with the machine, not with the people who use it.
Remote Desktop Services is the Windows Server role that enables centralized application delivery, virtual desktop infrastructure, and remote desktop access the technology that allows an organization to host applications and desktop sessions on a server and deliver them to users over the network rather than installing and maintaining software on each individual endpoint.
Every device that connects to a Windows Server 2025 Remote Desktop Session Host requires an RDS CAL. Without valid RDS CALs installed on a Remote Desktop Licensing server, the session host enters a 120-day grace period after which remote desktop connections from unlicensed devices stop working entirely. The RDS Device CAL is the license that makes each connecting device compliant and keeps those connections operational indefinitely.
Licensing note: The RDS Device CAL covers remote desktop access only. It does not include the Windows Server 2025 operating system license, which must be purchased separately.
It also does not substitute for the base Windows Server 2025 User or Device CAL required for general server access both a base Windows Server CAL and an RDS CAL are required for devices that connect to a Windows Server 2025 server via Remote Desktop Services. RDS CALs must be installed on a Remote Desktop Licensing server running Windows Server 2025 or a later supported version.
Remote Desktop Services Client Access Licenses come in two forms User CALs and Device CALs and the choice between them is a practical decision based on how users and devices are organized in the environment being licensed.
A Device CAL is assigned to a specific physical device. Once assigned, that device holds the RDS license and any user who sits down at that device can connect to the Remote Desktop Session Host no individual user license is required beyond the device’s CAL. A Device CAL is the right choice when a device is shared by multiple people:
shift workers who rotate through shared workstations, a kiosk terminal in a retail or production environment that any employee accesses, shared thin clients in a call centre or hospital ward, or lab computers used by rotating staff or students. In all of these scenarios, a single Device CAL per endpoint covers every person who uses that device, which is significantly more economical than a User CAL for each individual who might access the system.
A User CAL, by contrast, is assigned to a specific person through their Active Directory account, and covers that person connecting to the RDS environment from any number of devices their office desktop, their laptop, their home computer, a mobile device, or any other endpoint they use. User CALs are the right choice for workers who access the RDS environment from multiple devices:
remote workers who use a laptop at home and a desktop in the office, traveling employees who access the system from different locations, or any user whose connection patterns span multiple endpoints.
The choice between Device CALs and User CALs is made per environment based on the ratio of devices to users. When each device is used by more than one person when there are fewer devices than people who use them Device CALs are almost always the more cost-effective option. When each person accesses the system from more than one device when there are more devices than users User CALs are typically more economical.
Many organizations use a combination of both types within the same RDS deployment, assigning Device CALs to shared workstations and User CALs to individual named users, with the Remote Desktop Licensing server managing both simultaneously.
Remote Desktop Services is the Windows Server role suite that Microsoft has built and refined across more than two decades of enterprise deployment, and it remains the foundation of centralized application delivery and remote desktop access in Windows environments.
Its core components are the Remote Desktop Session Host the server that hosts the actual desktop sessions and applications that users connect to and the Remote Desktop Licensing server which stores, issues, and tracks RDS CALs for every device or user that connects.
The Remote Desktop Session Host is what most administrators think of when they think of RDS it is the role that runs multiple simultaneous Windows desktop sessions on a single server, allowing many users to work concurrently in isolated sessions from their own endpoint devices.
Applications installed on the session host are available to every connected user without being installed locally on their devices, which means software can be deployed, updated, and managed centrally on the server rather than individually on each endpoint. A line-of-business application that previously required installation and maintenance across fifty individual workstations can instead be installed once on the session host and delivered to all fifty users through RDS, with updates applied in a single operation on the server.
Remote Desktop Web Access publishes applications and desktops to an internal or external web portal, allowing users to launch remote sessions from a browser without requiring them to open the Remote Desktop Connection client manually.
Remote Desktop Gateway provides secure, encrypted remote access to the RDS environment over HTTPS without requiring a VPN, allowing authorized users to connect from outside the organization’s network through a standard HTTPS connection on port 443. Remote Desktop Virtualization Host enables session-based or VM-based virtual desktop infrastructure where each user connects to their own dedicated virtual machine rather than sharing a session host with other users.
Every device that connects to any of these components the session host, the gateway, the web access portal in a way that results in a session host connection requires a valid RDS CAL. Microsoft enforces this through the Remote Desktop Licensing server, which the session host contacts when a new device or user connects to determine whether a valid CAL is available. If a CAL is available, the connection proceeds and the license is issued.
If no CAL is available, the connection is refused once the grace period has expired. Installing RDS CALs on the licensing server is the act of making those licenses available for the session host to issue to connecting devices.
The Device CAL model is purpose-built for environments where multiple users share a smaller number of physical access points the scenario that describes a significant proportion of enterprise, healthcare, manufacturing, retail, and education RDS deployments.
In a hospital, nurses and physicians may each log into shared workstations at nursing stations, examination rooms, and administrative desks throughout a shift. The number of workstations is far smaller than the number of staff who access them. A Device CAL on each workstation covers every clinician who uses that station, regardless of how many different people log in across a day.
Licensing by user in the same environment would require a User CAL for every clinician, technician, and administrator who accesses the RDS environment potentially hundreds more licenses than the number of shared workstations that actually connect.
In a manufacturing plant, production line terminals and quality control workstations may be used by rotating shift workers around the clock. Three shifts across five workstations means many individual users sharing five endpoints. Five Device CALs cover the entire production environment, where User CALs would require one for each worker.
In a call centre, operators share terminals across shifts. In a retail environment, point-of-sale and back-office terminals are accessed by multiple employees throughout the day.
In an educational institution, computer lab workstations are used by any student enrolled in the relevant program. In all of these environments, Device CALs align the license cost with the actual number of access points rather than the total population of potential users, which is the economically correct licensing model for shared-device environments.
Perpetual License No Subscription, No Renewal Windows Server 2025 RDS Device CALs are perpetual licenses. They do not expire, do not require annual renewal, and do not carry a recurring subscription cost. Once purchased and installed on the Remote Desktop Licensing server, they issue to connecting devices and remain valid for the supported lifetime of the Windows Server 2025 RDS Device environment, including any eligible downgrade use for older session hosts in the same deployment. For organizations that have standardized on Windows Server 2025 and plan to run their RDS infrastructure for the full support lifecycle through 2034, perpetual RDS Device CALs purchased today remain valid through that entire period without additional cost.
Version-Specific Compatibility with Downgrade Rights RDS CALs are version-specific in the forward direction and backward-compatible in the downgrade direction. Windows Server 2025 RDS Device CALs can be used to license connections to session hosts running Windows Server 2025, 2022, 2019, and 2016 any version equal to or older than the CAL version.
Windows Server 2022 RDS CALs cannot be used to license connections to a Windows Server 2025 session host. This means organizations purchasing Windows Server 2025 RDS Device CALs today are purchasing the most flexible perpetual RDS CAL available compatible with their current Windows Server 2025 deployment and valid for any older Windows Server session hosts still in the environment, without needing to maintain separate CAL pools for different server versions.
Device CAL vs User CAL Choosing the Right Model The practical selection rule for most environments is straightforward. Count the number of devices that will connect to the RDS environment. Count the number of users who will connect to the RDS environment. If devices outnumber users if each person typically uses more than one device User CALs are likely more economical.
If users outnumber devices if multiple people share each connecting endpoint Device CALs are likely more economical. For environments with a mix of shared and individual-use devices, both CAL types can be deployed simultaneously within the same RDS licensing infrastructure, with the Remote Desktop Licensing server managing the two pools independently.
Managed by Remote Desktop Licensing Server RDS CALs are not installed on client devices and are not tracked on individual workstations. They are installed on a Remote Desktop Licensing server a Windows Server running the Remote Desktop Licensing role which the session host contacts automatically when a new device connects to determine whether a valid CAL is available.
The licensing server issues the CAL to the connecting device, records the issuance, and tracks CAL usage across the deployment. This centralized management means that IT administrators have a single point for monitoring CAL consumption, identifying when additional CALs need to be purchased as the device count grows, and ensuring compliance without per-device management overhead.
Grace Period Behavior When a Remote Desktop Session Host is first deployed without a configured Remote Desktop Licensing server, or when the licensing server has no remaining CALs to issue, Windows Server provides a 120-day grace period during which connections are permitted without a valid CAL.
This grace period exists to allow administrators time to configure the licensing infrastructure after initial deployment, not as a substitute for proper licensing. Once the grace period expires, the session host refuses connections from devices that have not been issued a valid CAL. Purchasing and installing RDS Device CALs on the licensing server before the grace period expires or immediately upon initial RDS deployment is the correct approach to avoid connection disruption.
RDS CAL Does Not Include Base Server Access Rights The RDS Device CAL specifically covers the right to access Remote Desktop Services on the session host. It does not cover general access to the Windows Server 2025 server’s other resources and services file shares, Active Directory, print services, and so on.
Base Windows Server 2025 User or Device CALs are required separately for general server access. An organization deploying Windows Server 2025 for Remote Desktop Services requires both a base Windows Server 2025 CAL (User or Device) and an RDS CAL (User or Device) for each connecting user or device. The two license types are complementary and both are required the RDS CAL does not subsume or replace the base server CAL requirement.
Installing RDS CALs requires a Remote Desktop Licensing server with the Remote Desktop Licensing role installed and activated. The Remote Desktop Session Host must be configured to point to the licensing server so that it can request CALs when devices connect.
Step 1 — Install the Remote Desktop Licensing role Open Server Manager on the server that will act as the license server. Click Manage, then Add Roles and Features. Select Remote Desktop Services installation, and then select Remote Desktop Licensing as the role to install. Complete the role installation wizard.
Step 2 — Activate the Remote Desktop Licensing server Open Remote Desktop Licensing Manager from Server Manager under Tools. Right-click the license server and select Activate Server. The Activate Server Wizard guides the process of registering the licensing server with Microsoft’s activation service, either automatically over the internet or manually by phone or web browser for servers without internet access.
Step 3 — Install the RDS CALs In Remote Desktop Licensing Manager, right-click the activated license server and select Install Licenses. Enter the product key provided by MMKeys when prompted. Select Windows Server 2025 as the product version and Remote Desktop Services Per Device as the license program. Complete the wizard. The CALs are now installed on the licensing server and available for issuance to connecting devices.
Step 4 — Configure the session host to use the licensing server On the Remote Desktop Session Host, open Group Policy Editor or use the Remote Desktop Session Host Configuration tool to specify the address of the Remote Desktop Licensing server. The session host will contact the licensing server automatically when devices connect and issue CALs from the installed pool.
Full installation and configuration instructions are included with every MMKeys order. Our support team is available 24 hours a day, 7 days a week for assistance with any stage of the licensing server setup or CAL installation process.
Any organization deploying Windows Server 2025 Remote Desktop Services where connecting endpoints are shared among multiple users, or where the number of users exceeds the number of connecting devices, should evaluate Device CALs as the primary or supplementary licensing model for their RDS deployment.
Healthcare organizations where shared workstations at nursing stations, examination rooms, and administrative desks are accessed by rotating clinical staff throughout each shift, where the number of workstations is substantially smaller than the total clinical and administrative headcount that accesses the RDS environment.
Manufacturing and production environments where shop floor terminals, quality control stations, and warehouse management workstations are used by rotating shift workers around the clock, where a small number of fixed endpoints serves a much larger workforce across multiple shifts.
Call centres, contact centres, and customer support operations where agents share terminal equipment across shifts and the number of operator seats is fixed while the number of agents who use them varies with shift patterns and staffing levels.
Retail and hospitality environments where back-office workstations, point-of-service terminals, and manager workstations are accessed by multiple employees throughout the operating day, and where purchasing a User CAL for every employee who might access a system would significantly exceed the cost of Device CALs for the actual terminal count.
Educational institutions where computer lab workstations, library terminals, and shared student computing resources are accessed by any enrolled student and licensing by device rather than by the full student population is the economically rational approach.
Branch offices and remote sites where a small number of shared workstations provide access to centrally hosted applications through RDS, where the device count at the branch is known and fixed while the number of individuals who use those workstations may vary.
IT departments managing mixed RDS environments where some users have dedicated workstations and others share endpoints, and where a combination of Device CALs for shared endpoints and User CALs for named individual users provides the most cost-effective compliance posture across the full deployment.
What does the RDS Device CAL cover? The RDS Device CAL gives a specific physical device the right to connect to a Windows Server 2025 Remote Desktop Session Host. Any number of users can access the RDS environment from that device using its Device CAL. It does not cover the Windows Server 2025 operating system license or the base Windows Server 2025 User or Device CAL both of those must be purchased separately.
Do I need both a Windows Server CAL and an RDS CAL? Yes. A base Windows Server 2025 User or Device CAL is required for general server access. The RDS Device CAL is required additionally for Remote Desktop Services access. Both are required for devices that connect to Windows Server 2025 via Remote Desktop Services. The base CAL covers access to the server’s general services. The RDS CAL covers the additional right to use Remote Desktop Services specifically.
Can I mix Device CALs and User CALs in the same RDS deployment? Yes. The Remote Desktop Licensing server supports both CAL types simultaneously. Organizations can assign Device CALs to shared endpoints and User CALs to individual named users within the same licensing infrastructure, with the licensing server managing both pools independently and issuing the appropriate CAL type based on the connection.
Are Windows Server 2025 RDS CALs backward compatible? Yes. Windows Server 2025 RDS Device CALs can be used to license connections to session hosts running Windows Server 2025, 2022, 2019, and 2016. Older RDS CALs Windows Server 2022 RDS CALs, for example cannot be used to license connections to a Windows Server 2025 session host. Purchasing 2025 CALs provides maximum flexibility across mixed-version server environments.
Do RDS Device CALs expire? No. Windows Server 2025 RDS Device CALs are perpetual licenses that do not require annual renewal or subscription payments. Once purchased and installed on the licensing server, they remain valid indefinitely for the Windows Server 2025 RDS Device environment.
What happens if I run out of RDS CALs? When the licensing server has no remaining CALs to issue, new devices attempting to connect to the session host will be refused once any existing temporary CAL grace period has elapsed. Monitor CAL consumption in Remote Desktop Licensing Manager and purchase additional CALs before the pool is exhausted as the device count grows.
What is the grace period for RDS? Windows Server 2025 Remote Desktop Session Hosts provide a 120-day grace period after the RDS role is installed, during which connections are permitted without valid CALs. The grace period is intended to allow time for licensing server configuration after initial deployment not as a long-term substitute for proper licensing. CALs should be purchased and installed before the grace period expires.
How many Device CALs do I need? One Device CAL per physical device that connects to the Remote Desktop Session Host. If fifteen shared workstations connect to the session host, fifteen Device CALs are required, regardless of how many users access those workstations. If the device count grows, additional Device CALs must be purchased to maintain compliance.
How soon will I receive my CAL key after purchase? Most MMKeys orders are delivered within minutes of payment confirmation, 24 hours a day, 7 days a week. Your email includes the product key and full installation instructions.
What if my CAL key does not activate? Contact MMKeys support at any time. Every license sold by MMKeys is backed by our lifetime warranty and money-back guarantee. If your key does not activate for any reason, we will resolve the issue or provide a replacement at no cost. CONTACT US
