When the grace period expires, Windows typically will reboot every hour until activated. The grace period it would seem is 30 days (which can be re-armed). The PowerShell script can be used to query and reset terminal server grace period to default 120 days if it is nearing to the end. We often need to deploy Terminal Server (Remote Desktop Session Host in 2012) for testing purposes in development environments allowing more than 2 concurrent Remote Desktop Sessions on it. Feb 24, 2017  Is there any way to reset Server 2012 R2 RDS trial for another 120 days? I know it's no problem on Server 2008/2008R2/2012, but have no info for 2012 R2 box. I can see EventID: 1128 Source: TerminalServices-RemoteConnectionManager description: The RD Licensing grace period has expired. On Server 2008/2008R2/2012 you just delete.

1. Windows Server 2012 R2 Rds Grace Period Reset Instructions
2. How To Reset Windows Server 2008 R2 Rds Grace Period

Hi, First of all sorry if this is in the wrong forum - since it involves sysprep I thought it was most appropriate here. So basically, I cant work out how to get sysprep to reset the RDS grace period on Windows Server 2008 R2. I am using: sysprep /generalize /oobe /reboot /unattend:Unattend.xml to sysprep the system and it works like a charm. The only problem I have now is that it wont reset the Remote Desktop Service's grace period it will continue to count down from 120days since it was originally installed on the system. I have tried activating the license server before running sysprep, and a few other hacky sort of things (ie: Delete%windir%System32LServer) without success. The grace period continues to countdown from 120 days from original install.

Any help on this matter would be great =) Regards. Sysprep to reset the RDS grace period? Are you correct? I have never heard about that.I only know sysprep can reset Windows Activation:Resetting Windows ActivationWhen you install Windows with a single license product key, you have 30 days during which you must activate that installation of Windows.

Volume License and OEM Activation RequirementsThere is no limit to the number of times that the Sysprep command can run on a computer. However, the clock for Windows Product Activation begins its countdown the first time Windows starts. You can use the sysprep /generalize command to reset Windows Product Activation a maximum of three times.

After the third time that you run the sysprep /generalize command, the clock can no longer be reset.When you run the sysprep /generalize command, the activation clock will automatically reset. You can bypass resetting the activation clock by using the SkipRearm setting in the Microsoft-Windows-Security-SPP component. This enables you to run the Sysprep command multiple times without resetting the activation clock.

For more information about this setting, see the Unattended Windows Setup Reference (Unattend.chm).Important:If you anticipate running the Sysprep command multiple times on a single computer, you must use the SkipRearm setting in the Microsoft-Windows-Security-Licensing-SPP component to postpone resetting the activation clock. Because you can reset the activation clock only three times, if you run the Sysprep command multiple times on a computer, you might run out of activation clock resets. We recommend that you use the SkipRearm setting if you plan on running the Sysprep command multiple times on a computer.Important:Before running the Sysprep command the final time before deploying the computer, rearm the computer by setting the SkipRearm setting to 0. This causes the activation timer to reset.You can review the number of times you can use the SkipRearm setting by using the slmgr /dlv command. For information, see.For volume licenses, activation clock reset behavior is different, depending on the type of license.Detecting the number of activations remaining Activation can be reset an unlimited number of times for an activated Key Management Service (KMS) clients. For non-activated KMS clients, the activation clock can be reset only up to three times, the same as a single license. We recommend that KMS clients use the sysprep /generalize command where the value of the SkipRearm setting is equal to 1.

After capturing this image, use the sysprep /generalize command, where the value of the SkipRearm setting is equal to 0. For Multiple Activation Keys (MAK) clients, the recommendation is to install the MAK immediately before running Sysprep the last time, prior to delivering the computer to a customer.For OEM Activation licenses, activation is not required. OEM Activation is available only to royalty OEMs.You can check the activation clock to see how many times you can use the sysprep /generalize command. For information, see.Activating Windows Before Shipping to a CustomerMost customers can easily manage activation after receiving their computers.

But if you prefer, you can activate the software on behalf of your customers, making it easier for them to start using their new computers. After activation is completed, most users will not need to activate their installation again.To activate Windows for your customer, use the unique Product Key from the certificate of authenticity (COA) label that is affixed to the specific computer, and activate the computer on behalf of the end user. Run the sysprep /oobe command to prepare the computer for delivery to the customer.Note:You cannot make an image of an activated Windows installation and duplicate that image to another computer.

If you do, Windows fails to recognize the activation and forces the end user to reactivate the installation manually.

Windows Server 2012 R2 Rds Grace Period Reset Instructions

EventID: 1128Source: TerminalServices-RemoteConnectionManagerThe RD Licensing grace period has expired and the service has not registered with a license server with installed licenses. A RD Licensing server is required for continuous operation.

How To Reset Windows Server 2008 R2 Rds Grace Period

A Remote Desktop Session Host server can operate without a license server for 120 days after initial start up.It appears that the RDSH server decided that the grace period of using the terminal server is over (120 days), and either it has to be extended or the RDS licenses have to be activated on a full-version server. It seems to be an RDS bug in Windows Server 2012.You can find out the current value of RDS Grace Period with this command:wmic /namespace:rootCIMV2TerminalServices PATH Win32TerminalServiceSetting WHERE (CLASS!=') CALL GetGracePeriodDaysTo solve this problem, you have to remove the key that determines the grace period of licensing on the RDS server. The date that determines the grace period for the server is stored in L$RTMTIMEBOMB key (quite a funny name — TIME BOMB.; ) located in the following registry branch:HKEYLOCALMACHINESYSTEMCurrentControlSetControlTerminal ServerRCMGracePeriodYou have to remove L$RTMTIMEBOMB key. However, the administrator doesn’t have relevant privileges to do it. Now, right-click L$RTMTIMEBOMB key and delete it.Restart your server, and connect to it using RDP client. Make sure that the license has been issued successfully in Remote Desktop Licensing Manager.However, I didn’t have it done at once.

Using this PowerShell command, make sure if the licensing server is set:$obj = gwmi -namespace 'Root/CIMV2/TerminalServices' Win32TerminalServiceSetting$obj.GetSpecifiedLicenseServerListAs you can see, the licensing server is not set (SpecifiedLSList is empty). Set the RD licensing server with the following command.$obj = gwmi -namespace 'Root/CIMV2/TerminalServices' Win32TerminalServiceSetting$obj.SetSpecifiedLicenseServerList('lon-rdslic.woshub.com')After it had been done, the server started issuing licenses to RD clients. Hi, Great run through.I had this issue and this worked for me, however I am in the process of moving to a new licensing server and although this works when initially defining a licensing server when I try and update the SetSpecifiedLicenseServerList parameter with the new server details$obj = gwmi -namespace 'Root/CIMV2/TerminalServices' Win32TerminalServiceSetting$obj.SetSpecifiedLicenseServerList('My-New-Server.Name ')I get the following error. Do you need to run a different command to update?Exception calling 'SetSpecifiedLicenseServerList': 'Invalid operation 'At line:1 char:1+ $obj.SetSpecifiedLicenseServerList('My-New-Server.Name')+ + CategoryInfo: NotSpecified: (:) , MethodInvocationException+ FullyQualifiedErrorId: WMIMethodExceptionAny help would be appreciated.Tony Reply.