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. Today’s tip for home labs.ĭownload a PowerShell script from Microsoft allowing you to reset the RDS grace period. wmic /namespace:\rootCIMV2TerminalServices PATH Win32_TerminalServiceSetting WHERE (_CLASS !=””) CALL GetGracePeriodDaysĪpparently, you can delete this key every time it expires …. Note that you have also a possibility to check how many days its left… Go to the command prompt and enter this command (not tested).
You should see the message changing at the taskbar area…. Update: Well, in fact, you can just restart the Service “Remote Desktop Services” which will momentarily disconnect all the active sessions and then after a minute or so you can reconnect to the sessions. Some users have reported that when not rebooting the host you will see the message changing, but no connections are possible. Once you delete the Registry key you must reboot the host.
Note: You must first take an ownership and give admins the full rights. HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerRCMGracePeriod The solution is to delete the REG_BINARY in: Step 1: Connect to your RDS Server as an admin and open regedit.
Note: This tip works also on Windows Server 2016 and Windows server 2019įor every admin who runs homelab or has a cloud lab, this is a must known hack. Simply log out and back in and the message changes from let’s say 54 days left to 120 days left. In fact, you do not need to reboot the server either.
What we will do is simply reset the default timer which is 120 days grace time, when you first add the RDS role. (and many other IT pros who test stuff in the lab too). However, we don’t want to do that because we have no license from Microsoft, in our lab. Normally you would need to activate the RDS/TS CAL License server and point the Server to License server with User/Device License and will resolve the problem.