Windows server 2012 server Remote Desktop login with an error message: "The remote session was interrupted because no Remote Desktop authorization server was available to provide the license. Contact your server administrator.
"At this time, you can use "mstsc /admin /v:target IP" to force the login to the server, but only as an administrator.
Fundamental Resolution: The remote session was interrupted because no Remote Desktop Authorization Server could provide the license.
Follow a method on the Internet to delete the following items in the registry: HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing.
This does not solve the problem, and then a new error message appears, as shown in the second image: "The remote session has been disconnected because access was denied causing the license store to fail to create." Run the Remote Desktop client with elevated privileges. ”
Fundamental Resolution: The remote session was interrupted because no Remote Desktop Authorization Server could provide the license.
Microsoft's official explanation:
Cause:
This issue occurs because the Windows Store app does not have sufficient permissions to access the MSLicensing registry key or child key store. As a result, when the application connects to the remote server, the remote desktop ActiveX interface is unable to access the registry in the in-process COM object and the connection process is stopped.
Solution:
Warning: Serious problems that can occur if the registry is modified incorrectly using the Registry Editor or other methods. These issues may require you to reinstall the operating system. Microsoft cannot guarantee that these issues will be resolved. Modifying the Registry is at your own risk.
Google gets the final solution:
The solution was to delete the REG_BINARY in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod
Only leaving the default.
And reboot.
From http://anilgprabhu.blogspot.com/2014/05/reset-trial-terminal-license-on-windows.html
The fundamental reason is that the default maximum remote login link for Server 2012 or Server 2008 is 2, and more than this number requires the use of the license server for authorization, which is said to be charged, but the official gives a grace period of 120 days to configure the license server. If there is still no license server available after more than 120 days, the first error occurs. This Grace period information is recorded in the registry above, so just delete the items in the registry (the owner of this registry key is Administrators, and add modification permissions to Administrators), and restart the server. It is also mentioned that the system time can be changed to the future, then delete the registry, and then change the system time back, so that you can get a longer grace period. This method works for server2012 and should work for 2008 as well, but 2003 has not been tested.
Referring to the explanation of Microsoft's official documentation, it is clear at a glance:
https://technet.microsoft.com/en-us/library/cc725933.aspx
Of course, in addition to the opportunistic method of modifying the registry, you can also deploy the license server (Server 2008) or deploy the license server and remote desktop gateway (server2012), 2012 has relatively large changes compared to 2008, and it is more troublesome to configure, if you are interested, you can refer to the following link:
http://www.wackytechtips.com/installing-and-configuring-remote-desktop-services-rds-on-windows-server-2012/3/
|
Posted on 10/17/2017 2:14:55 PM
|
|
|
|
