FIX: License Server is not available after renaming the RDS License Server 2016. (Solved)
This tutorial contains instructions to resolve the following error in Remote Desktop Service License Diagnoser: "License Server is not available. This could be caused by network connectivity problems, the Remote Desktop Licensing service is stopped on the license server, or RD Licensing is no longer installed on the computer" after renaming a Server 2016, with Remote Desktop Licenses installed.
How to fix: License Server is not available after renaming the RDS License Server 2016.
Method 1. For a Standalone RD Licensing Server.
Method 2. For a Non Standalone RD Licensing Server.
Method 1. FIX License Server is not available on a Standalone RD Licensing Server.
If your RD Licensing server is standalone (it is not part of RDS Deployment), then change the licensing server name, in Group Policy:
1. Open Group Policy Editor. To do that:
1. Simultaneously press the Windows
+ R keys to open run command box.
2. Type gpedit.msc and press Enter.
2. In Group Policy Editor navigate to:
- Computer Configuration\Administrative Templates\Windows Components\ Remote Desktop Services\Remote Desktop Session Host\Licensing
3. At the right pane double click at Use the specified Remote License Servers.
4. At 'License server to use' field, type the new server name and click OK.
5. Re-run the RD Licensing Diagnoser. The problem should be gone. *
* Note: In some cases, a restart of the RD Licensing server is required.
Method 2. FIX License Server is not available on a Non Standalone RD Licensing Server.
If your Remote Desktop Licensing server is not standalone (it is part of RDS Deployment collection), then you have to change the licensing server name, in Server Manager:
1. Open Server Manager.
2. Go to Remote Desktop Services –> Overview –> Tasks –> Edit Deployment Properties.
3. Click the the RD Licensing tab.
4. Type the new server name and click OK.
That’s it! Let me know if this guide has helped you by leaving your comment about your experience. Please like and share this guide to help others.
We're hiring
We're looking for part-time or full-time technical writers to join our team! It's about a remote position that qualified tech writers from anywhere in the world can apply. Click here for more details.
Dae
November 11, 2022 @ 8:49 pm
Jason Blalock, you're the boss! Thanks so much!
Jason Blalock
August 9, 2022 @ 9:13 am
Search for is 'oldservername', the markup on the page removed it when I put it in brackets.
Jason Blalock
August 9, 2022 @ 9:11 am
There's a much easier way to do this. Assuming you've already renamed the server, Go to regedit.
Search for "" – there are TWO places in the registry where this is defined, and they are identical. Change the server name value to the new server.
Reboot, good to go.
If you want the key names/paths, here they are.
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\TermService\Parameters\LicenseServers]
"SpecifiedLicenseServers"
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\TermService\Parameters\LicenseServers]
"SpecifiedLicenseServers"