From time to time it becomes necessary to regenerate temporary terminal server licenses. Whether it be a genuine error which is preventing you from using temporary licenses or the fact that someone 'forgot' to purchase TSCALS within the grace period allowed by Microsoft.
Microsoft Terminal Server License
For the Terminal Server Licensing Server Has No Permanent Licenses For Product events, use the Terminal Server Licensing administrative tool to register more licenses. For A License Could Not Be Issued To Because It Is Not A Member Of The Terminal Server Computers Group events, check the status of the License Server Security Group. Set the Remote Desktop licensing mode. This policy setting allows you to specify the type of Remote Desktop Services client access license (RDS CAL) that is required to connect to this RD Session Host server. You can use this policy setting to select one of two licensing modes: Per User or Per Device. Windows 2000 Server Terminal Services usually uses a license server in the local domain; however, you might want to have a central license server for audit purposes or use a server in another domain. A Terminal Services license server is used to install, distribute and manage these TSCALs. Without a license server, the terminal server will stop accepting connections after 90 days. If you're in a Win2K domain environment, you should install the Terminal Services Licensing service on one of your domain controllers. All terminal servers in the.
In my experience the below will fix 99.9% of problems surrounding temporary licenses and let you get back up and running with enough time to source some legitimate TSCALS.
*Note: These only apply to temporary licenses. If you are running a system with permanent TSCALS make sure you fully back your licenses up before doing this. If you don't you will have to call the Microsoft Clearing House to get your TSCALS back.
On the client:
Start up regedit.exe. Drill down to HKEY_LMSoftwareMicrosoftMSLicensing and delete this whole key.
On the server itself:
Go to Control Panel, Administritive tools, Services manager.
STOP Terminal Server Licensing Manager Service.
Delete contents of %systemroot%system32Lserver directory.
RESTART Terminal Server Licensing Manager Service.
As an absolute final resort (on the server):
Caution:Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.
To set a preferred license server by using the registry (on Windows Server 2003)
- On the license server, open Registry Editor. To open Registry Editor, click Start, click Run, type regedit, and then click OK.
- Locate, and then click, the following key in the registry:
HKEY_LOCAL_MACHINESYSTEM
CurrentControlSetServices
TermServiceParameters - On the Edit menu, point to New, click Key, and then type LicenseServers to name the new key.
- Locate, and then click, the following key in the registry:
HKEY_LMSYSTEMCurrentControlSet
ServicesTermServiceParameters
LicenseServers
On the Edit menu, point to New, click Key, and then type ServerNamewhere ServerName is one of the following:
- The FQDN of the server (for example, Server1.contoso.com)
- The NetBIOS name of the server(for example, Server1)
- The IP address of the server (for example, 206.73.118.1)
Are you tired of getting the error remote desktop licensing mode is not configured and the Remote Desktop Services will stop working in xx days? Learn how to fix it.
Do you want to get rid of the Remote Desktop licensing mode is not configured or Licensing mode for the Remote Desktop Session Host is not configured error as quickly as possible?
Well, if you are a system administrator who works with Remote Desktop Services (RDS) and uses Windows Server 2016 or Windows Server 2012 R2 very frequently then at some point you may have encountered the Remote Desktop licensing mode is not configured error.
Usually, this error appears as a notification popup in the bottom right-hand corner of the screen saying:
Remote Desktop licensing mode is not configured
Remote Desktop Services will stop working in xx days. On the RD Connection Broker server, use Server Manager to specify the Remote Desktop licensing mode and the license server.
And when you click on this notification popup, it doesn’t redirect you anywhere and it gets simply disappeared which is a quite frustrating situation.
On the Remote Desktop Licensing Manager, if there are valid licenses installed and everything seems accurate, and still, a popup appears that says Remote Desktop services will stop working on specific days then this circumstance is bound to scare almost anyone.
So, if you want to know how to fix remote desktop licensing mode is not configured error on Windows server then follow our handy guide which we brought to you today. So, without further ado, let’s begin.
How to Fix Remote Desktop Licensing Mode is Not Configured
Although, various expert users suggest different solutions to get rid of the remote desktop licensing mode is not configured on the RD connection broker server error and there are multiple methods available on the web for dealing with this issue as well. But here we are going to share only those active methods that are extremely easy to execute and work ideally in almost all situations.
So, let’s check out how to fix Remote Desktop licensing mode is not configured error on Windows Server:
Method 1: Using Windows Registry Editor
There are several ways to set the RDS licensing mode, but doing it via the Windows Registry Editor is the most convenient way. Here’s how to change the licensing mode for Remote Desktop session host using the registry editor and get rid of the error message Remote Desktop Services will stop working in xx days:
Step (1): At first, press Windows + R keys together and then type regedit in the Run dialog box and press Enter key.
Step (2): In the left pane of the Registry Editor, navigate to the following registry key:
HKLMSYSTEMCurrentControlSetControlTerminal ServerRCMLicensing Core
Step (3): Now in the right pane, double-click on the LicensingMode to edit its value and then change the Value data according to your requirement:
- Set the Value data 2 for Per Device RDS licensing mode
- Set the Value data 4 for Per User RDS licensing mode
Terminal Server License Cost
Step (4): Finally, click on the OK button to save the changes.
Now, restart your computer and check if the Remote Desktop licensing mode is not configured issue on Windows Server has been resolved or not.
Once you changed the licensing mode, now everything will be reported accurately and the Remote Desktop session host will recognize the licensing configuration.
Method 2: Using Local Group Policy Editor
If you are the administrator who has high-level access to the system then you can also use the Local Group Policy Editorto change the licensing mode for remote desktop session host.
Change Terminal Server License Server
Here’s how to change RDS licensing mode using Group Policy and solve the remote desktop licensing mode is not configured on Windows server error:
Step (1): First of all, press Windows + R keys together and then type gpedit.msc and press Enter key.
Step (2): On the Local Group Policy Editor, navigate to the Computer Configuration > Policies > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Licensing.
Step (3): Now double-click on the “Use the specified Remote Desktop license servers” setting and then select Enabled option. Finally, enter the names of the license servers (host name or IP address) and then click on the OK button.
Step (4): Similarly, double-click on the “Set the Remote Desktop licensing mode” setting and then select Enabled option. Finally, set the licensing mode (Per Device or Per User) and then click on the OK button.
Once all these changes are done, close the Local Group Policy Editor and then restart your computer.
Now open the Remote Desktop Licensing Diagnoser and you shouldn’t see any errors like the remote desktop licensing mode is not configured on windows server or any kind of issues regarding your licenses.
Conclusions
So these are the two easiest methods you can use to solve the Licensing mode for the remote desktop session host is not configured issue on Windows server. Now no need to get scared after seeing the notification popup saying the Remote Desktop Services will stop working on the RD connection broker server.
If you need any more help related to the Windows Server 2016 or Windows Server 2012 Remote Desktop licensing mode is not configured error or have any other queries regarding remote desktop services then feel free to let us know in the comments below.
You may also be interested in checking out: