Rds Cal License Registry Key

On the Remote Desktop License Server, the registry stores the scope of issuance (permanent vs. temporary).

| Aspect | Rating | Notes | |--------|--------|-------| | Usefulness for admins | ⭐⭐⭐⭐☆ | Critical for troubleshooting & recovery | | Safety for manual editing | ⭐☆☆☆☆ | Dangerous except for LicensingMode / LicenseServers | | Documentation clarity | ⭐⭐☆☆☆ | Microsoft docs are sparse on per-user CAL registry details | | Recommended approach | Avoid direct edits | Use Server Manager or Group Policy |

Final recommendation: The RDS CAL registry key is a powerful but risky diagnostic tool. Only modify LicensingMode and LicenseServers when group policy cannot be applied. Never touch the IssuedLicenses subtree without Microsoft Support involvement.

Managing RDS CALs via the Windows Registry is typically done to define licensing servers, set licensing modes, or reset the 120-day grace period. While Group Policy is the preferred management tool, these registry keys provide direct control over how a Session Host interacts with the License Server.  Core RDS Licensing Registry Keys 

The primary configuration keys are located under the Terminal Server services branch:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM  Configuration Task  Registry Path & Value Name Value Data Licensing Mode ...\RCM\Licensing Core\LicensingMode 2 = Per Device; 4 = Per User License Server List ...\RCM\LicenseServers\SpecifiedLicenseServers (REG_MULTI_SZ) FQDN or IP of servers Grace Period Reset ...\RCM\GracePeriod Delete the TimeBomb binary value*

*Note: Deleting the TimeBomb value requires taking ownership of the GracePeriod key first, as it is protected by SYSTEM permissions.  Specific Troubleshooting Keys 

For workgroup environments or complex licensing deployments, the following keys are used: 

Disable Workgroup Enforcement: Prevents licensing errors when the RD Licensing server is in a workgroup and not a domain.

Path: HKLM\SYSTEM\CurrentControlSet\Services\TermServLicensing\Parameters

Value: DisableWorkgroupAuthEnforcement (REG_DWORD) set to 1.

Prevent License Upgrades: Useful in environments where you want to prevent a client from automatically upgrading to a higher version CAL.

Path: HKLM\Software\Policies\Microsoft\Windows NT\Terminal Services Value: PreventLicenseUpgrade (REG_DWORD) set to 1.  Verification Steps  To ensure your registry changes have taken effect: 

Restart the Service: Restart the Remote Desktop Services service or the entire server for the new registry values to be read.

RD Licensing Diagnoser: Open the RD Licensing Diagnoser tool on the Session Host to verify that the licensing mode and server list match your registry entries.

Client-Side Check: On a client machine, you can check HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing to see cached license information issued by the server.  License Remote Desktop session hosts | Microsoft Learn

If your server improperly entered “grace period expired” status even after adding valid CALs, some administrators attempt to delete the GracePeriod key. However, doing this without stopping the TermServLicensing service can lead to system instability.

There are legitimate scenarios where an administrator needs to interact with the RDS CAL registry key. The most common is changing the licensing mode after initial deployment. For example, if a company switches from thin clients (Per Device) to roaming employees (Per User), an administrator can change the LicenseMode value from 2 (Per Device) to 4 (Per User). Another scenario is disaster recovery: after restoring a license server from backup, registry corruption may require manual cleanup of orphaned license entries. Third-party tools or scripts sometimes rely on reading these registry keys for inventory and monitoring.

However, the single most frequent – and dangerous – reason administrators touch this key is to circumvent licensing errors during the 120-day grace period. When an RDS server cannot reach a license server, it eventually stops accepting new connections. Unscrupulous or desperate guides online may suggest deleting or modifying registry keys to reset the grace period. This is a risky and often temporary hack.

This document explains the purpose, location, structure, and implications of the Remote Desktop Services (RDS) Client Access License (CAL) registry key(s) on Windows servers. It covers when registry changes are relevant, how the keys are used by RDS licensing components, risks of manual edits, troubleshooting pointers, and best-practice recommendations.

If you need the Windows Registry location used by Remote Desktop Services Client Access Licenses (RDS CALs), the relevant key for the Remote Desktop Licensing Grace Period and licensing configuration is:

Common subkeys/values under RCM:

Additional related key for licensing service settings:

Notes and cautions:

In Windows Remote Desktop Services (RDS), license configuration and grace period data are managed through specific registry keys. These keys allow administrators to define licensing modes, specify license servers, and troubleshoot activation issues. 1. Primary RDS Licensing Registry Locations

Most RDS licensing configurations are stored in the following high-level registry paths: Deployment Configuration (GPO/Policies):

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services This subkey stores settings pushed via Group Policy. System Runtime Configuration:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM

This path contains the active licensing state, including grace periods and certificate data. Licensing Service Parameters:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermServLicensing\Parameters

Used for server-level overrides, such as disabling workgroup authentication enforcement. Microsoft Learn 2. Key Registry Values and Their Meanings

Within these paths, specific values determine how the RDS environment operates: Registry Value Description LicensingMode ...\RCM\Licensing Core : Per Device mode. : Per User mode. : No mode set/Grace period. LicenseServers ...\Terminal Services

A list of fully qualified domain names (FQDNs) for the license servers. L$RTMTIMEBOMB ...\RCM\GracePeriod

A binary entry that tracks the remaining time in the 120-day licensing grace period. 3. Common Administrative Actions via Registry

Administrators often interact with these keys to resolve licensing errors or reset environments: Resetting the Licensing Grace Period:

If the 120-day grace period expires before CALs are installed, deleting the L$RTMTIMEBOMB entry under the GracePeriod

key can reset the timer. This requires taking ownership of the key and granting "Full Control" permissions to the Administrators group. Resolving Certificate Errors:

Corrupted X509 certificates can prevent licensing. Deleting the Certificate X509 Certificate X509 Certificate ID X509 Certificate2 values under

and restarting the Remote Desktop Licensing service forces the system to regenerate them. Forcing Licensing Mode:

If Group Policy is not applying correctly, manually changing the LicensingMode

value in the registry can sometimes resolve conflicts where the server continues to report a "5" (unconfigured) status. Microsoft Community Hub 4. Backup and Safety

Before modifying any licensing keys, it is standard practice to export the registry subkey rds cal license registry key

for recovery purposes. Modification of these keys should always be followed by a restart of the Remote Desktop Licensing service via services.msc to apply changes. Microsoft Community Hub taking ownership of a registry key to perform these resets?

If you've spent any time managing Windows Servers, you know the Remote Desktop Services (RDS) licensing process can be a headache. The RDS CAL License registry keys are the "hidden gears" that keep remote connections running—or bring them to a grinding halt. 🛠️ The "Big Three" Registry Keys

While most admins use Group Policy, the registry is where the real configuration lives. The Mode Selector (LicensingMode):

Path: HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\Licensing Core

The Secret Code: Setting this to 2 tells the server to look for Per Device CALs; setting it to 4 switches it to Per User. The Address Book (SpecifiedLicenseServers):

Path: HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\LicenseServers

Purpose: This tells your Session Host exactly which server is holding the "tickets" (licenses). Without this, your server is essentially shouting into a void. The Infamous "Time Bomb" (L$RTMTIMEBOMB):

Path: HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod

The Catch: This key tracks the 120-day grace period. If it expires, users get kicked out. Many admins in lab environments delete this key to "reset" the clock, though Microsoft warns this isn't for production use. 🚦 Pro-Tip: When to Use Them

Registry edits are usually a "last resort" for troubleshooting RDS licensing. Use them if:

Group Policy isn't applying correctly (check with gpresult /H).

You're working on a Workgroup server where Group Policy isn't available.

The RD Licensing Diagnoser shows a "No license server available" error despite correct settings.

⚠️ Warning: Always back up your registry before diving in. Deleting the wrong subkey in Terminal Server can lead to a full OS reinstallation.

Remote Desktop Services (RDS) Client Access License (CAL) system does not use a single "registry key" as a serial number. Instead, the registry is primarily used to manage the licensing mode , identify license servers , or reset the grace period 1. The "Grace Period" Registry Key

The most commonly referenced registry key regarding RDS licensing is the one that tracks the 120-day grace period. Once this period ends, users can no longer connect without a valid CAL.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod The "Timebomb"

: Inside this key, there is typically a binary entry starting with L$RTMTIMEBOMB

. Deleting this entry resets the 120-day timer, though this requires taking ownership of the registry folder first.

: This is usually a temporary fix for administrators to restore connectivity while they troubleshoot or wait for license procurement. 2. Configuring the Licensing Mode

If your server is failing to recognize installed licenses, it may be because the Licensing Mode

(Per User vs. Per Device) is not correctly set in the registry. Microsoft Learn

Configuring Remote Desktop Services (RDS) through the Windows Registry is a common task for system administrators troubleshooting licensing issues or setting up session hosts without using Group Policy Objects (GPO). Primary Registry Key Locations

There are several critical registry keys used to manage RDS Client Access Licenses (CALs), depending on whether you are defining the licensing mode, specifying a license server, or managing the grace period. Registry Path Value Name Licensing Mode

HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\Licensing Core LicensingMode Specified Server

HKLM\SYSTEM\CurrentControlSet\Services\TermService\Parameters\LicenseServers SpecifiedLicenseServers Policy-based

HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services LicensingMode & LicenseServers Grace Period

HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod

The primary registry keys for managing Remote Desktop Services (RDS) Client Access Licenses (CALs) are used to configure the licensing mode, specify license servers, or troubleshoot the 120-day grace period. 1. Core Licensing Configuration

Located at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\Licensing Core, the LicensingMode DWORD sets the mode (2 for Device, 4 for User). License servers are specified under HKLM\SYSTEM\CurrentControlSet\Services\TermService\Parameters\LicenseServers. 2. Group Policy and Troubleshooting License Remote Desktop session hosts | Microsoft Learn

Remote Desktop Services (RDS) Client Access Licenses (CALs) are essential for managing user and device connections to your terminal servers. Understanding the RDS CAL license registry key is critical for administrators needing to troubleshoot licensing issues, clear stuck grace periods, or back up configurations.

This guide covers the exact registry locations for RDS CALs, how to manage them, and best practices for system administrators. 🛑 Critical Warning Before You Begin

Modifying the Windows Registry can cause irreversible system damage if done incorrectly. Always back up the registry key before making changes. Document any values you modify or delete.

Perform registry edits during maintenance windows to avoid user disconnection. 📍 Where is the RDS CAL License Registry Key?

Windows stores RDS licensing data in different registry paths depending on whether you are looking at the RD Licensing Server or the RD Session Host (Client). 1. The RD Licensing Server Database Path

If you need to find where the actual licensing server stores its database configuration and activated license packs, navigate to:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermServLicensing\Parameters

What it does: This key points to the location of the Jet database (lServer.mdb) that tracks all issued CALs.

Common use case: Moving the license database to a new drive. 2. The RD Session Host Grace Period Key

When you build a new RD Session Host, Microsoft grants a 120-day grace period. Once this expires, clients cannot connect without a valid license server. To reset or check this grace period, navigate to: On the Remote Desktop License Server, the registry

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod

What it contains: A binary value that counts down the 120-day grace period.

Special permissions: To delete or modify this key, you must right-click the GracePeriod folder, go to Permissions, and take ownership from SYSTEM to grant your admin account full control. 3. The Client-Side Cached License Key

When a device connects to an RDS host, the host issues a digital token (CAL) to the client machine. This is stored locally on the user's computer at: HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing

What it contains: Subkeys like HardwareID and Store containing the actual certificates.

Common use case: Deleting the MSLicensing folder on a client machine is the standard fix for the error: "The remote session was disconnected because the local computer client access license could not be upgraded or renewed." 🛠️ How to Reset the RDS Grace Period via Registry

If your production licenses are still processing but your 120-day grace period has expired, you can temporarily reset it by removing the registry marker. Step-by-Step Reset: Open the Registry Editor (regedit.exe) as an Administrator.

Navigate to: HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod. Right-click the GracePeriod key and select Permissions.

Click Advanced, change the Owner to Administrators, and click OK.

Check the box to "Replace owner on subcontainers and objects". Give the Administrators group Full Control.

Right-click the specific binary value inside the folder (usually starts with L$FQDN) and click Delete.

Reboot the RD Session Host server for the reset to take effect.

🔍 How to Find Your Active RDS License Server via Registry

Sometimes group policies fail, and you need to force an RD Session Host to look at a specific licensing server. You can verify or set this manually in the registry.

Navigate to:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\LicenseServers

To add a server: Create a new Key under LicenseServers named exactly after the NetBIOS or FQDN of your license server.

Alternatively, modern versions of Windows Server prefer specifying this through the following path if set via policy:HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services Look for the string value: LicenseServers 💡 Best Practices for RDS License Registry Management

Use GPO over Registry: Whenever possible, use Group Policy Objects (GPOs) to assign license servers and licensing modes (Per User or Per Device) rather than hacking the registry manually. GPOs are easier to audit and replicate.

Backup MSLicensing: Before deleting the MSLicensing key on client machines to fix connection errors, right-click it and select Export.

Run as Admin: Remember that clearing the client-side MSLicensing key requires running the Remote Desktop Client (mstsc.exe) as an Administrator the first time you reconnect, so it has permission to recreate the registry keys.

Managing Remote Desktop Services (RDS) Client Access Licenses (CALs) through the Windows Registry is often necessary for troubleshooting licensing errors or configuring servers in environments where Group Policy is not applied. Key RDS Licensing Registry Keys

RDS configuration is primarily handled within HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\.

Mode (Licensing Core): Set LicensingMode (DWORD) to 2 (Per Device) or 4 (Per User).

Server Name (LicenseServers): Defines the license server IP/FQDN.

Grace Period: Located in the GracePeriod key, you may need to delete the L$RTMTIMEBOMB value (after taking ownership) to reset the 120-day evaluation. Essential Considerations

Domain vs. Workgroup: Workgroup servers only support Per Device (Mode 2).

Policy Overrides: Settings in SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services take precedence.

Workgroup Setup: For workgroups, you may need to set DisableWorkgroupAuthEnforcement to 1 in ...\Services\TermServLicensing\Parameters.

Note: Always restart the server after making registry changes to apply new licensing configurations. Guidance for troubleshooting RDS Licensing - Windows Server

The registry keys for Remote Desktop Services (RDS) Client Access Licenses (CALs) differ depending on whether you are configuring the session host, managing the licensing server, or troubleshooting a client device. 1. Configure Licensing Mode and Server

These keys are used on the RD Session Host to specify how it finds and communicates with the license server. Group Policy-Defined Settings:

Registry Path: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services Value: LicensingMode (DWORD) 2 = Per Device 4 = Per User

Value: LicenseServers (String) — The FQDN of your license server. Local/Manual Configuration:

Registry Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\Licensing Core Value: LicensingMode (DWORD) — Same values as above.

License Server Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters\LicenseServers

Value: SpecifiedLicenseServers (Multi-String) — Contains the list of license servers. 2. Reset RDS Grace Period

If your 120-day evaluation period has expired and you need to reset it for testing, you must delete the "Timebomb" key.

Registry Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod

Action: Delete the L$RTMTIMEBOMB... binary value. Note that you must take ownership of the GracePeriod folder to delete this entry. 3. Clear Client-Side Licensing Errors

If a client PC receives a "licensing protocol" error, deleting the local license cache often forces a fresh request. Guidance for troubleshooting RDS Licensing - Windows Server | Aspect | Rating | Notes | |--------|--------|-------|

The primary registry keys associated with RDS CAL (Client Access License)

management handle three main functions: defining the licensing mode, identifying the license server, and managing the 120-day grace period. 1. Licensing Mode and Server Configuration

These keys define how the Remote Desktop Session Host (RDSH) requests licenses and where it looks for them. Licensing Mode

: Determines if the server is in "Per User" or "Per Device" mode.

HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\Licensing Core LicensingMode (Per Device) or (Per User). Specified License Servers : Lists the addresses of the servers that issue the CALs.

HKLM\SYSTEM\CurrentControlSet\Services\TermService\Parameters\LicenseServers SpecifiedLicenseServers Group Policy Overrides

: When set via GPO, the configuration is stored in a different location that takes precedence over the standard RCM keys.

HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services LicenseServers LicensingMode Microsoft Learn 2. The RDS Grace Period (The "Timebomb")

Windows Server provides a 120-day grace period before it strictly requires CALs. This state is tracked by a specific binary registry entry often called the "timebomb".

HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod The Binary Entry : Look for a entry beginning with L$RTMTIMEBOMB Deep Feature - Resetting the Period

By default, even Administrators cannot delete this key due to restricted permissions.

To reset the grace period (often done in lab/test environments), you must Take Ownership GracePeriod folder, grant the Administrators group Full Control , delete the L$RTMTIMEBOMB entry, and reboot. 3. Client-Side License Storage

When a client (computer) is issued a "Per Device" CAL, a token is stored locally on that client's registry so it can present it during future connections. Microsoft Learn HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing Troubleshooting

: If a client cannot connect due to a "corrupt license" error, administrators often delete this MSLicensing

key on the client machine (with elevated privileges) to force a fresh license request upon the next login. Microsoft Learn 4. License Server Certificate Reset Remote Desktop License Issue - Microsoft Q&A

Managing RDS Client Access Licenses (CALs) via the registry is often necessary when Group Policy or the Server Manager GUI fails to apply settings correctly. You can configure the licensing mode and the license server address directly through the Registry Editor. 1. Configure the RDS Licensing Mode

This registry key tells the RD Session Host whether to look for Per User or Per Device CALs.

Registry Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\Licensing Core

Action: Locate or create a DWORD (32-bit) value named LicensingMode. Values: 2 — Per Device mode. 4 — Per User mode. 2. Specify the RD License Server

If your Session Host cannot find the license server, you can manually point to it using the registry.

Registry Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters\LicenseServers

Action: Create a new Key (folder) under LicenseServers named with the FQDN or IP Address of your license server.

Note: You can also use the Microsoft Learn guide to verify if the server is properly configured via PowerShell as an alternative to registry edits. 3. Clear Cached Grace Period (Troubleshooting)

If you are seeing "The Remote Desktop trial period has expired" even after installing licenses, you may need to delete the cached grace period key to force a refresh.

Registry Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod

Action: You must first take ownership and grant yourself "Full Control" permissions for this key. Once done, delete the L$RTMTIMEB... binary value inside.

Reboot: A restart is required for this change to take effect and for the server to reach out to the specified license server. 4. Verify Activation

After making registry changes, use the RD Licensing Manager tool to confirm the server status.

Open Server Manager > Tools > Remote Desktop Services > Remote Desktop Licensing Manager.

The server should show a green checkmark if it is activated and communicating correctly. License Remote Desktop session hosts | Microsoft Learn

In the fluorescent-lit hum of the Server Room, a junior admin named Leo stared at a flickering monitor. It was 4:45 PM on a Friday. He was trying to get a new Remote Desktop Session (RDS) host online, but every user who tried to log in was met with a cold, digital wall: “The remote session was disconnected because there are no Remote Desktop License Servers available.”

Leo had installed the licenses. He had activated the server. Yet, the server was acting like it had amnesia.

"It’s the registry," whispered Sarah, the senior lead, appearing like a ghost behind him. "The server is looking for a map it can't find."

She leaned over and opened regedit. They dove into the belly of the machine, navigating the hive:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\Licensing Core

"Look here," she pointed to the LicensingMode key. "It’s set to 5. That’s the ghost code. It doesn't know if it wants Per User or Per Device."

With a few keystrokes, they flipped the value to 4 (Per User). But the beast still wouldn't budge. Sarah knew they had to clear the "Grace Period" debris—the digital cobwebs left behind from when the server was free and young.

They navigated to:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod "The gatekeeper key," Leo muttered.

Windows didn't want them there. It protected that key with ironclad permissions. Sarah right-clicked, seized Ownership from the SYSTEM, and granted herself full control. With a final, decisive click, she deleted the binary blob sitting inside. "Now," Sarah said, "give it a heartbeat."

Leo restarted the services. The progress bar crawled. He held his breath and tried a test login. Instead of an error, the desktop bloomed into view—icons, taskbars, and all. The registry key had been turned, the lock had clicked, and the users were finally home.

Here is text related to "RDS CAL license registry key," broken down by context. This includes technical locations, troubleshooting advice, and important warnings.