Windows instance: no remote Desktop license server can provide license
Last updated: 2020-03-20 17:55:48PDF
This article introduces the handling method of the alarm prompt such as "the remote Session connection has been disconnected because there is no remote desktop authorization server to provide a license" when connecting to a Windows instance remotely.
When Windows uses remote Desktop to connect to the Windows instance, it prompts that "the remote Session connection has been disconnected because there is no remote Desktop license server to provide a license." Please contact the server administrator. "
Cause of failure
The main reasons for the above prompts are as follows (not limited to the following situations, please analyze them according to the actual situation):
- The system is configured with RDP-Tcp restrictions by default, and each user can only carry out one Session. If the account has been logged in, other Session will not be able to establish.
- The "remote Desktop Session Host" role function has been added to the system, but the authorization for this role has expired.
The "remote Desktop Session Host" role function is free to use for 120 days. After the function expires, you need to pay to use it.
Log in to Cloud Virtual Machine through VNC
- Login Cloud Virtual Machine console .
- On the instance management page, find the target Cloud Virtual Machine instance and click Log in.
- In the pop-up "Log in to Windows instance" window, select "other (VNC)", and click "Log in now" to log in to Cloud Virtual Machine.
- In the pop-up login window, select send remote Command in the upper left corner, and click Ctrl-Alt-Delete Enter the system login interface.
Option 1: modify policy configuration
- In the operating system interface, click To open the Windows PowerShell window
- In the Windows PowerShell window, enter Gpedit.msc , billed by Enter To open the local group policy editor
- In the left navigation tree, select computer configuration-> Administrative templates-> Windows components-> remote Desktop Services-> remote Desktop Session Host-> connections, and double-click to open limit the number of connections.
- In the pop-up "limit the number of connections" window, modify the [maximum number of RD connections allowed] according to the actual needs, and click "OK".
- Switch to the Windows PowerShell window.
- In the Windows PowerShell window, enter Gpupdate , billed by Enter To update the policy.
Option 2: delete the role of "remote Desktop Session Host"
If you do not want to delete the "remote Desktop Session Host" role, you can skip this step and go to Microsoft official website Purchase and configure the appropriate certificate authorization.
- In the operating system interface, click To open the server manager
- Click manage at the top right of Server Manager, and select Delete roles and Features.
- In the remove roles and Features Wizard window, click next.
- In the Delete Server role interface, uncheck remote Desktop Services, and in the pop-up prompt box, select Delete function.
- Click next twice.
- Check [automatically restart Launch's target server if necessary] and click [Yes] in the pop-up prompt.
- Click [Delete].
You can wait for Cloud Virtual Machine to return to Launch.