Good afternoon, dear readers and subscribers, last time we solved the error that the search in outlook 2013 does not work. Today we will not touch the office products of Microsoft, but we will analyze the error in the operation of an RDP connection on a terminal server running Windows Server 2012 R2. An employee tries to connect to a remote desktop, but instead of a familiar working environment, he receives an error: The remote session is disconnected because the remote desktop client license stored on this computer has been changed. And as a result, it kicks off the user, preventing him from logging in via a remote connection. Below we will look at how to deal with this.
The cause of the error stored on this computer has been changed
Let's see why you have this problem, these are echoes of another error: Error remote session disconnected because there are no available Remote Desktop licensing servers, at that time we ran out of licenses on the terminal server, for client connections and as a result we did not were able to get in. As a result of this, in some cases you 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 the remote session is disconnected because the remote desktop client license stored on this computer has been changed is popping up on client operating systems like Windows 10 or 8.1
I will describe how I fixed this on Windows 10, but it will work for any OS version. Open the Windows Registry Editor.
Go to the registry branch
HKEY_LOCAL_MACHINE \ Software \ Microsoft \ MSLicensin
And completely delete the entire section, through the right click.
We confirm the deletion. Then we restart the computer.
Once you have rebooted, press WIN + R and type mstsc / admin to open a Remote Desktop window as administrator.
We can all try to connect to your terminal server.
If it does not help, then try to create a bat file and execute it, below is the content.
Const HKLM = & H80000002
Const MSLicensingStore = "Software \ Microsoft \ MSLicensing \ Store \"
Set oReg = GetObject ("winmgmts: \\. \ Root \ default: StdRegProv")
RetVal = oReg.EnumKey (HKLM, MSLicensingStore, RegKeys)
If RetVal<>0 Then
MsgBox ("Failed to read registry key" & MSLicensingStore)
WScript.Quit
End If
If IsArray (RegKeys) Then
For Each Key In RegKeys
KeyName = MSLicensingStore & Key
If InStr (1, UCase (KeyName), "LICENSE")> 0 Then
RetVal = 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 it.
Good day! Sometimes, when connecting to a terminal server through the client "", an error may occur: " The remote session is disconnected because there are no Remote Desktop CALs.»In this article, I want to describe the causes of this error and suggest possible solutions to this problem.
So, when connecting to a terminal server via RDP, an error occurs: “The remote session is disconnected because there are no Remote Desktop CALs for this computer. "
This message can be seen in the following cases:
- There is no licensing server configured for Remote Desktop Services on the terminal server.
- There are no CALs left on the license server.
Let's consider these situations in more detail, and also outline the ways to eliminate them.
1. Configuring the licensing server
You can read about installing a terminal server, as well as setting up an RD Licensing server and activating licenses in the articles:
If the remote desktop connection to the terminal server worked before, then this client may have been issued a temporary license for 180 days, and this license has already expired. In order to re-obtain a temporary license, you need to client machine delete information about the current expired license from the registry.
Launch the registry editor. This can be done by running the command regedit.exe (« Start» - « Find programs and files"Or" Start» — « Execute"Or press the key combination Win + R and enter the command name in the " Execute»).
In the registry editor that starts, delete the following directory:
HKEY_LOCAL_MACHINE \ Software \ Microsoft \ MSLicensing
After removal, you must definitely start the client with, so that a new temporary license is registered in the registry.
2. Lack of CAL licenses
If the licensing server that is licensing this terminal server runs out of licenses, you must wait for someone to release the license, or purchase and activate the required number of CALs.
You can view the total, used, and available number of licenses in the Terminal Server Licensing snap-in. To open this snap-in, you need to consistently go to the menu " Start» - « Administration» - « Remote Desktop Services» - « Remote Desktop Licensing Manager»
- date and time of the report creation;
- report area, for example Domain, OU = Sales, or All trusted domains;
- the number of RDS User CALs installed on the license server;
- The number of RDS User CALs issued by the licensing server based on the specified report area.
The generated reports are displayed on the " Reports»In Remote Desktop Licensing Manager.
Did this article help you?
Any Windows operating system has a standard RDP client that allows you to view and work from your computer, even if the user is behind a different PC. Sometimes, when connecting to an RDP client, a connection error occurs. This error can occur in two cases:
- The remote session has been disconnected because there are no CALs.
- The client cannot be opened because the server with licenses is not configured.
In this article, we will analyze in detail how to fix these two errors.
Remote Desktop Licensing Server is unavailable
To activate a user or device on 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 obtain a license. If there is a free license on the server, it is sent to the client. Then he can connect to the session host.
When connecting to the server, errors may occur, the reason is an incorrect licensing setting for the server or the grace period for remote desktop licensing has expired.
How the problem is solved:
Missing Remote Desktop CAL
This error appears on already configured systems. As a rule, upon connection, a temporary license is issued for 120 or 180 days. After this period, the client is faced with errors in the system. To fix the error, you need to purchase a new temporary license. But for this you need to erase the old one from the program registry.
It should be noted that before you can remove a branch, you need to export it. This is necessary to be able to restore the settings.
To restore registry settings, you must:
- Find file *. reg with the previous version.
- Double click on the file and confirm the import.
You can also restore the original data from the registry itself. To do this, select File-> Import and specify the previously created file.
Sometimes, after deleting a registry branch, a new error may appear, which indicates that the remote computer disconnected the session due to an error in the license protocol.
To solve the problem, you need to run the RDP client from your account or from the command line. In both cases, you must log in as an administrator.
If User Account Control works, it must be disabled:
- Open Start - Control Panel - User Accounts and Family Safety - User Accounts.
- Now you need to change the parameters of the control of records. To do this, there will be a similar link at the bottom of the page.
- Click on OK and restart your computer.
This instruction is relevant for computers with Windows 7. There are some users who still have Windows Vista, for them there are no special changes in the instructions. The only difference is another name for the option to be disabled (Using accounts to protect your computer). Also click on OK and restart your computer.
After completing these steps, the problem should be resolved.
Conclusions on the article
A remote computer is created so that the user can work on it even from another device. Basically, this model is used for computers in an organization. For home use, it makes no sense to connect such a system.
The remote session can be disconnected for two reasons:
- Lack of licenses.
- The remote session has been disconnected because there are no servers available for licensing.
In order to make sure that the server has licenses, you need to do the following:
- Go to the RDP client manager.
- Click Actions - Create reports. All information on available permissions for use will appear in the window.
The most effective method in dealing with such an error is to delete one branch in the registry. But first you need to check the server itself.
Option 1:
Step 1. Launch the registry editor with the Regedit command (with administrator rights).
How to call the "Run" menu and type the command "regedit" read in the instructions on the link
Delete the entire registry branch named "MSLicensing" from the section:
Close the registry editor. This should be enough to solve the problem. If it doesn’t help, we do “Step 2 ″.
Step 2. For limited accounts or when elevated privileges are required, you will need to perform additional operations:
Run "Start-Programs-Accessories-Remote Desktop Connection" (mstsc.exe) with administrator rights (right-click on the program - "Run as administrator")
and connect to the RDS.JUPITER.NSU.RU computer with the same name and password that you use to enter the EDMS to create a new MSLicensing registry branch.
ALTERNATIVE VARIANT OF THE SOLUTION:
1) Connect via a new server, instructions: How to log into a new 1C server
(you can even use a test username and password)
2) Stay to work there or fully exit - How to exit 1C correctly
(if you went under the test, just close the window)
3) The problem with logging into the old server will be solved automatically.
