Revoking Per-Device RDS CALs
Understanding the complexities of revoking Client Access Licenses in Windows Server.
Revoking per-device Remote Desktop Services (RDS) Client Access Licenses (CALs) can be a complex and often misunderstood process in a Windows Server environment. The key takeaway is that direct revocation of a single per-device CAL is not always possible or straightforward.
⚠️ The Challenge with Revocation:
You cannot directly revoke an RDS CAL that has been issued. Once a per-device CAL is issued to a client, it is permanently assigned for a set period, typically 52-89 days, before it's automatically renewed upon the next connection. This design prevents administrators from reusing CALs for different devices frequently, which is a violation of the licensing terms.
Method 1: Limited Revocation via RD Licensing Manager
In certain Windows Server versions, it is possible to revoke a small percentage of per-device CALs using the Remote Desktop Licensing Manager console (licmgr.exe).
The General Process:
- Open the RD Licensing Manager:
- On the license server, open Server Manager.
- Go to Tools > Remote Desktop Services > Remote Desktop Licensing Manager
- Locate the CALs:
- In the console tree, expand the server and the license pack you want to manage.
- You will see a list of issued licenses, including the devices they are assigned to.
- Revoke the License:
- Right-click the specific device you want to revoke the license from.
- Select Revoke License.
Important Considerations:
- This option is not always available or may be greyed out.
- This method is limited to a small percentage (e.g., 20%) of your total CALs.
- This method works better on older Windows Server versions.
Method 2: The "Wait and Expire" Method
The most reliable and officially sanctioned method for reclaiming a per-device CAL is to simply let it expire.
- When a device no longer connects to the RDS environment, its assigned CAL will not be renewed.
- It will eventually expire, making it available for a new device.
The RDS licensing server automatically manages this process, so no manual intervention is required. This is the intended behaviour and the simplest way to maintain licensing compliance.
Author Bio
Microsoft Certified Professional
With over 20 years of experience deploying and managing enterprise Windows Server environments, Keloth leads technical implementation at RDS CAL Store. He specializes in Remote Desktop Services infrastructure, secure remote architecture, and helping IT teams seamlessly scale their official licensing.
Related Posts
Understanding RDS CAL Downgrade Rights
Home – Understanding RDS CAL Downgrade Rights Understanding RDS CAL Downgrade Rights When managing a Remote Desktop Services environment, hardware and software upgrades rarely happen all at once. You might purchase new Client Access Licenses (CALs) today, but still need them to authorize connections to older servers running in your datacenter. Microsoft accommodates this reality…
How to Disable Remote Desktop Easy Print in Windows Server (2016-2025)
Home – How to Disable Remote Desktop Easy Print in Windows Server (2016-2025) How to Disable Remote Desktop Easy Print in Windows Server (2016-2025) Remote Desktop Easy Print is the default driver Windows uses to map local client printers into a remote session. While convenient, it strips away advanced printer features (like stapling, tray selection,…
How to Create a Remote Desktop User in Windows Server (2016, 2019, 2022 & 2025)
Home – How to Create a Remote Desktop User in Windows Server (2016, 2019, 2022 & 2025) How to Create a Remote Desktop User in Windows Server (2016, 2019, 2022 & 2025) Provisioning remote access for a new employee requires more than just creating a standard Windows account. To securely connect to a Session Host,…
How to Fix the CredSSP “Encryption Oracle Remediation” RDP Error
Home – How to Fix the CredSSP “Encryption Oracle Remediation” RDP Error How to Fix the CredSSP “Encryption Oracle Remediation” RDP Error If you are managing Windows Servers, you have likely encountered this terrifying error message when trying to connect via Remote Desktop: “An authentication error has occurred. The function requested is not supported… This…
