The following scenario assumes the grace period has ended. When a client has a Full CAL, that CAL has an expiration date associated with it, and it must be periodically renewed by the issuing license server.
The CAL allocation process can seem complicated, but by understanding how the process works, you can better understand where things can go wrong and where to look when trouble arises. Always verify the licensing mode of the Terminal Server in Terminal Services Configuration to be sure the server has not been inadvertently flipped from one mode to another.
Also, realize that the license server will never decrement the Per-User CAL pool s as these licenses are unmanaged. Finally, check the event logs on the Terminal Server, License Server and the client for clues to where the trouble may lie. In a future article, we will discuss troubleshooting techniques for locating where the process breaks down and how to correct it. Your email address will not be published.
Learn about the latest security threats, system optimization tricks, and the hottest new technologies in the industry. The grace period ends after days or once the Terminal Server locates a license server, whichever comes first. Once out of the grace period, in most cases the Terminal Server must be able to contact a license server to accept new connections.
Temporary CALs are issued to a client the first time they connect to a Terminal Server and are valid for 90 days. A license server can issue Temporary CAL regardless of whether the license server has been activated or not. In addition, Temporary CALs are generated by the license server itself so there is no limit to the number of Temporary CALs a license server can issue.
However, once a client has received a Temporary CAL, it can never receive another one, and once it expires, a Full CAL must be available for the client to connect. Beginning with Windows Server , Microsoft introduced a Per-User licensing model for connecting to Windows Terminal Servers, where the license is tied to the user as opposed to the device.
However, it is important to distinguish that this is not a concurrent user model — each user is licensed individually and exclusively. This licensing model was added just prior to the release of Windows Server , so Microsoft had no time to fully implement the licensing model as they had no existing way to attach a Terminal Server CAL to a user account. This is also the reason why we have a choice of licensing modes for a Terminal Server.
For more information on this, see Microsoft KB article Each device must be licensed in the environment as this is not a concurrent connection license. When the license server issues the CAL, a random expiration date is generated for the CAL, which expires between days from the date issued.
The limit of 89 days is key to the license recovery process. Here I am granting administrators full control on the key. Now, with permissions set, right-click the timebomb value in the GracePeriod key and Delete.
Next, the only thing left to do is reboot your server. Once the server is rebooted, you can enjoy once again having the full day grace period for your RDS server in the lab environment. The process to reset day RDS Grace period on and Windows Servers as well as older server versions such as Windows Server and R2 is very straightforward using this process to delete the timebomb registry key.
Keep in mind this is not supported and certainly not a process for running in production. However, it is very handy for lab environments to keep from having to redeploy Windows Server virtual machines simply to have a fresh day grace period.
Error after day grace period has expired for Remote Desktop Services. Navigate to the Advanced permissions properties. Change the ownership of the registry key. Submit ». Carl Holzhauer This person is a verified professional.
Verify your account to enable IT peers to see that you are a professional. Did you see this? Justin This person is a verified professional. Microsoft Remote Desktop Services expert.
Thai Pepper. Sajiin This person is a verified professional. Carl Holzhauer wrote: Did you see this? On the device side you can just revoke it.
On the User side that is not the case.
0コメント