Remote desktop error licensing

Cause: The terminal server might not be able to locate the license server. Solution: Perform the following steps: 1. Verify that the license server is correctly installed. Verify that the Terminal Server Licensing service is running on the license server.

Verify that the client, the terminal server, and the license server can communicate by ensuring that Domain Name System DNS is configured correctly on each computer. If any of the ping commands fail, verify the DNS configuration on the network. On the terminal server, set a preferred licensing server to connect to. Solution: If the previous solution does not resolve this problem, create a backup of the MSLicensing registry key and its sub keys on the client, and then remove the original key and sub keys by doing the following: 1.

Accessing remote desktops and configuring them is a common administrative task in organizations, and it has taken greater importance in the current work-from-anywhere culture.

However, accessing remote desktops is not always a straightforward task as it could require licenses and can throw up many errors in case of misconfigurations. The error message is often not detailed enough to give you the cause of the problem, so fixing it can take up a ton of time and effort, not to mention the frustrations that come with it.

Every device or user that wants to connect to a remote desktop session host requires a Client Access License CAL , to help you install and track licenses across different computers. This CAL also helps with streamlining access and ensures that no unauthorized system can connect to a remote host. When a host or device tries to connect to a remote desktop session RDS Host server, it checks the configuration to see if a CAL is required.

Next, the server checks if the CAL is valid and issues the same to the client. Many CAL versions apply to different session host versions. So, check the version compatibility for your CAL. When you use the Per Device model, a temporary license is issued the first time a device connects to the RD Session Host.

When you use the Per User model, licensing is not enforced and each user is granted a license to connect to an RD Session Host from any number of devices.

It's your responsibility to ensure that all of your users have a valid license and zero Over-Used CALs—otherwise, you're in violation of the Remote Desktop Services license terms. An example of where one would use the Per Device model would be in an environment where there are two or more shifts using the same computers to access the RD Session Host s.

However, if you do have licenses here is some information help you make your choice:. The licenses you purchased can be used either as Per User or Per Device. It is purely up to you, however if you already have a RDS Licensing Server you will have to choose the same option you chose when importing the licenses originally.

Now you should specify who can connect to the Remote Desktop Server, I will just add my user account Windows Geek , then click next.

You are now given the option of making the RDS Server look and act more like Windows 7, this is to avoid users getting confused when they see the classic theme. I will enable the all the settings, it requires more bandwidth though, so take your network traffic into account before going click-happy and selecting everything. Once you have made your choice click next. Once installation is complete, reboot your server, when you log in the configuration will complete.