Activating Windows Server 2016 RDS 50 User CAL
Activating Windows Server 2016 RDS 50 User CAL allows you to legally provide remote desktop services to users within your company. In practice, this means that up to 50 specified users can connect to the server with the Remote Desktop Services role, regardless of the number of devices they use. This is a convenient solution in office environments where one person works on a desktop computer, laptop, and sometimes also from home.
In the User CAL model, the license is assigned to the user, not the device. If your organisation prioritises who uses the resources rather than the hardware used, this option is usually better than Device CAL. In Windows Server 2016, configuring the RDS license server and installing the CAL package is done using system administrative tools, but requires following the correct sequence of actions.
Below, you will find a simple instruction for activating the RDS 50 User CAL license for Windows Server 2016.
Step by Step
-
Log in to the server with administrator privileges.
-
Open Server Manager and go to:
Tools→Remote Desktop Services→Remote Desktop Licensing Manager. -
In the left panel, find your server name. If the license server has not been activated yet, you may see information about the lack of activation next to its name.
-
Right-click the server name and select:
Activate Server. -
The activation wizard will start. The most commonly chosen method is:
Automatically connect (recommended). This option requires internet access from the server level. If the server does not have a connection, you can use activation via a browser or phone, but in a typical deployment, the automatic option is the fastest. -
Fill in your company's data, such as organisation name, country, and optionally contact details. Then complete the wizard. After successfully completing the process, the license server will be activated.
-
After completing the activation, select the option to start installing the license package. If the wizard does not start automatically, right-click the server name and select:
Install Licenses. -
In the license installation wizard, select the appropriate licensing program compatible with the received key or license document. Depending on the source of purchase, this may be a different type of program. Then enter the required identification data.
-
In the next step, add the package: Windows Server 2016 Remote Desktop Services - 50 User CAL. Make sure you select the correct system version and license type:
Per User. -
After completing the license installation, go to the RDS session host configuration. Open:
Server Manager→Remote Desktop Services. Then specify the license server and set the licensing mode:Per User. -
If you are configuring this locally through group policy, you can use:
gpedit.msc→Computer Configuration→Administrative Templates→Windows Components→Remote Desktop Services→Remote Desktop Session Host→Licensing. There, set:Use the specified Remote Desktop license serversandSet the Remote Desktop licensing modetoPer User. -
After saving the settings, restart the service or restart the server if your environment requires it.
For any further assistance, please contact us at [email protected] or call 00 800 121 1654.
Verification
After activation, it is worth confirming that the server correctly sees the installed RDS 50 User CAL package.
The easiest way to do this is in the Remote Desktop Licensing Manager. After expanding the server name, the installed license package should be visible with information about the system version, license type, and the number of available permissions. For this configuration, a package corresponding to Windows Server 2016 RDS User CAL should appear.
Additionally, check the RDS licensing diagnostics to see if the session host reports errors related to the licensing mode or the lack of a specified license server. If the mode on the host is set to Per Device, and Per User is installed, the system will report an inconsistency despite the correctly added CAL package.
It's also a good idea to perform a login test with a regular user account and confirm that the RDP connection works without any license-related issues.
Problems
The most common problem is inconsistent licensing mode. If the purchased license is 50 User CAL, the session host must also operate in Per User mode. Simply adding the key to the license server is not enough.
Another common situation is lack of a specified RDS license server. The session host may work for some time in the grace period, but after it ends, users will start having problems connecting. Therefore, after installing the license, it is essential to assign the correct license server.
Choosing the wrong product version during package installation can also be a problem. For an environment based on Windows Server 2016, it is crucial to ensure version and CAL type compatibility. Incorrect selection may result in package rejection or errors in diagnostics.
If the server does not have internet access, automatic activation may fail. In such a case, use activation via a browser or phone. Before starting the process, it's also a good idea to ensure that the network firewall or security policies do not block the communication required by the licensing service.
If you have trouble with activation or selecting the correct license, please contact us: [email protected] or call 00 800 121 1654.
FAQ
Does 50 User CAL mean 50 simultaneous connections?
Not always. User CAL means licenses assigned to 50 users. Licensing applies to authorized persons, not just the number of simultaneous sessions. Technical limitations of the environment still depend on the server and RDS service configuration.
How does User CAL differ from Device CAL?
User CAL assigns a license to a specific user who can connect from multiple devices. Device CAL assigns a license to a device from which multiple users can use it. In offices with hybrid work, the User CAL variant is more often chosen.
Do I need to restart the server after installing the key?
Not always, but after changing licensing settings or specifying a license server, it's a good idea to restart the RDS services or restart the server to ensure that the configuration has been applied correctly.
