Windows Server 2022 — Remote Desktop Licensing service not issuing CALs — Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution — Primary Fix
7. Solution — Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

RDS users are denied sessions or receive grace-period warnings because RD Licensing server does not issue valid CALs. Multi-user app access is interrupted.

Environment & Reproduction

Usually triggered by licensing role corruption, misconfigured licensing mode, or policy mismatch after role changes.

Get-WindowsFeature RDS-Licensing,RDS-RD-Server
Get-Service TermServLicensing
Get-WinEvent -LogName Application -MaxEvents 50 | Where-Object {$_.Message -match 'Remote Desktop Licensing|CAL'}

Root Cause Analysis

Licensing database inconsistency, wrong per-user/per-device mode, and unreachable license server settings in GPO are the top causes.

Quick Triage

Validate licensing mode and configured license servers from both host and policy view.

Get-ItemProperty 'HKLM:/SOFTWARE/Policies/Microsoft/Windows NT/Terminal Services'
qwinsta
Get-RDLicenseConfiguration -ConnectionBroker  -ErrorAction SilentlyContinue

Step-by-Step Diagnosis

Audit role health, event channels, and policy enforcement precedence.

gpresult /h C:/Temp/gp-rds.html
Get-WinEvent -LogName 'Microsoft-Windows-TerminalServices-Licensing/Admin' -MaxEvents 60
Get-Service | Where-Object {$_.Name -match 'TermService|TermServLicensing'}

Solution — Primary Fix

Restart licensing services, reconfigure correct licensing mode/server, and reactivate license server if required.

Restart-Service TermServLicensing -Force
Set-ItemProperty 'HKLM:/SOFTWARE/Policies/Microsoft/Windows NT/Terminal Services' -Name LicensingMode -Type DWord -Value 4
Set-ItemProperty 'HKLM:/SOFTWARE/Policies/Microsoft/Windows NT/Terminal Services' -Name LicenseServers -Value ''
gpupdate /force

Solution — Alternative Approaches

Rebuild RD Licensing role service if database corruption persists and restore license packs through Microsoft clearinghouse process.

Uninstall-WindowsFeature RDS-Licensing
Install-WindowsFeature RDS-Licensing -IncludeManagementTools
Restart-Computer -Force

Verification & Acceptance Criteria

New RDS sessions succeed without grace-period warnings and licensing events indicate successful CAL issuance.

Get-WinEvent -LogName 'Microsoft-Windows-TerminalServices-Licensing/Admin' -MaxEvents 30
quser
Get-Service TermServLicensing

Rollback Plan

If new licensing configuration fails, restore previous policy and service state while maintaining temporary access controls.

reg import C:/Temp/rds-licensing-backup.reg
gpupdate /force
Restart-Service TermServLicensing

Prevention & Hardening

Document licensing mode per collection, monitor grace-period counters, and test policy changes in staging brokers first.

Get-ScheduledTask | Where-Object {$_.TaskName -match 'RDS|Licens'}
Get-WinEvent -LogName 'Microsoft-Windows-TerminalServices-Licensing/Admin' -MaxEvents 100

Related Errors & Cross-Refs

Related to RDS grace period expiry, license mode mismatch, and broker-policy conflicts in multi-host farms.

View all Windows Server 2022 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Microsoft RDS licensing deployment and troubleshooting documentation for Windows Server 2022 and enterprise CAL lifecycle management.