Windows Windows Server

What to do when your Remote Desktop Licensing Manager Server Crashed

image-63

There is no cause for alarm whenever your designated Remote Desktop Licensing Manager Server crashed, and people are finding it hard to connect remotely to servers due to the crash because the server to assign RDS license has crashed. In this guide I will be showing you how to quickly configure another server as the RD Licensing Manager and connect all other servers to it for their licensing management. 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”, 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], 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, How to Resolve Microsoft RDP Connection Black Screen

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.

image-47
RD Diagnoser

Now move to the server you want to configure as the new RD Licensing Manager, right-click on the server and select RD Licensing Manager.

image-48
RD Licensing Manager

After the RD Licensing Manager page opens right-click on the server name and choose Manage Licenses from the drop-down.   

image-49
Managing Licenses

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.

image-50
Action selection

You will need to check the I agree to discontinue using the source license server as a license server, and
– Click Next.

image-51
Manage License Wizard

Then enter the previous CAL license and click Next.

image-52
Manage License Wizard

If you enter a valid license, you will get a successful outcome.

image-54
RD License Manager Overview

But at this stage the new server has not to be recognized as the license manager as you can see on the RD Licensing Diagnoser page in the below image: There lies the message that the server cannot issue licenses to the Remote Desktop Session Host server because the “License server security group” Group Policy setting is enabled.

image-57
RD Licensing Diagnoser Displaying Error

Now go into the Local Group Policy, under the RD Licensing, and disable the License server, security group.

image-58
Local Group Policy Editor

Click on Disabled and click Next.

image-59
License Server Security Group

You can now refresh the RD Licensing Diagnoser page and you will see that the error messages will no longer show.

image-60
RD Licensing Diagnoser Correct Display

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 and people can start connecting remotely.

image-61
Connecting to RD Session Host Server

I hope you found this blog post on What to do when your Remote Desktop Licensing Manager Server Crashed very interesting and helpful. In case you have any questions do not hesitate to ask in the comment section.

Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x