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 another PC. Sometimes a connection error occurs when connecting to the RDP client. This error can occur in two cases:
- The remote session was disconnected because CALs are missing.
- The client cannot be opened because the server with licenses is not configured.
In this article we will look in detail at how to fix these two errors.
The 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. After which it can connect to the session node.
Errors may occur when connecting to the server; the reason is that the licensing settings for the server are incorrect or the grace period for licensing remote desktops has expired.
How to solve the problem:
Remote Desktop Client License missing
This error appears in already configured systems. As a rule, upon connection, a temporary license is issued for 120 or 180 days. After this period, the client encounters errors in the system. To correct the error, you must purchase a new temporary license. But to do this, you need to erase the old one from the program registry.
It is worth noting: before you delete a branch, it must be exported. This is necessary to be able to restore settings.
To restore registry settings, you must:
- Find file *. reg with the previous version.
- Double click on the file and confirm 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 key, a new error may appear, indicating 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 is working, it must be disabled:
- Open Start - Control Panel - User Accounts and Family Safety - User Accounts.
- Now you need to change the record control settings. To do this, there will be a similar link at the bottom of the page.
- Click on OK and restart the 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 a different name for the disabled option (Use accounts to protect your computer). We also click on OK and restart the computer.
After performing 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. This model is mainly used for organizational computers. For home use there is no point in connecting such a system.
A remote session can disconnect for two reasons:
- Lack of licenses.
- The remote session was disconnected because there are no servers available for licensing.
To ensure that the server has licenses, you must perform the following steps:
- 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 to combat such an error is to delete one branch in the registry. But first you need to check the server itself.
All versions of Windows, starting with XP, have a standard RDP (Remote Desktop Protocol) client that is used to connect to the Remote Desktop Service. Sometimes, when connecting to a terminal server via a remote desktop client, an error occurs: “the remote session was disconnected because there are no client licenses.”
This message can occur in two cases:
- The terminal server is not configured with a license server for Remote Desktop Services.
- The licensing server has not allocated client access licenses (CALs).
Let's take a closer look at both cases.
Setting up a license server
The error often occurs after some time in already configured connections, after 120 or 180 days. It is likely that when the connection was created, the client was issued a temporary license for a given period of time. To obtain a new temporary license, you must delete information about the expired license from the registry on the client machine. For this:
- Press Win+R and run the regedit command.
- Make a backup.
- Click File → Export → Range (Entire Registry) → Give a file name → Save.
- Open the branch: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing and delete MSLicensing.
- Then open a remote desktop connection with administrator rights. When opened, the new license will be registered in the registry.
Advice! To configure a profile for connecting client machines to a remote network, read the equipment instructions.
Checking CAL licenses
It is possible that the Terminal Server licensing server has run out of licenses. To do this, just wait until the license becomes available, or purchase and activate the required number of CAL licenses.
To check available and occupied CALs, use Terminal Server Licensing on server Windows:
- Open Start → Administrative Tools → Remote 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 Remote Desktop Services CALs per user that:
- installed on the licensing server;
- issued by the licensing server based on the specified report scope.
Option 1:
Step 1. We launch the registry editor with the Regedit command (with administrator rights).
How to call up the “Run” menu and type the “regedit” command, read the instructions at the link
We delete the entire registry branch with the name “MSLicensing” from the section:
Close the registry editor. This should be enough to solve the problem. If it doesn’t help, do “Step 2”.
Step 2. For limited accounts or when requiring elevated privileges, 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 computer RDS.JUPITER.NSU.RU with the same name and password that you use to log into the EDMS to create a new registry branch MSLicensing.
ALTERNATIVE SOLUTION:
1) Connect through a new server, instructions: How to log into a new 1C server
(you can even use a test login and password)
2) Stay working there or leave completely - How to exit 1C correctly
(if you logged in under the test window, just close the window)
3) The problem with logging into the old server will be solved automatically.
Remote desktop licenses are one of the most common services that are purchased separately for a virtual server. You can easily set up Remote Desktop Services client licenses yourself and take advantage of a free trial period of 120 days, only after which you can start paying for the exact number of licenses that you actually need.
Open the Server Manager window (it opens by default when you start the server) and select Add roles and features.
For correct installation and further successful configuration of the licensing server, Active Directory Domain Services must be installed on your server.
When you select the “Active Directory Domain Services” checkbox, a window will open for additional necessary services that will be installed; they must be accepted by clicking “Add Features”.
Then click “Next >” several times
Once the installation is complete, click Close and return to the Server Manager window to configure the Active Directory Domain Services installation.
In the window that opens, select “Add a new forest” and specify the name of the root domain (Root domain name) - this can be a completely arbitrary domain name, the existence of which is not required, for example, “test.domain”.
After clicking “Next >” you will be asked to create and specify a recovery password.
Then click “Next >” several times in subsequent steps and finally click “Install”.
Once the installation is complete, the server will automatically reboot.
After the reboot, we can proceed directly to installing the RDP remote connection licensing server. To do this, in the “Server Manager” window, select “Add roles and features” again and in the window that opens, “Remote Desktop Services installation”.
Then select “Session-based desktop deployment”
In further windows that open, simply click “Next >” until you reach the last one, where by selecting “Restart the destination server automatically if required”, click the “Deploy” button.
The server will be rebooted during installation. After rebooting, when connecting, you will see the following window, which after installation is complete, simply close.
After installation, the “Remote Desktop Services” tab will appear in the “Server Manager” panel.
By clicking on the “Remote Desktop Services” tab, you will see the RDP remote connection licensing server settings control panel.
In the next step, you will be asked to enter the name of the new certificate, which will be used to encrypt the connection between clients connecting via RDP and the server.
Then click on the “Add” button and wait until the system configuration is completed. When finished, the window will close automatically and only one icon will remain in the form of a green plus with the inscription “RD Licensing”
By clicking it, also follow the steps of the setup wizard:
In the next step, click on the final “Add” button and wait until the configuration is completed. When finished, the window will also close automatically.
Now we have installed the license management service directly and the “Remote Desktop Licensing Manager” application has become available to you (you can find it by opening all applications in the “Start” menu, or through the search bar there). Launch this application.
Select the line of your server (the only one in the screenshot), right-click and select “Review Configuration...”
Click on the button at the top “Change Scope...” of the window that opens and select “The forest”.
After successful addition, in the same configuration window, click the button below “Add to Group”. After confirming this action, the notification windows will close and the “Add to Group” button will disappear. Click the "OK" button below to close the window.
Select your server line again, right-click and select “Activate Server”.
In the window that opens, simply follow the steps of the setup wizard, filling out the required fields (full name, organization name, country, email, etc.).
At the last step, if you do not have your own licenses, uncheck “Start Install Licenses Wizard now” and click “Finish”.
After this, restart your server.
After the reboot, you will see a notification that the licenses are not installed and you have another 119 days before they must be purchased and installed on your server.
The setup and configuration does not end here. Return to the Server Manager window, go to the Remote Desktop Services tab and select TASKS -> Edit Deployment Properties.
In the window that opens, select “RD Licensing”. Here you need to select the licensing method for remote connections: per user (how many users can simultaneously connect to the server) or per device (how many different devices can simultaneously connect to the server). Once selected, click the “Apply” button and go to the “Certificates” tab.
Good day! Sometimes when connecting to a terminal server via the client "", an error may occur: " The remote session is disconnected because there are no Remote Desktop CALs available.» In this article I want to describe the reasons for this error and offer possible solutions to this problem.
So, when connecting to a terminal server via RDP, an error occurs: “The remote session was disconnected because there are no Remote Desktop CALs for this computer. »
This message may be seen in the following cases:
- There is no licensing server configured for Remote Desktop Services on the terminal server.
- There are no client access licenses (CALs) left on the licensing server.
Let us consider these situations in more detail, and also outline ways to eliminate them.
1. Setting up a licensing server
You can read about installing a terminal server, as well as setting up a remote desktop licensing server and activating licenses in the following articles:
If the remote desktop connection to the terminal server was previously working, it is possible that the client was issued a temporary license for 180 days, and this license has already expired. In order to re-obtain a temporary license, you must: client machine remove information about a valid expired license from the registry.
Launch the registry editor. You can do this 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»).
When the Registry Editor starts, you need to delete the following directory:
HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing
After uninstallation, you must start the client with , so that a new temporary license is registered in the registry.
2. Lack of CALs
If the license server that licenses this terminal server runs out of licenses, you must wait until someone releases 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 the report was created;
- report area, for example Domain, OU=Sales or All trusted domains;
- the number of Remote Desktop Services CALs per user installed on the licensing server;
- The number of Remote Desktop Services CALs per user issued by the licensing server based on the specified report scope.
The generated reports are displayed on the " tab Reports» in Remote Desktop Licensing Manager.
Did this article help you?
