Methods for Resetting Windows Server's 120-Day Remote Desktop Services Grace Period

Overview

Remote Desktop Protocol (RDP) provides a framework for managing remote desktop connections in Windows Server environments. As part of this system, Microsoft allows a grace period of 120 days for organizations to deploy the necessary Client Access Licenses (CALs).

This period gives administrators time to set up their RDP infrastructure without immediately purchasing licenses, which can be beneficial for testing or development purposes. However, if the grace period expires without applying the necessary CALs, users may find themselves locked out from accessing Remote Desktop Session Hosts, causing disruptions in productivity.

Fortunately, administrators can reset this 120-day grace period using the Windows Registry. This process involves a series of steps that require careful execution, as the Windows Registry is a critical operating system component. By following these steps, you can regain access to your RDP without immediately needing to install licenses. In this guide, we’ll walk you through the detailed steps to reset the grace period, enabling you to maintain your remote desktop services smoothly.

Pioneers in Cloud Consulting & Migration Services

Reduced infrastructural costs
Accelerated application deployment

Get Started

Steps to Reset the 120-Day RDP Grace Period

Step 1: Open the Run Dialog

The Run dialog box can be opened by pressing Windows Key + R.

Step 2: Access the Registry Editor

To launch the Windows Registry Editor, type regedit into the Run box and click OK.

step2

Step 3: Open the Registry Editor and navigate to the following path:

Navigate to the following path in the Registry Editor:

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

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

step3

Step 4: Modify Permissions on the GracePeriod Key

To access Permissions, right-click on the GracePeriod key and choose it.

By default, this key has no permissions set, even for administrators. You will need to take ownership in the next step.

step4

Step 5: Take Ownership of the GracePeriod Key

In the Permissions dialog, click Advanced.

step5

In the text field labeled Owner, click Modify.

step5b

Choose the local administrator’s group or the relevant user/group that should manage the key.

Check the options to Replace owner on subcontainers and objects and Replace all child object permissions.

step5c

step5d

Step 6: Grant Full Control to Administrators

After changing ownership, adjust the permissions by granting the Administrators group full control over the GracePeriod key. Select Full Control in the permissions dialog.

step6

Step 7: Delete the TimeBomb Value or the Entire GracePeriod Key

With the correct permissions set, right-click on the TimeBomb value under the GracePeriod key and select Delete. Alternatively, you can remove the entire GracePeriod key from the Registry.

step7

Step 8: Confirm Deletion

Confirm that you want to delete the registry entry.

step8

Step 9: Restart the Server

Restart your server. After rebooting, the full 120-day grace period for your RDP server will be reset, allowing continued use in your lab environment.

step9

Step 10: Adjust Group Policy Settings

Type gpedit.msc in the Run dialogue box once more after restarting.

step10

Go to Administrative Templates > Windows Components > Remote Desktop Services > Connections to open the Remote Desktop Session Host.

Enable Limit number of connections and set it to 999999.

step11

Conclusion

Resetting the 120-day RDP grace period on a Windows Server is a simple process involving changes to the Windows Registry and group policy settings. Following the steps outlined above, you can maintain access to your Remote Desktop Session Hosts without the immediate requirement for client access licenses.

Drop a query if you have any questions regarding RDP and we will get back to you quickly.

Making IT Networks Enterprise-ready – Cloud Management Services

Accelerated cloud migration
End-to-end view of the cloud environment

Get Started

About CloudThat

CloudThat is a leading provider of Cloud Training and Consulting services with a global presence in India, the USA, Asia, Europe, and Africa. Specializing in AWS, Microsoft Azure, GCP, VMware, Databricks, and more, the company serves mid-market and enterprise clients, offering comprehensive expertise in Cloud Migration, Data Platforms, DevOps, IoT, AI/ML, and more.

CloudThat is the first Indian Company to win the prestigious Microsoft Partner 2024 Award and is recognized as a top-tier partner with AWS and Microsoft, including the prestigious ‘Think Big’ partner award from AWS and the Microsoft Superstars FY 2023 award in Asia & India. Having trained 650k+ professionals in 500+ cloud certifications and completed 300+ consulting projects globally, CloudThat is an official AWS Advanced Consulting Partner, Microsoft Gold Partner, AWS Training Partner, AWS Migration Partner, AWS Data and Analytics Partner, AWS DevOps Competency Partner, AWS GenAI Competency Partner, Amazon QuickSight Service Delivery Partner, Amazon EKS Service Delivery Partner, AWS Microsoft Workload Partners, Amazon EC2 Service Delivery Partner, Amazon ECS Service Delivery Partner, AWS Glue Service Delivery Partner, Amazon Redshift Service Delivery Partner, AWS Control Tower Service Delivery Partner, AWS WAF Service Delivery Partner and many more.

To get started, go through our Consultancy page and Managed Services Package, CloudThat’s offerings.

FAQs

1. What occurs when the 120-day grace period ends?

ANS: – When the grace period expires, users will be locked out and unable to connect to the Remote Desktop Session Hosts until valid CALs are installed.

2. Is it safe to modify the Windows Registry?

ANS: – While altering the Windows Registry can solve specific issues, proceeding carefully is crucial, as incorrect changes can impact system functionality. Make a backup every time you alter the registry.

3. Can I reset the grace period multiple times?

ANS: – Yes, the grace period can be reset as needed. However, frequent resets may indicate that you must license your environment properly.

WRITTEN BY Noopur Shrivastava

Noopur Shrivastava works as a Research Associate at CloudThat. She is focused on gaining knowledge of the Cloud environment. Noopur loves learning about new technology and trying out different approaches to problem-solving.