Since there are no client computers for this computer. Error "The remote session has been disabled because there are no Remote Desktop CALs"

Good day! Sometimes when connecting to the terminal server through the client "", an error may occur: " The remote session is disabled because there are no Remote Desktop CALs.» In this article, I want to describe the causes of this error and suggest possible solutions this problem.

So, when connecting to a terminal server via RDP, an error occurs: “The remote session has been disabled because there are no remote desktop client licenses for this computer. »

This message can be seen in the following cases:

1. There is no license server configured for Remote Desktop Services on the terminal server.
2. There are no client access licenses (CALs) left on the license server.

Let's consider these situations in more detail, and also indicate ways to eliminate them.

1. Setting up the license server

You can read about installing a terminal server, as well as configuring a remote desktop license server and activating licenses in the following articles:

If the connection via Remote Desktop 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 must client machine remove from the registry information about the current expired license.

We start the registry editor. You can do this by running the command regedit.exe (« Start» - « Find programs and files", or " Start» — « Run» or press the key combination Win+R and enter the name of the command in the window " Run»).

In the launched registry editor, you must delete the following directory:

HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing

After removal, it is necessary to start the client with in order for the new temporary license to be registered in the registry.

2. Lack of CALs

If the license server that licenses 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 sequentially go to the menu " Start» - « Administration» - « Remote Desktop Services» - « Remote Desktop Licensing Manager»

• date and time the report was created;
• report scope, such as Domain, OU=Sales, or All trusted domains;
• the number of Remote Desktop Services Per User CALs installed on the license server;
• The number of Remote Desktop Services Per User CALs issued by the license server based on the specified scope of the report.

The generated reports are displayed on the tab " Reports» in the Remote Desktop Licensing Manager.

Did this article help you?

I recently ran into an unexpected problem, in January I installed and configured windows server 2012, everything was done according to TK

those. Windows Server 2012 is used in a workgroup (without using a domain), purchased client certificates are installed to connect to the terminal server,

the license server is installed and activated.

Everything worked fine for exactly 120 days after that an error occurred

« Remote session because there are no Terminal Server license servers available to perform licensing. Contact the server administrator«.

The question arose of how and why.

First of all, we went to

Server Manager\Remote Desktop Services\Servers

They checked that

1. Windows server 2012 activated

2. Services started: remote desktops ,

Server Manager\Local Server

there was an error

The Remote Desktop Licensing grace period has expired and the service has not been registered with the license server with the licenses installed. For permanent operation, a Remote Desktop Licensing Server is required. An RD Session Host server can operate without a license server for 120 days from the date of initial launch.

remote desktop licensing mode not set

However, the licensing mode is set and the licensing service is configured and the server itself is activated.

It turned out that in latest versions microsoft windows server 2008 2008 r2 2012 recommend using a domain, while both licensing modes work,

and in the absence of a domain, only the licensing mode per device is possible, and after 120 days the licensing mode per user stops working and it becomes impossible to connect to the server via RDP.

fix this situation open Powershell or run winkey+r

We configure local policies for servers located in the workgroup

In the terminal line we write gpedit.msc and change the corresponding keys.

Use specified Remote Desktop license servers(add the name of our server or its ip address)

Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Licensing - Set Remote Desktop Licensing Mode

English version:

Use the specified Remote Desktop license servers(add the name of our server or its ip address)

Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Licensing - Set the Remote licensing mode (select the type of licenses for the device)

Important! If we choose per user licensing mode then the error will remain and the server will keep repeating that no license servers available, because in A workgroup can only have a per-device licensing mode.

open all servers - right click on our server - license management

dalle - rebuild license server database - remote desktop licensing database corrupted

click the checkbox to confirm the removal of licenses installed on this server

open license agreement enter your authorization number and license number if you have purchased Windows.

the type of licenses must be selected for the device.

Then restart the services: remote desktop licensing and remote desktops

or restart the server, after which you can connect to the server again via RDP

When you try to remote desktop a Windows VM in Azure, you might encounter certain errors. This article describes some of the most common error messages and steps to resolve them. If you are unable to connect to virtual machine via RDP protocol, but no error message appears, see .

For some specific errors, see later in this article.

The remote session is disabled because there are no remote desktop license servers available to perform licensing.

Cause: The 120-day licensing grace period for the Remote Desktop Server role has expired and you need to install licenses.

As a solution, you can save a local copy of the .rdp file from the portal and then establish a connection by running the following command in command line PowerShell. This step will disable licensing for the current connection only.

Mstsc .RDP /admin

If you don't plan on having more than two simultaneous remote desktop connections to a virtual machine, you can remove the Remote Desktop Server role using Server Manager.

For more information, see the blog post RDP to Azure VM fails with "No Remote Desktop License Servers available".

The Remote Desktop Service cannot find the computer name.

Cause: The Remote Desktop Client cannot resolve the computer name in the .rdp file settings.

Possible Solutions

• If you are working on an organization's intranet, make sure that your computer has access to the proxy server and the ability to send data to it over HTTPS.

If you're working with a local .rdp file, try using the file created using the portal. In this step, you will verify that the VM's DNS name, cloud service name, and VM endpoint port are correct. Here is an example of an RDP file generated by the portal:

Full address:s:tailspin-azdatatier.cloudapp.net:55919 prompt for credentials:i:1

The address part in this RDP file consists of:

• the FQDN of the cloud service that hosts the virtual machine (in this example, tailspin-azdatatier.cloudapp.net);
• endpoint external TCP port for remote desktop communication (55919).

An authentication error has occurred. Unable to contact the local security administrator."

Cause: The target VM cannot find the security administrator specified in the username part of your credentials.

If the username is in the format safety system\Username(for example, CORP\User1), then safety system in this entry, denotes the computer name of the virtual machine (for local security) or the Active Directory domain name.

Possible Solutions

• If the account is local to the VM, check the spelling of the VM name.
• If the account belongs to an Active Directory domain, check the spelling of the domain name.
• If it is an Active Directory domain account and the domain name is correct, verify that the domain controller is reachable for that domain. In Azure virtual networks with domain controllers, this feature can often be unavailable because it is not running. As a solution, use a local administrator account instead of a domain account.

Windows Security Error: Credentials do not work.

Cause: The target VM cannot verify the account name and password.

A Windows computer accepts local and domain account information.

• For local accounts, use the syntax computer_name\Username(for example, SQL1\Admin4798).
• For domain accounts, use the syntax domain name\Username(for example, CONTOSO\ivan_ivanon).

If you promote a virtual machine to a domain controller in a new Active Directory forest, the local administrator account that you are logged on with is converted to the equivalent account with the same password in the new forest and domain. The local account is then deleted.

For example, if you're signed in with the local account DC1\DCAdmin and you promote a virtual machine to a domain controller corp.contoso.com in a new forest, the local account DC1\DCAdmin is deleted and a new domain account CORP\DCAdmin is created instead same password.

Make sure the account name is a name that the VM can verify and accept as a valid account, and that the password is correct.

For information about how to change the password for the local administrator account, see Reset Remote Desktop Services or its logon password on a Windows virtual machine.

Unable to connect to remote computer.

Cause: The account you are using to connect does not have permissions to log in to Remote Desktop.

On each Windows computer There is a local group of users of a remote desktop. It contains accounts and groups that have the right to log on remotely. Members of the local Administrators group have similar access rights, although the corresponding accounts are not members of the local Remote Desktop Users group. On domain-joined computers, the local Administrators group also contains the administrator accounts for that domain.

Make sure the account you use to connect has permissions to log in to Remote Desktop. To resolve this issue, use a domain administrator or local administrator account to create a Remote Desktop connection. To add the required account to the local Remote Desktop Users group, use the Microsoft Management Console (MMC) snap-in ( Utilities > Local Users and Groups > Groups > Remote Desktop Users).

Further actions

If you don't see the above errors and an unknown issue occurs when you connect using RDP, see the Remote Desktop Connection Troubleshooting Guide.

• For information about troubleshooting access to applications running in a virtual machine, see Troubleshoot connection issues with applications on Linux virtual machines in Azure .
• If you're connecting to an Azure Linux VM using SSH and you're having issues, see this article

All versions of Windows since 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 through 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:

1. The terminal server is not configured with a license server for Remote Desktop Services.
2. The license server has not allocated client access licenses (CALs).

Let's consider both cases in more detail.

Setting up the license server

The error often occurs after some time in already configured connections, after 120 or 180 days. It is likely that when creating the connection, the client was issued a temporary license for this period of time. To obtain a new temporary license, you must delete the expired license information from the registry on the client machine. For this:

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 is released, or purchase and activate the required number of CAL - licenses.

To check available and used CALs, use "Terminal Server Licensing" on server Windows:

1. Open Start → Administrative Tools → Remote Desktop Services → Remote Desktop Licensing Manager.
2. Select your license server.
3. In the window that opens, click "Action" → "Create Report".

The report will display the number of Remote Desktop Services Per User CALs that:

• installed on the license server;
• issued by the licensing server based on the specified scope of the report.