Fix: Remote Session was Disconnected

because there are no Remote Desktop License Servers available to provide a license

Windows 10, like the older versions, provides users with Remote Desktop Protocol (RDP) feature through which users can connect from one system to other Windows devices. However, there have been several reports where users aren’t able to form a connection. Whenever they try to establish a connection, they are prompted with the ‘Remote session was disconnected because there are no Remote Desktop License Servers available to provide a license.’ error.

Remote Sessions was Disconnected

This error can be easily resolved by modifying one or two entries in the Windows registry. If you have been encountering the said error, this article will show you how to isolate it in no time. But before that, let us give the possible causes of the error a read.

What causes the ‘Remote Session was Disconnected’ Error on Windows 10?

Well, from what we have salvaged, this error is most of the time due to the following factor —

• TS not able to locate the license server. The major cause of the error would be the Terminal Server (TS). When this server is not able to locate the license server in the system, you will receive the said error message.

To circumvent the issue, you can follow the solutions given below. Please make sure to follow the instructions carefully as Windows Registry can cause critical issues to rise.

Solution 1: Deleting the MSLicensing Key

The reason due to which the Terminal Server (TS) is not able to locate the license server can potentially be due to this specific key. Therefore, you will have to delete the key and then try using RDP. Here’s how to do it:

1. Press Windows Key + R to open Run.
2. Type in ‘gpedit’ and then press Enter.
3. Once the Windows Registry opens, navigate to the following path:
4. Afterward, locate the MSLicensing key.
5. Expand the key, right-click the ‘Store’ key and click Delete. Deleting Store Key in the Windows Registry
6. Once prompted, select Yes.
7. Check if the issue still persists.

Solution 2: Deleting the GracePeriod Key

You can also fix your issue by removing the GracePeriod key in the Windows Registry which, at times, can be the cause of the pop up. You can apply this solution if you are using Windows Server 2012 or later. Here’s how to do it:

1. Open up the Windows Registry as shown in solution 1.
2. In the Windows Registry, navigate to the following path:
3. In the RCM key, locate the GracePeriod key and right-click on it.
4. Select Delete to remove the key. In some cases, you might have to take permissions over the key in order to remove it. Deleting GracePeriod Key
5. To take permissions over the key, just right-click GracePeriod and select Permissions. Changing Permissions of the GracePeriod Key
6. Then select your User Account and check the ‘Full Control’ and ‘Read’ boxes.
7. Click Apply and then hit OK.

Solution 3: Run RDP as an Administrator

In some cases, the error can be merely due to insufficient permissions of the Remote Desktop Connection application. Therefore, to eliminate such a possibility, you’ll have to run the app as an administrator. If it fixes the issue, make sure to run the application always. Here’s how to do it:

1. Go to the Start Menu, type in ‘Remote Desktop Connection’. Right-click on it and select ‘Run as an administrator’.
2. Try connecting to see if it fixes the issue.

You can also use Run to run RDP as an administrator. Here’s how to do it:

1. Press Windows Key + R to open Run.
2. Type in the following command and press Enter:

Running RDP As An Admin Using Run

Solution 4: Restart Remote Desktop Services

Finally, if the above solutions do not work out for you, you can resolve the issue by restarting the ‘Remote Desktop Services’ service. Here’s how to do it:

1. Go to the Start Menu, type in Services and open it up.
2. From the list, locate the ‘Remote Desktop Services’ service.
3. Right-click on it and click ‘Restart’. Restarting Remote Desktop Services Service
4. Try connecting again.

The remote session was disconnected because there are no Remote Desktop client access licenses available for this computer. Please contact the server administrator.

Normally, this would be a remote server question, but everything checks out on the server. What I would like to try is uninstalling and reinstalling the Remote Desktop Connection and start out from groud zero. I am running Windows Vista. How do I do this?

I had the same problem but it was only when trying to RDP from ONE computer. I found the solution was to delete the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing

I found the solution from this post so I don’t claim credit for the solution.

Hope this helps others out as well.

69 people found this reply helpful

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Thank you for visiting Microsoft Answers.

• Which version of Windows Vista is installed on your computer?
• Were you able to establish remote desktop connection earlier?
• Is your computer connected to any domain or server?

Let’s try to reconfigure the remote desktop settings by following the steps given under ‘How do I install Remote Desktop Connection? ‘and ‘How do I enable Remote Desktop Connection on the computer I want to connect to? ‘in the links given below to:

Note: You cannot use Remote Desktop Connection to connect to computers running Windows Vista Starter, Windows Vista Home Basic, Windows Vista Home Basic N, or Windows Vista Home Premium. You can, however, connect from those editions of Windows Vista to computers running other versions of Windows.

Regards
Debleena S
Microsoft Answers Support Engineer
Visit our Microsoft Answers Feedback Forum and let us know what you think.

Remote Desktop client disconnects and can’t reconnect to the same session

After Remote Desktop client loses its connection to the remote desktop, the client can’t immediately reconnect. The user receives one of the following error messages:

• The client couldn’t connect to the terminal server because of a security error. Make sure you are signed in to the network, then try connecting again.
• Remote Desktop disconnected. Because of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again.

When the Remote Desktop client reconnects, the RDSH server reconnects the client to a new session instead of the original session. However, when you check the RDSH server, it says that the original session is still active and didn’t enter a disconnected state.

To work around this issue, you can enable the Configure keep-alive connection interval policy in the Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections group policy folder. If you enable this policy, you must enter a keep-alive interval. The keep-alive interval determines how often, in minutes, the server checks the session state.

This issue can also be fixed by reconfiguring your authentication and configuration settings. You can reconfigure these settings at either the server level or by using group policy objects (GPOs). Here’s how to reconfigure your settings: Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security group policy folder.

1. On the RD Session Host server, open Remote Desktop Session Host Configuration.
2. Under Connections, right-click the name of the connection, then select Properties.
3. In the Properties dialog box for the connection, on the General tab, in Security layer, select a security method.
4. Go to Encryption level and select the level you want. You can select Low, Client Compatible, High, or FIPS Compliant.

• When communications between clients and RD Session Host servers require the highest level of encryption, use FIPS-compliant encryption.
• Any encryption level settings you configure in Group Policy override the settings you configured using the Remote Desktop Services Configuration tool. Also, if you enable the System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing policy, this setting overrides the Set client connection encryption level policy. The system cryptography policy is in the Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options folder.
• When you change the encryption level, the new encryption level takes effect the next time a user signs in. If you require multiple levels of encryption on one server, install multiple network adapters and configure each adapter separately.
• To verify your certificate has a corresponding private key, go to Remote Desktop Services Configuration, right-click the connection that you want to view the certificate for, select General, then select Edit. After that, select View certificate. When you go to the General tab, you should see the statement, «You have a private key that corresponds to this certificate» if there’s a key. You can also view this information with the Certificates snap-in.
• FIPS-compliant encryption (the System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing policy or the FIPS Compliant setting in Remote Desktop Server Configuration) encrypts and decrypts data sent between the server and client with the Federal Information Processing Standard (FIPS) 140-1 encryption algorithms that use Microsoft cryptographic modules. For more information, see FIPS 140 Validation.
• The High setting encrypts data sent between the server and client by using strong 128-bit encryption.
• The Client Compatible setting encrypts data sent between the client and the server at the maximum key strength supported by the client.
• The Low setting encrypts data sent from the client to the server using 56-bit encryption.

Ошибка: The remote computer disconnected the session because of an error in the licensing protocol

Сегодня на нескольких компьютерах пользователей встретились со следующей ошибкой, появляющейся при попытке удаленного rdp подключения к серверу терминалов Windows 2008 Server.

Ошибка выглядит так: The remote computer disconnected the session because of an error in the licensing protocol. Please try connecting to the remote computer again or contact your server administrator.

В русскоязычной версии Windows ошибка звучит так:

Удаленный компьютер отключил сеанс из-за ошибки в протоколе лицензирования. Попытайтесь подключиться к удаленному компьютеру снова или обратитесь к администратору сервера

Кроме того, встречались еще и такие ошибки:

Удаленный сеанс отключен из-за отсутствия доступных лицензий клиента сервера терминалов для этого компьютера

The remote session was disconnected because there are no Remote Desktop client access licenses available for this computer

Данная ошибка появлялась как на компьютерах с Windows 7, так и с Windows XP, хотя часть клиентов работала нормально.

Чтобы победить эту ошибку, воспользуйтесь следующей инструкцией

1. Откройте редактор реестра regedit
2. Найдите ветку реестра HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing
3. На всякий случай создайте резервную копию этой ветки, экспортировав ее в reg файл
4. Удалите все содержимое в ветке MSLicensing, включая все подпапки и ключи в них.
5. Перезагрузите компьютер
6. После перезагрузки откройте меню ‘Start‘–> ‘Programs / All programs‘ –>Accessories
7. Щелкните правой кнопкой мыши по значку Remote Desktop Connection (mstsc.exe) и выберите “Run as Administrator“, после чего в ветке MSLicensing должны пересоздаются ключи Hardware ID и Store

После выполнения указанной процедуры у вас получится установить соединение с сервером терминалов Remote Desktop Services, а клиенту будет выдана новая терминальная лицензия.

В том случае, если вы не запустите rdp клиент с правами обычного пользователя, тогда в указанной ветке реестра не будут созданы необходимые ключи, ведь у обычных пользователей нет прав на запись в этот раздел реестра.

Почему же могла появиться ошибка «The remote computer disconnected the session»?

С уверенностью на этот вопрос я ответить не смогу, но подозреваю что в несоответствии настроек лицензирования на сервере терминальных лицензий и сервере терминалов, например, когда на первом имеются лицензии только «На устройство» (Per device), а второй настроен на лицензирование «На пользователя» (Per User). В качестве второй версии, вероятно проблемы несоответствия или истечения сроков временных терминальных лицензий.