[Fix] Remote Desktop Licensing Mode Is Not Configured (100% Working)

wIt is a frequent administrative activity in enterprises to connect to remote desktops as well as configure them, I become much more important in the present attitude of “working from everywhere.” Accessing remote computers, on the other hand, is often not an easy operation, since it may necessitate the purchase of licenses and may result in numerous problems if the settings are incorrect. Because the error notice is frequently insufficiently specific to identify the root of the issue, resolving it can require a significant lot of time and resources, to not include the aggravation that comes with it. “Remote desktop licensing mode is not configured,” for example, is a key problem that does not have an auto error message. This article will provide comprehensive information about this mistake, its reasons, and even how to resolve it.

remote desktop licensing mode is not configured

What Is Remote Desktop Licensing?

In connecting to such a remote desktop connection host, each device, as well as the user, must have a Client Access License (CAL), which is used to assist you set up and monitoring licenses across several computers in your network. It also assists in simplifying access and ensuring that no illegal systems can establish connections with a distant host. 

Whenever a host and perhaps device attempts of connecting a remote desktop session (RDS) Hosting server, the host and system check the settings to determine whether a CAL is necessary. If the answer is positive, the RDS network device contacts the RD license servers to obtain a CAL. Following that, the server determines whether or not the CAL is legit and problems the CAL to such clients.

A connection to an RD Session server computer and, into it, towards the appropriate remote desktop is established with the help of this CAL. 

Multiple variations of the CAL are compatible with various session host types. 

After the 120-day probation period has expired, no license is necessary during that timeframe, according to Microsoft. Clients will require a Client Access License (CAL) in simply logging in to the remote desktop sessions hosted by the RD Session Host computer once this period has expired. 

Now that you’ve learned about the remote desktop license, let’s dive right into the problem.

What Is the Meaning of the Error Message “Remote Desktop Licensing Mode Is Not Configured”?

What is the meaning of the “remote desktop licensing mode is not configured” problem message. The reason for this mistake and the steps to correct it are both listed below. 

Let’s take a look and see what we can discover.

Troubleshooting ‘Remote Desktop Licensing Mode Is Not Configured’

Method 1: Make Use of the Registry

By using the registry, you could also set up the licensing. 

You can alter the LicensingMode input values from 5 to 2 if you’ve used the licensing mode of per-device, perhaps from 4 to 5 when you’re using currently the licensing mode of  per-user, by going to the following path:

HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\Licensing Core

And changing the LicensingMode attribute values from 5.

Method 2: Check the Grace Time Offered by Microsoft

Sometimes, a pop-up window in the settings menu will appear, informing you that now the remote desktop services will cease to function in an x day’s time. If you encounter this issue, the solution is obvious. 

As previously stated, Microsoft provides a 120-day time limit; therefore, this notice reminds you to purchase a license when you decide to continue using the software after the grace time has expired. This is merely a reminder, and it will not prevent you from utilizing remote desktop services in the future. 

Therefore, if you exceed the 120-day waiting period, you will be unable to use the service anymore. When this occurs, the alert will be converted into an issue, as well as you will be required to purchase a license in continuing visiting the site.

There are a variety of alternative reasons for the “remote desktop licensing mode is not configured” problem, albeit it’s the most typical reason and cause. 

However, recognizing them is difficult because the error that occurred may not be simple. After all, it’s at this point that testing methods such as the RD Licensing Diagnoser might be useful. 

To access this tool, navigate to Administrative Tools and there, you have to select the Remote Desktop Services and then RD Licensing Diagnoser in the Control Panel. The messages displayed by this application can provide a more accurate understanding of the main reason for the “remote desktop licensing mode is not configured” problem.

When you launch this program, you will see a warning notice stating that licenses for the Remote Desktop Session host server are not currently available. 

You must therefore establish the Session Host server’s licensing model, which is a time-consuming procedure. Keep in mind that you can receive this warning even if you’ve never set up the host server within the time limit if you don’t. 

For a double check whether or not licensing has been configured, run the following PowerShell command prompt:

$object = gwmi -namespace “Root/CIMV2/TerminalServices” Win32_TerminalServiceSetting


The command Get-RDLicenseConfiguration may provide you with the information you require. However, it might not be the case. As a result, the GetSpecifiedLicenSeserverList() function described above should be used. 

There are indeed a variety of options for configuring the license mode, and thus the following are some examples. 

Make use of the PowerShell command 

In order to make it work, run the following command to setup the license:


Method 3: Make Use of either a Local or Even a Domain Policy

Verify to see whether your RDS servers are indeed a member of a working group that isn’t connected here to domains that host its Active Directory. For configuring your RDS license on such a local system, use this local Group Policy Editor. 

Step 1: To access windows Group Policy Editor, navigate to Start and open Run by typing Windows + R key from your keyboard and enter this command: gpedit. msc. 

Step 2: Access the following locations: Computer Configuration and then, Administrative Templates from there, go to the Windows Components. Here, select the Remote Desktop Services and choose the Remote Desktop Se Session Host. And finally, click on the Licensing 

Step 3: Locate and then, you have to right-click on “Use the specified Remote Desktop license servers” in the policies list by navigating through it. Choose Properties from the drop-down menu.

Step 4: Determine whether the “Use the specified Remote Desktop license servers” policy is active. If this is not, activate the policy and then provide the address of the RDS license server in the policy description. 

Step 5: When you have over than 1, you should divide them with commas. 

Following that, select the licensing mode. Make your go to the section labeled “Set the Remote Desktop Licensing Mode,” you have to right-click, and then choose Properties. 

Step 6: Check to see if the checkbox labeled “Enabled” is selected. Alternatively, select this option. 

Step 7: Go to the “specify the licensing mode for the RD session host server” section and select either “per user” or “per device,” depending on your license model. Click “OK.” 

Step 8: Save your changes and then depart. Restart your computer if necessary. 

Step 9: Lastly, reboot the server to see whether you can connect here to the remote device this time.

Method 4: Ensure That You Are Using the Correct Type of Rds Cal

The use of the incorrect form of CAL in the RDS system can result in the “remote desktop licensing mode is not configured” issue being thrown at times. 

If you have a domain-joined web server, you can easily use either per-user or per CALs for most situations. When you only employ network servers, you can only use their per CALs that are provided. 

Keeping this in consideration, double-check that you’re going to connect that use the correct CAL for such a job.

Method 5: Make That the Firewall Is Working Properly

You may be unable to access your remote server if your firewall blocks your requests. Disable your firewall for just a few moments and then try connecting again to see whether the firewall is indeed the problem. 

The firewall could be temporarily disabled for testing purposes, but this is not a long-term solution. 

Access the ports listed below to allow connections from either the RDSH host or the RDS license server to provide a lasting solution. 

UDP 137 or 138 are the numbers to look out for. This is the RPC region, as well as TCP ports 135, 137, and 139

Method 6: Verify if the Two Are Compatible

This license also isn’t backward-compatible, therefore make sure that your license remains suitable to the Windows Operating system before continuing. Typically, it is indeed a fundamental but underappreciated issue. 

Whenever the CAL is about a major boost than current servers, you should consider changing your computer or purchasing a CAL which is appropriate with the type you currently have.


If you are facing this error, you can try the methods above to fix the issue.

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *