Shulou(Shulou.com)06/01 Report--

This article will explain in detail how to solve the problem of remote desktop login on Windows server 2012 server. The editor thinks it is very practical, so I share it with you for reference. I hope you can get something after reading this article.

An error occurred when logging in to the remote Desktop of the Windows server 2012 server: "the remote session was interrupted because there is no remote Desktop license server to provide a license. Please contact the server administrator." At this point, you can use "mstsc / admin / v: target ip" to force login to the server, but only as an administrator.

In one of the ways described online, delete the following key from the registry: HKEY_LOCAL_MACHINE\ Software\ Microsoft\ MSLicensing.

Does not solve the problem, and then a new error message appears, such as the second figure: "the remote session has been disconnected because the creation of the license store failed because access was denied. Please run the remote Desktop client with elevated permissions."

Microsoft's official explanation is:

Microsoft's official explanation:

Reason:

This problem occurs because the application of the Windows App Store does not have sufficient permissions to access the MSLicensing registry key or subkey store. Therefore, when the application connects to the remote server, the remote Desktop ActiveX interface cannot access the registry in-process COM objects and stops the connection process.

Solution:

Warning: serious problems that can occur if you modify the registry incorrectly using Registry Editor or other methods. These problems may require you to reinstall the operating system. Microsoft cannot guarantee that these problems will be solved. Modify the registry at your own risk. --! Sweat.

Download the automatic fix: click on me to download

Manual repair steps:

1. Start the Registry Editor. To do this, follow these steps:

a. Touch the right side of the screen and click search. Or, if you use the mouse, point to the lower right corner of the screen, and then click search.

b. In the search box, type regedit.exe.

c. Click or click the regedit.exe icon that appears.

two。 Configure permissions for the MSLicensing registry key. To do this, follow these steps:

a. Locate the following registry subkey:

HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ MSLicensing

b. Right-click the MSLicensing key, and then click permissions.

c. Click add, and in the Select user or Group dialog box, click or click the location.

d. Select the local computer in the list at the top and click or click OK.

e. Type the following values in the select box by entering the object name: all packages for the application

f. Click or click OK.

g. Make sure you have read permissions to enable all Application packages, and then click or click OK.

3. Configure permissions to store registry keys. To do this, follow these steps:

a. Locate the following registry subkey:

HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ MSLicensing\ Store

b. Right-click to store the key, and then click permissions.

c. Click or click add. In the Select user or Group dialog box, click or click the location.

d. Select the local computer in the list at the top and click or click OK.

e. Type the following values in the enter object name to select box:

All packages for the application

f. Click or click OK.

g. Make sure that read permissions for all Application packages are enabled.

h. Click or click Advanced.

i. On the permissions tab below, select all application packages for the entry, and then click or click Edit.

j. In the permissions project window of the storage area, click or click the Show Advanced permissions link.

k. Make sure that the following four check boxes are selected:

Query value

Set valu

Create a child

Enumerate subitems

l. Click or click OK three times.

4. Exit Registry Editor.

Microsoft's official explanation:

Reason:

This problem occurs because the application of the Windows App Store does not have sufficient permissions to access the MSLicensing registry key or subkey store. Therefore, when the application connects to the remote server, the remote Desktop ActiveX interface cannot access the registry in-process COM objects and stops the connection process.

Solution:

Warning: serious problems that can occur if you modify the registry incorrectly using Registry Editor or other methods. These problems may require you to reinstall the operating system. Microsoft cannot guarantee that these problems will be solved. Modify the registry 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 root cause is that the default maximum number of remote login links such as server 2012 or server 2008 is 2. If you exceed this number, you need to use license server for authorization, which is said to be a fee, but the official Grace period is given 120 days to configure license server. If no license server is available after more than 120 days, the first error occurs. This Grace period information is recorded in the registry above, so just delete the key in the registry (you need to change the owner of this registry key to Administrators, and add the permission to modify to Administrators), and restart the server. Someone also mentioned that you can change the system time 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 applies to server2012 and should also apply to 2008, but 2003 has not been tested.

It is clear at a glance by referring to the explanation in Microsoft's official documentation:

Https://technet.microsoft.com/en-us/library/cc725933.aspx

Of course, in addition to the opportunistic way to modify the registry, you can also deploy license server (server 2008) or license server and remote desktop gateway (server2012). Compared with 2008, 2012 has a larger change and is more troublesome to configure.

On "how to solve the Windows server 2012 server remote desktop login problems" this article is shared here, I hope the above content can be of some help to you, so that you can learn more knowledge, if you think the article is good, please share it out for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.