How to Remove RDS Temporary Licenses and Configure Perpetual Licenses in Windows Server

Imagine you've just implemented Remote Desktop Services (RDS) in your company, and your users begin accessing it remotely via RDP clients. The initial connection is straightforward, but behind the scenes, Windows automatically assigns a temporary license to allow access for 90 days. What happens when it's time to go further and establish a license that truly lasts forever? This is where proper RDS license management becomes crucial to prevent service interruptions and ensure stable and legal remote access.

The Origin of the Temporary License and Its Limitation

When an RDP client connects for the first time, it receives a temporary license valid for 90 days. This temporary license is stored on the client computer within the Windows registry, specifically in the path HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing. However, this license is not a permanent solution, as once it expires, the user may encounter unexpected blocks when attempting to connect to the server.

How to Eliminate a Temporary License to Upgrade to a Perpetual License?

Removing a temporary license isn't complicated, but it requires precision. It involves deleting certain keys in the client's registry, specifically within the path mentioned, to remove the stored temporary license. It's crucial to back up the registry before making any changes to avoid impacting system stability.

Steps to remove the temporary license:

• Open the Windows Registry Editor with administrator privileges.
• Navigate to HKEY_LOCAL_MACHINESoftwareMicrosoftMSLicensing.
• Remove the keys and subkeys within this path that store the temporary license.
• Close the editor and restart the RDP client to generate a new connection without a temporary license.

Configuring the Server to Issue Perpetual Licenses

With the temporary license removed from the client, the next step is to properly configure the RDS license server. The server must be ready to issue permanent licenses—either per user or per device—depending on your organization's structure and needs.

Furthermore, it's important to know that Windows Server offers a 120-day grace period after RDS installation during which Client Access Licenses (CALs) are not required. However, once this period has expired, the server will no longer allow connections without valid and correctly configured licenses, which could jeopardize service continuity.

Protect Remote Access with Proper Migration and Validation

When the infrastructure evolves or maintenance is performed on the RDS environment, it may be necessary to migrate licenses to new servers. Following careful steps to migrate and validate these perpetual licenses ensures that remote access remains active and uninterrupted.

The overall process involves deleting the temporary license on the RDP clients, configuring and validating the license server to issue permanent licenses, and verifying that users or devices are properly registered. This approach prevents users from being locked out when their temporary licenses expire and facilitates ongoing license management across the network.

Conclusion

Managing RDS licenses in Windows Server environments may seem like a complex technical task, but understanding the cycle from assigning temporary licenses to implementing perpetual licenses is crucial for maintaining a seamless remote experience. Removing temporary licenses on clients, properly configuring servers for perpetual licenses, and keeping track of the grace period ensures your users never lose access to their remote desktops.

Are you ready to optimize RDS license management in your organization? Start by ensuring you remove temporary licenses and set up valid licenses today to avoid future problems.