![]() grant your user full control permission to the key computer\hkey_local_machine\system\CurrentControlSet\Control\Terminal Server\RCM\GracePeriodĤ. Removing the RDS licensing time-bomb registry entry with sysinternals pexec (downloaded from ) resolved the problem:ģ. However, I am somewhat suspicious that this only hacked the time bomb but did not actually activate the CAL licenses (none show used in RD License Manager).Īnyway, hope this helps someone not to waste hours. It had to actually be run under highest privileges with the help of Sysinternals: psexec -s -i regedit.exeĪfter another reboot things seem to be working now. Force-removing the RDS licensing time-bomb registry entry:Ĭomputer\hkey_local_machine\system\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod This got us to a stage where Licensing diagnostics looked good and no related local errors showed up in the server logs but remote sessions were still refused, leading to.Ģ. To reset the RDS licensing grace period, perform the following steps: On the RD session host, launch Registry Editor (regedit) as an administrator. Set the Remote Desktop licensing mode = Per User The following steps should not be performed on a server that is in production. Local Computer Policy -> Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Licensing ![]() ![]() The fall back is configuration via group policy: ![]() The graphical management tools for RDS Session Host Management are disabled when not oprerating a Domain (why?). Ok, I think I have it figured it out and consider this (a) bad product design and (b) a Server 2012 bug.ġ. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |