There is no cause for alarm whenever your designated Remote Desktop Licensing Manager Server crashes, and people are finding it hard to connect remotely to servers due to the crash because the server to assign the RDS license has crashed. In this article, we shall demonstrate what to do when your Remote Desktop Licensing Manager Server crashes. We will achieve this by quickly configuring another server as the RD Licensing Manager and connecting all other servers to it for their licensing management. Please see how to Resolve Microsoft RDP Connection Black Screen.
If you need more guides on remote connection issues read these. How to fix the issue “The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license”, and how to fix the issue “The Security Database on the Server does not have a Computer Account for this Workstation Trust Relationship” on Windows Server [Part 2].
RD Licensing Diagnoser found the issue “Remote Desktop Licensing Manager Server Crashes”
You will see the image below displaying the RD Licensing issue because the server that was configured for licensing cannot be detected on the network again.
Setting up the New RD Licensing Manager on Your Chosen Server
Now, go to the server you wish to set up as the new RD Licensing Manager, right-click on the server, and choose RD Licensing Manager.
After the RD Licensing Manager page opens right-click on the server name and choose Manage Licenses from the drop-down.
Here are some exciting guides: How to Activate and Press Ctrl+Alt+Del in Anydesk for Remote Access Connection to Windows system, How to fix Error 853: The remote access connection completed, but authentication failed because the certificate that authenticates the client to the server is not valid, ensure that the certificate used for authentication is valid.
Since we are not doing a replacement rather the previous server crashed you will need to select The source license server is no longer functioning and click Next.
You will need to check the I agree to discontinue using the source license server as a license server, and click Next.
Then enter the previous CAL license and click Next.
If you enter a valid license, you will get a successful outcome.
Please see Remote Desktop Services Setup on Windows Server, How to Install HTML Web Client for Microsoft RDS. Also, see Windows Licensing: How to find your Windows 10 Product key, and RDS client access licenses: How to install a new Per User Remote Desktop Services license.
License Server Security Group Policy Setting Impact on License Issuance
But at this stage, the image below displays the RD Licensing Diagnoser page with the message: The enabled “License server security group” Group Policy setting prevents the server from issuing licenses to the Remote Desktop Session Host server.
Now go into the Local Group Policy, under the RD Licensing, and disable the License server, security group.
Click on Disabled and click Next.
You can now refresh the RD Licensing Diagnoser page. Then you will see that the error messages will no longer show.
You can then start connecting each server to the RD Licensing Manager server one after the other.
But you need to read this guide: How to fix the issue “The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license” on how you can fully add your host server to the licensing server. Then people can start connecting remotely.
I hope you found this blog post on What to do when your Remote Desktop Licensing Manager Server Crashes very interesting and helpful. In case you have any questions do not hesitate to ask in the comment section.
