AWS, Cloud Computing

3 Mins Read

Resetting Windows Server Grace Period Using AWS Fleet Manager

Voiced by Amazon Polly

Introduction

The grace period in Windows Server is after installation, where the server can be used without activation, typically lasting 180 days. During this time, the system operates with full functionality but prompts users to activate the product. If not activated within the grace period, the server enters reduced functionality mode, limiting access to certain features.

Resetting the grace period allows administrators to extend the trial period, which can be useful for testing, migrations, and license management. The reset can be performed using the command slmgr.vbs /rearm in an elevated Command Prompt or PowerShell. Each server allows three resets.

However, this should be done cautiously to avoid violating licensing terms or exposing the system to security risks. After the grace period expires and resets are exhausted, activation becomes mandatory to continue using the server.

While it’s common to reset the terminal server by logging directly into a Windows server, there are times when we forget to reset the grace period, preventing us from logging in via RDP. In such cases, AWS Fleet Manager offers a solution. AWS Fleet Manager, a service within AWS Systems Manager, helps users efficiently manage and maintain their fleets of EC2 instances, on-premises servers, and virtual machines (VMs). Using Fleet Manager to reset the grace period is simpler and less time-consuming than traditional approaches.

Resetting the grace period essentially extends this trial period, giving you additional time to activate the system before reduced functionality takes effect.

Pioneers in Cloud Consulting & Migration Services

  • Reduced infrastructural costs
  • Accelerated application deployment
Get Started

Prerequisites

Before you proceed with resetting the grace period, there are a few prerequisites that must be met:

  • The Server Must Be Running Windows Server: The grace period reset is relevant only to Windows Server installations.
  • SSM Agent Installed (For Remote Management): If you’re using AWS Fleet Manager or remote management tools, ensure the SSM Agent is installed and running on your server.
  • Administrator Privileges: You must have administrator rights on the server to execute the necessary commands for resetting the grace period.

Step-by-Step Guide

  1. Ensure that the SSM agent is installed and online on the Windows server, and only then can we use the AWS Fleet Manager.
  2. Go to AWS Systems Manager.
  3. On the left-hand side, navigate to AWS Fleet Manager & search for the Instance on which you want to reset the grace period. (Ping status of the server should be Online)

step3

4. Open the server, and on the left-hand side, navigate to the Windows registry.

step4

5. Now go to this path: HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Terminal Server/RCM/GracePeriod

step5

6. Now delete the TIMEBOMB.

step6

7. After deleting TIMEBOMB, restart the server and use this command to check the grace period.

Command: wmic /namespace:\\root\CIMV2\TerminalServices PATH Win32_TerminalServiceSetting WHERE (__CLASS !=””) CALL GetGracePeriodDays

step7

Conclusion

Resetting or managing the Terminal Server grace period is essential to maintaining uninterrupted access to Remote Desktop Services (RDS) on your Windows Server.

The grace period provides a temporary window of 120 days to use RDS without a valid license, allowing administrators time to configure and install necessary RDS Client Access Licenses (CALs). Once the grace period expires, RDS functionality will be restricted unless proper licensing is in place.

Install the required RDS CALs, set up a Key Management Service (KMS), or use Active Directory-based activation to reset or extend the grace period. While the grace period cannot be reset indefinitely, ensuring the correct licensing will help you avoid disruptions and ensure compliance with Microsoft’s licensing policies.

By proactively managing the grace period and properly licensing your server, you can ensure that Remote Desktop Services continue to operate smoothly and efficiently, providing secure and reliable remote access for users across your network.

Drop a query if you have any questions regarding Remote Desktop Services 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 PartnerAWS Migration PartnerAWS Data and Analytics PartnerAWS DevOps Competency PartnerAWS GenAI Competency PartnerAmazon QuickSight Service Delivery PartnerAmazon EKS Service Delivery Partner AWS Microsoft Workload PartnersAmazon EC2 Service Delivery PartnerAmazon ECS Service Delivery PartnerAWS Glue Service Delivery PartnerAmazon Redshift Service Delivery PartnerAWS Control Tower Service Delivery PartnerAWS WAF Service Delivery PartnerAmazon CloudFront and many more.

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

FAQs

1. Can I use RDS without a license server?

ANS: – No, you cannot use Remote Desktop Services without a License Server. The License Server manages and issues RDS CALs to clients. You must install and activate a License Server on your network to use RDS.

2. How long does the Terminal Server grace period last?

ANS: – By default, the Terminal Server grace period lasts 120 days from enabling Remote Desktop Services (RDS) on a server. After the grace period expires, the server will stop accepting remote connections unless it is properly licensed with RDS CALs.

WRITTEN BY Ashutosh Dange

Share

Comments

    Click to Comment

Get The Most Out Of Us

Our support doesn't end here. We have monthly newsletters, study guides, practice questions, and more to assist you in upgrading your cloud career. Subscribe to get them all!