Rds Cal License Registry Key !!hot!! -

Title

RDS CAL License Registry Key — Detailed Review and Guidance

Error 2: "Value cannot be deleted" – The Key Reappears

This happens when the RDS service is running. You must stop TermService before certain deletions, especially GracePeriod.

Part 6: Best Practices for Registry Management of RDS CALs

  1. Prefer PowerShell over Regedit
    Use Set-ItemProperty or New-ItemProperty to reduce mistakes. Example:

    New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM" -Name "SpecifiedLicenseServers" -PropertyType MultiString -Value "licserv.domain.com"

  2. Document Every Change
    Save screenshots or .reg exports before each edit. rds cal license registry key

  3. Use Group Policy for Production
    Instead of manually editing SpecifiedLicenseServers, set the policy “Use the specified license servers” via GPO. Registry edits should only be temporary.

  4. Monitor Event Logs
    After registry edits, check Event Viewer → Applications and Services Logs → Microsoft → Windows → TerminalServices-Licensing → Operational.

  5. Never Delete the Entire RCM Key
    Doing so will completely break Remote Desktop Services, requiring a repair installation or full server rebuild. Title RDS CAL License Registry Key — Detailed

Common Administrative Tasks Involving the Registry

  1. Verify licensing mode: confirm LicensingMode matches intended deployment (Per User vs Per Device).
  2. Pointing session hosts to license servers: confirm LicenseServers contains correct entries.
  3. Clearing corrupted client CALs: on RDP client machines, delete MSLicensing keys to remove stale license caches (requires admin rights); then reconnect to reissue.
  4. Grace period troubleshooting: inspect GracePeriod to determine whether the temporary licensing grace period exists or was reset.
  5. Repairing licensing service: check TermServLicensing-related keys and service configuration if the Licensing service fails to start.

2. Technical Overview

Remote Desktop Licensing (RD Licensing) manages the issuance of CALs. When a device connects to an RD Session Host, the License Server issues a temporary or permanent CAL. This license is cryptographically bound to the hardware ID of the device.

Microsoft does not document these registry keys in the Windows UI; they are stored in binary format and encrypted. Direct manipulation of these keys is unsupported and can lead to licensing failures.

7. Recommended PowerShell (Safe) Alternative

Instead of direct registry manipulation, use: Document Every Change Save screenshots or

# List installed license packs
Get-WmiObject -Class Win32_TSIssuedLicense -Namespace root\cimv2\terminalservices

Error 1: Access Denied (Even as Admin)


Some RDS registry keys are owned by NT SERVICE\TermService. To edit them, you must:


    

  • Take ownership via Regedit → Permissions → Advanced → Change owner to Administrators.
    • 

  • Grant yourself Full Control.
    • 



Procedure C: Clear Stuck CAL Tokens


If a single user consistently receives a temporary license instead of a permanent CAL:


    

  1. Navigate to: HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\LicensingCore\TemporaryLicenses
    2. 

  2. Look for entries matching the problematic user or device.
    3. 

  3. Delete those specific keys.
    4. 

  4. Restart the RDS service.
    5. 





Background


    

  • Purpose: RDS CALs control and track licensing for Remote Desktop Services (formerly Terminal Services). Windows stores configuration and some status information about RDS licensing in the registry so the RDS Licensing service and client components can locate license servers, apply licensing mode (Per User vs Per Device), and cache client-side license information.
    • 

  • When it matters: Admins interact with RDS licensing registry entries when configuring or troubleshooting RDS deployment, moving license servers, clearing corrupted license caches, or diagnosing CAL issuance problems.
    •