Remote Desktop Services (RDS) previously referred to as Terminal Server is a feature that you can use to connect to servers remotely. Each user and device that connects to a Remote Desktop Session host need a client access license (CAL). You use RD Licensing to install, issue, and track RDS CALs. When a user or a device connects to an RD Session Host server, the RD Session Host server determines if an RDS CAL is needed. The RD Session Host server then requests an RDS CAL from the Remote Desktop license server.
Furthermore, If an appropriate RDS CAL is available from a license server, the RDS CAL is issued to the client, and the client can connect to the RD Session Host server and from there to the desktop or apps they are trying to utilize. Please see how to set up and configure Remote Desktop Services via Standard Deployment on Windows Server, and How to install HTML 5 Web Client for Microsoft RDS Server.
Please note that you have a licensing grace period of 120 days, during which no license server is necessary. Once the grace period ends, clients must have a valid RDS CAL issued by a license server before they can log on to an RD Session Host server. Here are some guides relating to RDS: How to install RDS via Quick Start Deployment: Install, Publish, Update and Uninstall Remote Desktop Web Client, How to change a password on a Remote Desktop session, and Publish Remote Desktop Web Client: How to install HTML 5 Web Client for Microsoft RDS Server.
Each user and device that connects to a Remote Desktop Session host need a client access license (CAL). You use RD Licensing will help issue, and track RDS CALs. Microsoft offers a device-based CAL (Device CAL) or a user-based CAL (User CAL) for purchase. Ensure you are using per-user client access licenses (CALs) rather than per-device CALs before installing the Web Client. Otherwise, because the HTML client is incompatible with this form of licensing, it would seize all per-device CALs.
Add a new RDS client access licenses
To do this, launched the RD Licensing Manager. Right-click the license server, and then click Install licenses as shown below. Here is a guide on how to Remove and Manage Terminal Server licenses from an RDP client with PowerShell.
This will open the Install License Wizards (i.e, the welcome page). Kindly click on next to proceed.
This will open the Activation Server Wizard. I will keep the default connection method, as it’s recommended and used for contacting Microsoft clearing house during licensing installation. Click on next to continue.
Prompted by the Install License Wizard, choose License and click Next, as shown below.
Install a new Per User Remote Desktop Services license
Now select the product version, license type, and a number of licenses for your environment that will allow you to install a new Per User Remote Desktop Services license, and then click Next. The license manager contacts Microsoft Clearinghouse to validate and retrieve your licenses.
Note: If you had 10 before, and you are adding 40 new client access licenses, this will be a total of 50 licenses. Please verify that you are not needing a total of 50 but 40. This means you will have to add 30 new RDS to make 40.
When you are done entering the parameters, click next! To install a new Per User Remote Desktop Services license, ensure you follow the steps for seamless integration.
Enter your agreement number, and click next.
After completing the necessary steps on the last page, click Finish to finalize the process and smoothly integrate the keyphrase “install a new Per User Remote Desktop Services license. You can see that we have successfully installed the requested licenses.
Adding a Per User RDS License and Refreshing the License Server
Now, let’s proceed to the RD Licensing Manager once more to install a new Per User Remote Desktop Services license and perform a refresh of the license server.
You should be able to see the license installed. Here are some interesting guides as well: How to Remove and Manage Terminal Server licenses from an RDP client with PowerShell, how to publish Remote Desktop Web Client: How to install HTML 5 Web Client for Microsoft RDS Server, and how to remove a Remote Desktop Service collection on Windows Server.
Note: If you try to use RDS Per User CAL in a workgroup, the RDSH server will forcibly end a user session every 60 minutes with a message: “Remote Desktop License Issue: There is a problem with your Remote Desktop license, and your session will be disconnected in 60 minutes”. Therefore, for RDS servers in a Windows Workgroup environment, you need to use the only device licensing (Per Device RDS CALs).
I hope you found this blog post about how to install a new Per User Remote Desktop Services license helpful. If you have any questions, please let me know in the comment session.
