Managing CAL Licenses in Windows Server 2022: Complete Administrator’s Guide

Windows Server licensing extends beyond server activation—Client Access Licenses (CALs) form an equally critical component. Administrators often prioritize deployment while treating CAL management as secondary, only discovering compliance gaps during audits or when encountering unexpected connection limits.

This guide addresses CAL licensing for Windows Server 2022, breaking complex processes into practical steps. Coverage spans basic concepts through advanced management techniques for implementing properly licensed environments.

Understanding CAL Licensing in Windows Server 2022

Client Access Licenses enable client connections to Windows Server resources under Microsoft’s licensing model. CALs supplement the server license itself—purchasing Windows Server 2022 only licenses the server software, not client access to it.

Two primary CAL types exist:

User CALs grant specific users access from unlimited devices. Employees connecting from multiple locations or devices throughout workdays need only single User CALs. A sales representative accessing resources from laptop, tablet, and smartphone requires just one license.

Device CALs permit specific devices to access server resources regardless of user count. This proves economical where multiple users share devices—shift workers at common workstations, kiosks, or manufacturing terminals.

Organizations typically choose either User CALs or Device CALs for entire Windows Server environments. Calculate which approach offers better cost-effectiveness based on usage patterns.

Specialized CALs exist for specific services:

• RDS CALs (Remote Desktop Services) enable remote desktop connections beyond two default administrative sessions
• External Connector Licenses serve as CAL alternatives for external users like customers or partners

CALs require no technical installation on client devices. License servers track usage and ensure compliance through various mechanisms. While licensing remains invisible to end users, administrators must ensure proper configuration to prevent connection issues or compliance problems.

Base Windows Server CALs cover only standard Windows services. Services like RDS require additional, service-specific CALs.

Installing the License Server Role in Windows Server 2022

Setting up the license server role precedes CAL activation. This component manages CAL inventory and handles license assignment.

Method 1: Using Server Manager

1. Log into Windows Server 2022 with administrator privileges
2. Open Server Manager (launches automatically or via Start menu)
3. Click “Manage” in upper-right corner, select “Add Roles and Features”
4. Click “Next” until reaching “Server Roles” screen
5. For standard CALs, no specific role is required—servers handle these automatically
6. For RDS CALs, expand “Remote Desktop Services”
7. Check “Remote Desktop Licensing” box, click “Next”
8. Follow wizard with default options until “Confirmation” screen
9. Click “Install” and wait for completion
10. Click “Close” when finished

Method 2: Using PowerShell

Command-line administrators can install faster via PowerShell:

# Open PowerShell as Administrator

# For RDS licensing:

Install-WindowsFeature RDS-Licensing, RDS-Licensing-UI -IncludeManagementTools

 

# Verify installation:

Get-WindowsFeature *RDS*

 

Post-installation configuration:

1. Open “Remote Desktop Licensing Manager” from Start menu or Server Manager Tools
2. Right-click “All Servers,” select “Install License Server”
3. Follow activation wizard with requested server information
4. Choose whether to manage licenses organization-wide or domain-only
5. Complete wizard to register license server

Standard Windows Server CAL tracking requires no additional configuration as these licenses aren’t technically enforced. RDS CALs need proper license server configuration to function.

A single license server can manage licenses for multiple Windows servers, eliminating the need for per-server role installation.

Adding and Activating Standard User CALs

After license server configuration, add User CALs to license inventory.

Preparation:

• Obtain CAL pack information from license retailer or Microsoft Volume Licensing Service Center (VLSC)
• Note License ID and authorization number for activation
• Ensure license server internet connectivity (for online activation)

Adding CALs:

1. Open “Remote Desktop Licensing Manager” from Administrative Tools
2. Connect to license server if not already selected
3. Right-click server name, select “Install Licenses”
4. Choose purchase program (Volume Licensing, Retail, etc.)
5. Select “User CALs” as license type
6. Enter license information including License ID and authorization number
7. Complete wizard to add licenses to inventory

Activation Process:

Activation typically occurs automatically during installation with internet connectivity. Manual activation otherwise:

1. Right-click server in Remote Desktop Licensing Manager
2. Select “Activate Server”
3. Choose activation method (automatic over internet is simplest)
4. Follow prompts to complete activation
5. Verify CALs appear correctly in license inventory

User CAL activation is straightforward as these licenses aren’t tied to specific users within licensing tools. Organizations track User CAL assignments through internal asset management.

Verification:

1. Expand server name in Licensing Manager
2. Click “Windows Server User CALs”
3. Right pane displays installed licenses with quantity and expiration details

While standard Windows Server CALs don’t require technical enforcement configuration, proper documentation protects during audits and aids usage tracking for budgeting and planning.

Installing and Configuring Device CALs

Device CALs require more detailed tracking since they apply to specific devices rather than users.

Adding Device CALs:

1. Open Remote Desktop Licensing Manager
2. Right-click license server, select “Install Licenses”
3. Choose license program type
4. Select “Device CALs” when prompted
5. Enter license information including authorization numbers
6. Complete wizard to add licenses

Configuring Assignment:

Device CALs require allocation method configuration:

1. Right-click server in Licensing Manager, select “Properties”
2. Go to “Device CAL” tab
3. Choose allocation method:
   • First-come, first-served: Assigns CALs to devices by connection order
   • Predetermined by administrator: Manual assignment to specific devices

For manual assignment:

1. Expand server in Licensing Manager
2. Click “Device CALs”
3. Select “Assign CALs to Devices” from Action menu
4. Enter device names or browse network to select them
5. Confirm assignments

Device CALs include mechanisms identifying inactive devices for potential license reclamation:

1. Right-click server in Licensing Manager, select “Properties”
2. Go to “Device CAL” tab
3. Set desired inactive period for license reclamation
4. Click “OK” to save

Windows Server uses different tracking mechanisms for various CAL types. Standard Windows Server CALs aren’t technically enforced, while RDS CALs are strictly enforced and prevent connections when unavailable.

Setting Up RDS CAL Licensing for Remote Desktop Services

Remote Desktop Services requires specialized CALs beyond standard Windows Server CALs.

Prerequisites:

• RD Licensing role installed
• Valid RDS CALs purchased through Microsoft reseller
• Server registered with license clearinghouse

Installation:

1. Open “Remote Desktop Licensing Manager” from Administrative Tools
2. Right-click license server, select “Install Licenses”
3. Choose license program (Volume, Retail, etc.)
4. Select “RDS Per User CAL” or “RDS Per Device CAL” based on purchase
5. Enter license information including License ID and activation codes
6. Follow wizard to complete installation

Configuring RDS Environment:

After installing RDS CALs, configure RDS to use them:

1. Open Server Manager
2. Navigate to Remote Desktop Services > Overview
3. Under “Deployment Tasks,” select “Edit Deployment Properties”
4. Select “RD Licensing” in left pane
5. Click “Add” to specify license server
6. Enter server FQDN or browse network
7. Choose appropriate license type (Per User or Per Device)
8. Click “OK” to save

Verification:

1. In Server Manager, go to Remote Desktop Services > Overview
2. Check RD Licensing Diagram shows green check mark
3. Connect test client to verify successful connections

Grace Period: Windows Server 2022 provides 120-day grace period for RDS connections after initial configuration. Clients can connect without valid RDS CALs during this time. Complete licensing deployment before grace period expiration to prevent service interruptions.

For deployments with multiple RD Session Host servers, configure all hosts to use the same license server for centralized management. This simplifies administration and ensures consistent license tracking across RDS farms.

RDS CALs are typically version-specific. Windows Server 2022 RDS deployments generally require 2022 RDS CALs, though Microsoft sometimes offers limited backward compatibility.

Managing CAL Licenses Through PowerShell

Larger environments benefit from PowerShell’s automation capabilities for CAL license management.

Installing License Server Role:

# Install RD Licensing role

Install-WindowsFeature RDS-Licensing -IncludeManagementTools

 

# Install management UI

Install-WindowsFeature RDS-Licensing-UI

 

Configuring License Server:

# Import RemoteDesktop module

Import-Module RemoteDesktop

 

# Set RD License server

Set-RDLicenseConfiguration -LicenseServer “LicenseServer.domain.com” -Mode PerUser -ConnectionBroker “RDBroker.domain.com”

 

Checking License Status:

# Check RDS license configuration

Get-RDLicenseConfiguration -ConnectionBroker “RDBroker.domain.com”

 

# Get detailed license information

Get-WmiObject -Namespace “Root/CIMV2/TerminalServices” -Class “Win32_TSLicenseKeyPack” -ComputerName “LicenseServer.domain.com”

 

Managing Reports:

# Generate license usage report (CSV export)

Get-WmiObject -Namespace “Root/CIMV2/TerminalServices” -Class “Win32_TSIssuedLicense” -ComputerName “LicenseServer.domain.com” | 

Export-Csv -Path “C:\LicenseReport.csv” -NoTypeInformation

 

Automating Monitoring:

Schedule this script to check for low license availability:

$LicServer = “LicenseServer.domain.com”

$LicenseInfo = Get-WmiObject -Namespace “Root/CIMV2/TerminalServices” -Class “Win32_TSLicenseKeyPack” -ComputerName $LicServer

$AvailableLicenses = ($LicenseInfo | Measure-Object -Property AvailableLicenses -Sum).Sum

$TotalLicenses = ($LicenseInfo | Measure-Object -Property TotalLicenses -Sum).Sum

 

if ($AvailableLicenses -lt ($TotalLicenses * 0.1)) {

    Send-MailMessage -To “admin@company.com” -From “alerts@company.com” -Subject “Low RDS CAL Warning” -Body “Only $AvailableLicenses licenses remaining out of $TotalLicenses total.”

}

 

Bulk Management:

Handle multiple license servers efficiently:

$LicenseServers = “LicServer1”, “LicServer2”, “LicServer3”

foreach ($Server in $LicenseServers) {

    Write-Host “License information for $Server” -ForegroundColor Green

    Get-WmiObject -Namespace “Root/CIMV2/TerminalServices” -Class “Win32_TSLicenseKeyPack” -ComputerName $Server | 

    Format-Table KeyPackType, TotalLicenses, AvailableLicenses -AutoSize

}

 

PowerShell commands work well for RDS CAL management. Standard Windows Server CALs lack the same technical enforcement or PowerShell management capabilities since Windows Server doesn’t track them directly.

For environments with System Center Configuration Manager or other management tools, integrate PowerShell scripts with these platforms for comprehensive license management.

Troubleshooting Common CAL Licensing Issues

CAL licensing problems occur despite careful setup. Here are solutions for common issues:

Issue: “No Remote Desktop License Servers Available”

This appears when RDS can’t locate your license server.

Solutions:

• Verify license server runs and is network-accessible
• Check proper license server registration in Active Directory

Manually specify license server in RDS configuration:
Set-RDLicenseConfiguration -LicenseServer “LicenseServer.domain.com” -Mode PerUser -ConnectionBroker “RDBroker.domain.com”

• Ensure firewall allows traffic on licensing service ports (TCP 135 and dynamic RPC ports)

Issue: Licenses Not Showing After Installation

Licenses appear to install but don’t show in inventory.

Solutions:

Restart Remote Desktop Licensing service:
Restart-Service TermServLicensing

• Verify proper license server activation before installing licenses
• Re-run license installation, checking for error messages
• Contact Microsoft Support with authorization IDs if problems persist

Issue: “The Remote Computer Disconnected the Session”

Commonly indicates RDS CAL issues after grace period expiration.

Solutions:

• Verify available RDS CALs installed of correct type (User or Device)
• Check if clients receive licenses by examining event logs on client computers

Temporarily extend grace period while troubleshooting (not for long-term use):
reg add “HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod” /v “Max” /t REG_DWORD /d 0xffffffff /f

• Reset RDS licensing database if corrupted

Issue: Unexpected CAL Consumption

CALs consumed faster than expected.

Solutions:

• For Device CALs, check reclamation policy ensures inactive device licenses return to pool
• Review license reports for unusual patterns or potential overuse
• Verify chosen CAL model (User vs Device) still aligns with usage patterns
• Check for unauthorized access or unexpected client connections

Issue: License Server Discovery Problems

When automatic license server discovery fails.

Solutions:

Ensure license server registered in Active Directory:
gpupdate /force

• Check DNS configuration for proper license server resolution
• Verify license server in same domain as RD Session Host or has appropriate trust relationships
• As last resort, manually specify license server on each RD Session Host

Issue: “Terminal Server has Exceeded Maximum Connections”

Indicates CAL limit reached.

Solutions:

• Install additional CALs
• Review current usage for unnecessary connections

For temporary relief, disconnect idle sessions:
Get-RDUserSession | Where-Object {$_.SessionState -eq “STATE_DISCONNECTED”} | Remove-RDUserSession

Check Windows Event Logs for specific licensing error messages. The “Terminal Services-Licensing” log contains valuable diagnostic information pinpointing exact licensing problems.

Best Practices for CAL License Management

Effective CAL management extends beyond initial setup. These practices maintain compliance while optimizing licensing investment:

License Inventory Management

Create comprehensive license inventory documenting:

• License quantities and types
• Purchase dates and renewal information
• Assignment details for tracking
• License keys and authorization numbers
• Regular reconciliation of deployed licenses against purchased inventory
• Secure but accessible license documentation storage for audits
• Dedicated license management software for larger deployments

Planning and Optimization

• Regularly evaluate whether User CALs or Device CALs better suit current usage
• Implement forecasting systems anticipating license needs before urgency
• Consider financial and practical implications of different models:
  • Subscription vs. perpetual licenses
  • Software Assurance benefits
  • Volume licensing advantages
• Consolidate license purchases for maximum volume discounts

Deployment Best Practices

• Use multiple license servers in large organizations for redundancy
• Configure automatic replication between license servers when possible
• Implement monitoring alerting when availability drops below defined thresholds
• Document license server configurations thoroughly for disaster recovery

Compliance and Auditing

• Schedule regular internal license audits before Microsoft audits
• Establish clear license assignment and reclamation procedures
• Train IT staff on licensing requirements and compliance importance
• Maintain records of decommissioned servers and reassigned licenses
• Engage licensing specialists during major infrastructure changes

Security Considerations

• Restrict license server administration to authorized personnel
• Implement change management procedures for licensing modifications
• Regularly review license usage for unexpected patterns indicating security issues
• Secure license documentation as sensitive business information

License Reassignment Policies

Develop clear guidelines for license reassignment:

• For standard Windows Server CALs, document internal reassignment processes
• For RDS CALs, configure appropriate reclamation policies
• Ensure compliance with Microsoft’s reassignment restrictions (typically 90 days between reassignments)
• Maintain detailed reassignment records

Optimizing License Costs

• Regularly review connected devices for license reclamation candidates
• Consider consolidating RDS servers to maximize license utilization
• Evaluate whether certain user groups could share device-based licenses
• Right-size license purchases by analyzing actual usage patterns

While technical enforcement varies between CAL types, legal compliance requirements apply equally to all Microsoft licenses. Even licenses without technical enforcement still require proper licensing for compliance.

Conclusion

Managing CAL licenses in Windows Server 2022 requires understanding both technical implementation and licensing requirements. This guide covers activation procedures, different license types, and common issue troubleshooting.

CAL licensing may seem complex initially, but with proper planning and management, it becomes straightforward Windows Server administration. Properly configured licensing infrastructure reduces compliance risks, prevents connection issues, and optimizes licensing costs.

Licensing requirements evolve over time. Stay informed about Microsoft’s latest licensing terms and maintain regular communication with Microsoft licensing representatives or resellers. Their guidance ensures organizational compliance while maximizing licensing investment value.

Whether managing small business servers or enterprise deployments with thousands of CALs, the principles remain consistent: understand needs, implement proper tracking, maintain adequate documentation, and regularly review licensing position. These practices prevent common CAL management pitfalls while ensuring properly licensed, fully functional Windows Server environments.