Activating Windows Server 2019 RDS 50 User CAL
The RDS 50 User CAL licences for Windows Server 2019 are used for legally providing remote desktop services to users within a company. This licensing model means that the permission is assigned to the user, not to a specific device. This allows one person to use RDS services from multiple computers, laptops, or terminals, as long as they are covered by the licence.
Below, you will find a practical guide to activating the licensing role and installing the 50 User CAL package in a Windows Server 2019 environment. The instructions have been prepared with administrators in mind, who want to quickly launch the RDS server and correctly add the purchased licences.
Step by Step
1. Install the Remote Desktop Services Licensing Role
On a server with Windows Server 2019, open Server Manager and go to the Add Roles and Features option. In the wizard, select role-based or feature-based installation, specify the appropriate server, and then select the Remote Desktop Services role.
In the next step, select the Remote Desktop Licensing role service. The system may ask you to install additional components. Confirm the installation and complete the wizard. After completion, it is best to restart the server if the system suggests it.
2. Open the Remote Desktop Licensing Manager
After installing the role, go to the Remote Desktop Licensing Manager tool. You can find it quickly from the Tools level in Server Manager.
The local license server should be visible on the list. If an information symbol indicating a lack of activation appears next to the server name, you must first activate the licensing server and then install the CAL package.
3. Activate the Licensing Server
Right-click the server name and select Activate Server. The activation wizard will start. The most commonly chosen method is Automatic Connection, as it is the fastest and most convenient, provided the server has internet access.
In the form, enter the company's basic data, such as the organization name, country, and administrator contact details. After confirmation, the wizard will connect to the Microsoft clearing center and activate the license server. At the end, you can immediately proceed to install the CAL licenses.
If the server does not have internet access, you can use the web browser method or telephone activation. In this case, the wizard will show the server identifier and further instructions.
4. Install RDS 50 User CAL Licenses
After activation, right-click the license server and select Install Licenses. In the wizard, specify the appropriate licensing program compatible with the documents received during purchase. Then, provide the required data, such as the agreement number, authorization number, or license key, depending on the form of purchase.
It is essential to select the correct license type:
- Product: Windows Server 2019 - Remote Desktop Services
- CAL type: User CAL
- Quantity: 50
After confirmation, the system will download and save the license package on the server. If the operation is successful, you will see the added pool of 50 User CAL in the Licensing Manager.
5. Configure the Licensing Mode on the RDS Server
Installing CAL is not enough if the RDS session host does not know which license server to use. Open the Local Group Policy Editor or use domain policies and go to the Remote Desktop Services settings.
Configure two key settings:
- Set the Remote Desktop Services licensing mode to Per User
- Use the specified Remote Desktop license servers and enter the license server name
After saving the changes, run gpupdate /force or restart the server. This will allow the session host to use the correct configuration.
Verification
The simplest verification involves reopening the Remote Desktop Licensing Manager and checking if the server is activated and if it displays a pool of 50 User CAL for Windows Server 2019.
Additionally, it's worth running the Remote Desktop Licensing Diagnostics tool. If the configuration is correct, no errors related to licensing mode, lack of license server, or CAL type inconsistencies should appear.
In a domain environment, it's also a good idea to test logging in as a regular user via remote desktop and check if the session starts without any licensing issue messages.
Problems
The most common problem is the lack of a set licensing mode. If the session host operates in Per Device mode, and User CAL licenses are installed, the system will report errors. The license type on the server and in the policies must be consistent.
Another common cause of problems is incorrect license server specification or lack of network communication between the RDS host and the licensing server. In such cases, check the server name, DNS, firewall, and GPO policies.
It also happens that the administrator installs licenses on a different server than the one specified in the RDS configuration. As a result, the licenses are correctly added, but the service does not use them.
If the wizard does not accept licensing data, first verify the type of licensing program and purchase documents. Incorrectly selecting a variant in the wizard often causes the license number to be rejected, even if the key is correct.
If you have trouble with activation or selecting the correct installation path, you can contact us at [email protected].
FAQ
Does 50 User CAL mean 50 simultaneous connections?
No. 50 User CAL means permission for a maximum of 50 users. Each of these users can use remote desktop services according to the environment's rules, also from different devices.
Do User CAL licenses need to be manually assigned to each account?
In practice, the system and environment administration should reflect the number of authorized users. The key is for the company to have an appropriate number of licenses for the actual users. In the User CAL model, licensing compliance is important, not manual assignment like in a classic device inventory system.
Will RDS CAL for Windows Server 2019 work with a different server version?
It depends on the environment version and licensing compatibility rules. It's safest to use CALs compatible with the server version or confirm the scenario before deployment. When purchasing, make sure the license matches the exact environment used. If you want to check before installation, write to [email protected].
