One computer will upload a license on a remote server. Eliminate the RDP error: "The remote session is disabled since there are no client licenses

Tariffs

In any Windows operating system, there is a standard RDP client that allows you to view and work from your computer, even if the user is after another P. K. Sometimes the connection error occurs when connected to the RDP client. This error may occur in two cases:

A remote session is disabled, since there are no client licenses.
Unable to open the client, since the server with licenses is not configured.

In the article, we will analyze in detail how to fix these two errors.

Remote Desktop Licensing Server Unavailable

To activate a user or device in the server, you must provide a license for the RDP client. To obtain a license, the server sends a request on behalf of the client to receive a license. If the server has a free license, then it is sent to the client. After that, it can connect to the session node.

When connecting to the server, errors may occur, the reason is incorrect setup of licensing for the server or the grace period of licensing remote desktops expired.

How the problem is solved:

There is no client remote desktop license

This error appears in the already configured systems. As a rule, when connected, a temporary license is issued for 120 or 180 days. After this period, the client faces errors in the operation of the system. To correct the error, you must purchase a new temporary license. But for this you need to erase old from the registry of programs.

It is worth noting: before remove the branch, it must be exported. This is necessary to restore the settings.

To restore the registry settings, you must:

Find file *. REG with the previous version.
Press the file twice and confirm the import.

You can also restore the source data from the registry itself. To do this, select File-\u003e Import and specify the previously created file.

Sometimes after removing the registry branch, a new error may appear, which will indicate that the remote computer disabled the session due to the error in the license protocol.

To solve the problem, you need to start the RDP client from the account or from the command line. In both cases, it is necessary to enter the administrator.

If the tool of user accounting is running, it must be turned off:

Open Start - Control Panel - User Accounts and Family Security - User Accounts.
Now you need to change record control settings. To do this, at the bottom of the page will be a similar link.
Click on OK and reboot your computer.

This manual is relevant for computers with Windows 7. There are such users who still have Windows Vista, there are no special changes in the instructions. The only difference is another name of the disabled option (using credentials to protect the computer). Also click on OK and reboot the computer.

After performing such actions, the problem should be solved.

Conclusions by article

A remote computer is created to ensure that the user can work for it even from another device. Basically such a model is used for computer computers. For home use, it makes no sense to connect such a system.

A remote session can be disconnected for two reasons:

License shortage.
A remote session is disabled, since there are no available licensing servers.

In order to make sure that the server has licenses, you must perform the following steps:

Go to the RDP client dispatcher.
Press the steps - Create reports. All information on available permissions for use will appear in the window.

The most efficient method in the struggle of such an error is the removal of one branch in the registry. But at first it is necessary to check the server itself.

Option 1:

Step 1. Run the registry editor by the Regedit command (with administrator rights).

How to call the "Run" menu and dial the "Regedit" command in the reference instructions.

We remove the entire registry branch named "Mslicensing" from the section:

Close Registry Editor. This should be enough to solve the problem. If it did not help - we do "Step 2".

Step 2. For limited accounts or at the request of elevated privileges, you will need to additionally perform operations:

Run "Start-Start-Standard-Connection to Remote Desktop" (mstsc.exe) with administrator rights (click on the program Right-click - "Run on the name of the administrator")

and connect to the rds.jupiter.nsu.ru computer with the same name and password that you use to enter the EDD to create a new MSLicensing registry branch.

Alternative solution:

1) Connect through a new server, instruction: How to go to a new server 1c

(even under test login and password)

2) stay to work there or fully exit - how to get out of 1c

(if you came under test just close the window)

3) The problem with the input to the old server will be solved automatically.

Good day Dear readers and subscribers, last time we solved the error that the search for Outlook 2013 did not work. Today, we will not touch Microsoft's office products, and we will analyze the error in the RDP connection, to the terminal server running Windows Server 2012 R2. An employee tries to connect to the remote desktop, and in the place of the usual work environment it receives an error: the remote session is disabled, since the remote desktop client license stored on this computer has been changed. And as a result, removes the user without letting it go on a remote connection. Below we will look at how to deal with it.

Causes of mistakes stored on this computer has been changed

Let's figure it out, because of what you have this problem is, it is an echo of another error: an error Remote session is disabled because there are no available licensing servers for remote desktops, at that time on the terminal server ended with licenses for client connections and as a result, we are not Could get. As a result, you in some cases may have a problem in the Windows registry leading to an error that the client license stored on this computer has been changed.

In most cases, the error remote session is disabled, since the remote desktop client license stored on this computer has been changed, pops up on client operating systems, by type Windows 10 or 8.1

I will describe how I removed it to Windows 10, but it will suit any version of the OS. Open Windows registry editor.

Go to the registry branch

HKEY_LOCAL_MACHINE \\ SOFTWARE \\ Microsoft \\ Mslicensin

And completely remove the entire section, through the right click.

Confirm removal. After that reboot the computer.

Once you have rebooted, press Win + R and enter MSTSC / ADMIN so that you have a remote desktop window on behalf of the administrator.

We can all try to connect to your terminal server.

If it does not help, try to create a BAT file and execute it below the content.

Const HKLM \u003d & H80000002
Const MsLicensingstore \u003d "Software \\ Microsoft \\ MsLicensing \\ Store \\"
SET OREG \u003d GetObject ("WinMgmts: \\\\. \\ Root \\ default: stdregprov")
Retval \u003d oreg.Enumkey (HKLM, MSLICENSINGSTORE, REGKEYS)
IF Retval<> 0 Then.
MSGBox ("Failed to read the registry branch" & MslicensingStore)
Wscript.quit.
End if
IF Isarray (Regkeys) THEN
For Each Key in Regkeys
Keyname \u003d MsLicensingStore & Key
IF Instr (1, UCASE (KeyName), "License")\u003e 0 THEN
Retval \u003d Oreg.DeleteKey (HKLM, KEYNAME)
End if
Next
End if

Also, if you have a terminal server on Windows 7, then check the operation of the module, you may have to reinstall.

In all versions of Windows, starting with XP, there is a standard RDP client (Remote Desktop Protocol), which is used to connect to the service of remote desktops. Sometimes, when connecting to the terminal server, an error occurs through the remote desktop client: "The remote session is disabled since there are no client licenses."

This message may occur in two cases:

The Terminal Server does not configure the licensing server for the service of remote desktops.
The licensing server has not allocated client access licenses (CAL).

Let us consider in more detail both cases.

Configuring a licensing server

The error occurs more often after a while in already configured connections, 120 or 180 days later. It is likely that when creating a connection, a temporary license was issued to the client for a given period. To get a new temporary license, you need to remove information about the overdue license from the registry on the client machine. For this:

Press Win + R and execute the REGEDIT command.
Make backup.
Click "File" → "Export" → "Range (entire registry)" → Name the file name → "Save".
Open the branch: HKEY_LOCAL_MACHINE \\ Software \\ Microsoft \\ Mslicensing and remove MsLicensing.
Then open the connection to the remote desktop with the administrator rights. When opening, the new license is registered in the registry.

Tip! To configure the profile to connect client machines to a remote network, read the instructions to snap.

CAL Verification - Licenses

This option is possible that licenses ended on the terminal server licensing server. To do this, just wait for the license to be free, or purchase and activate the required number of CAL licenses.

To check available and busy CAL, use the "Terminal Server Licensing" on the server Windows:

Open "Start" → "Administration" → "Deleted Desktop Services" → "Remote Desktop Licensing Manager".
Select your license server.
In the window that opens, click "Action" → "Create Report".

The report will display the number of client licenses of remote desktops "by user" which:

installed on the licensing server;
issued by the licensing server, taking into account the specified report area.