Windows Server 2012 does not have a Remote Desktop license server that can provide a license for a remote session to be interrupted

Remote access is not possible today when you log in to a server inside your company.

Pop-up error message: No Remote Desktop license server can provide license, remote session is interrupted

After searching the web, the server 2012 Telnet only provides a 120-day lifespan.

The solution is in two steps:

One. Refer to the following article

Http://blog.sina.com.cn/s/blog_5e8c26990102w7bc.html

WORKAROUND: The remote session was interrupted because no license was available for the Remote Desktop license server. This post contains pictures ( -- One- +  +: the: -Reprint Label: server2012 Remote Desktop Licensing Server license Remote session was interrupted when the Windows Server 2012 Server Remote Desktop Logon error message occurs: "The remote session was interrupted because no Remote Desktop licensing server can provide a license." Please contact the server administrator. You can now use the mstsc/admin/V: Target IP "to force the logon server, but only for administrator status. WORKAROUND: The remote session was interrupted because no license was available for the Remote Desktop license server. According to some method on the Internet, remove the following key from the registry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing. Does not resolve the problem, a new error message appears, such as the second diagram: "The remote session has been disconnected because access is denied causing the creation of the license store to fail." Run the Remote Desktop client with elevated privileges. "Fundamentally resolved: The remote session was interrupted because no Remote Desktop licensing server could provide a license." Microsoft's official explanation is (source this link to http://blog.163.com/smile_big/blog/static/35710579201311982024/):Microsoft Official Explanation: This issue occurs because the Windows store application does not have sufficient permissions to access the MSLicensing registry key or the subkey store. Therefore, when an application connects to a remote server, the Remote Desktop ActiveX interface cannot access the registry in-process COM objects and stops the connection process. Resolution: Warning: If you modify the registry incorrectly by using Registry Editor or other methods, serious problems may occur. These issues may require you to reinstall your operating system. Microsoft cannot guarantee that these issues will be resolved. You are responsible for modifying the registry at your own risk. Baidu basically can not find a feasible solution, Google get the Final Solution: the solution is to delete the REG_Binaryinchhkey_local_machine\system\currentcontrolset\control\terminal Server\rcm\graceperiodonly leaving thedefault. and reboot. From http://anilgprabhu.blogspot.com/2014/05/reset-trial-terminal-license-on-windows.htmlthe root cause is that the server -or Server 2008, such as the default maximum Telnet link is 2, more than this number needs to use license server authorization, this authorization is said to be charged, but the official gave a 120-day grace period to configure License server. If license server is still not available after 120 days, the first error will occur. And this grace period information is recorded in the registry above, so as long as you delete the entries in the registry (you need to modify this registry key permissions to the owner of administrators, to administrators add Modify permissions), restart the server. It has also been mentioned that you can modify the system time for the future, then delete the registry, and then change the system time back, so that you can get a longer grace period. This method applies to server2012 and should also be applied to 2008, but 2003 has not been tested. See the official Microsoft documentation for a glance: https://technet.microsoft.com/en-us/library/cc725933.aspxOf course, in addition to the opportunistic approach of modifying the registry, you can also deploy license server (server -or deploy license server and Remote Desktop Gateway (server2012), 2012 compared to 2008 has a relatively large change, configuration is more troublesome, interested can refer to the following link: http://www.wackytechtips.com/installing-and-configuring-remote-desktop-services-rds-on-windows-server-2012/3/ 

Two.

When you delete the Graceperiod item, you find the prompt error, and the deletion of this error should be a permission issue.

Then perform the following steps:

1.

2.

3.

4.

5. Remove the binary items under Graceperiod and restart the machine

Windows Server 2012 does not have a Remote Desktop license server that can provide a license for a remote session to be interrupted