How to Install RDS CALs on Windows Server 2016
A step-by-step guide to installing the Remote Desktop Licensing role, activating the server, and installing licenses.
Installing Remote Desktop Services (RDS) Client Access Licenses (CALs) on Windows Server 2016 is a two-part process. You first install the Remote Desktop Licensing role and then activate the license server to install your CALs.
Prerequisites
Before you begin, ensure you have the following:
Step 1: Install the Remote Desktop Licensing Role
- Open Server Manager and click Manage > Add Roles and Features.
- Click Next on the "Before You Begin" screen.
- Select Role-based or feature-based installation and click Next.
- Choose the server from the server pool and click Next.
- On the "Select server roles" page, check Remote Desktop Services, then click Next.
- Click Next again to skip the "Features" screen.
- On the "Remote Desktop Services" page, click Next.
- Select both Remote Desktop Licensing and Remote Desktop Session Host. (Click Add Features if prompted).
- Click Next and then Install.
(The server may need to restart).
Step 2: Activate the License Server and Install CALs
Once the role is installed, you can activate the server and add your licenses.
- Open Server Manager and navigate to Tools > Remote Desktop Services > Remote Desktop Licensing Manager.
- In the RD Licensing Manager, right-click on the server name and select Activate Server.
- The Activate Server Wizard will open. Click Next.
- Select Automatic connection (recommended) and click Next.
- Fill in the required company information and click Next. (The server will contact Microsoft's clearinghouse).
- Once activation is successful, the wizard may prompt you to install licenses. If not, right-click the server and select Install Licenses.
- Click Next on the "Welcome to the Install Licenses Wizard" screen.
- Choose the License Program you purchased your CALs through (e.g., Retail Purchase, Select License, Other Agreement) and click Next.
- Enter your License Key or Agreement Number and click Next.
- Specify the Product Version, License Type (Per User or Per Device), and Quantity.
- Click Next. The server will contact Microsoft to install your CALs.
Your installed RDS CALs will now appear in the RD Licensing Manager.
⚠️ Important Next Step:
Installing the CALs is not enough. You must configure the server to use them.
Click here for a guide on How to configure “Licensing Mode” and “License Server to Use”
Related Posts
How to Fix the CredSSP “Encryption Oracle Remediation” RDP Error
Home – How to Fix the CredSSP “Encryption Oracle Remediation” RDP Error How to Fix the CredSSP “Encryption Oracle Remediation” RDP Error If you are managing Windows Servers, you have likely encountered this terrifying error message when trying to connect via Remote Desktop: “An authentication error has occurred. The function requested is not supported… This…
How to Configure the RDS “Startup Environment” in Server 2016, 2019, 2022 & 2025
Home – How to Configure the RDS “Startup Environment” in Server 2016, 2019, 2022 & 2025 How to Configure the RDS “Startup Environment” in Server 2016, 2019, 2022 & 2025 If you recently upgraded your infrastructure, you likely noticed a glaring omission: Microsoft removed the Environment, Sessions, and Remote Control tabs from the Active Directory…
How to configure “Licensing Mode” and “License Server to Use” on a Windows Server?
Home / How to configure “Licensing Mode” and “License Server to Use” on a Windows Server? Configuring RDS Licensing Mode and License Server A guide for Windows Server 2016, 2019, 2022, and 2025. Configuring the Remote Desktop Services (RDS) licensing mode and license server on a Windows Server is a critical step for allowing more…
Everything you need to know about Microsoft RDS CALs
Home / Everything you need to know about Microsoft RDS CALs Everything you need to know about Microsoft RDS CALs A complete guide to Remote Desktop Services Client Access Licenses. What are Microsoft RDS CALs? RDS CALs (Remote Desktop Services Client Access Licenses) are a type of license required for a user or device to…
