How To Install Cal License In Windows 2012 Server

In this blog mail we will look at how to install and activate a Remote Desktop License Server on Windows Server 2022 R2. We will also review the 2 different types of CALs, and how to install CALs on the RD License Server. Finally, we will look at how to designate specific License Servers to RD Session Host Servers, through PowerShell and Group Policy.

If you don't have Remote Desktop Services Client Access Licenses (RDS CALs), your users will not be able to connect to a remote desktop session host server, later the initial grace menses of 120-days expires. To install Remote Desktop Services CALs, you kickoff need to install Remote Desktop Licensing. This is a role service of the Remote Desktop Services role on Windows Server 2022 R2. You can utilize RD Licensing to install, issue, and runway the availability and usage of licenses.

Citrix XenApp too relies on a RD license server. Considering what XenApp essentially does, is to extend the capabilities of the Microsoft Remote Desktop session host server. Each fourth dimension a user connects to a XenApp session, he is also connecting to a Remote Desktop Session. So you will need licenses for both XenApp and RDS.

Continue in mind, the license server nosotros fix up in this blog postal service, volition just exist used to issue licenses to session host servers that will host shared desktops and deliver applications in a Citrix XenApp surroundings. Such a deployment volition only accept RD session host servers and license server(s). There will be no Remote Desktop Connectedness Broker.

Navigation

1. Installing the Role Service
ii. Activating the server
three. Types of CALs
4. Install CALs
five.Specify Licensing Style and License server for RD Session Host Servers

1. Installing the Role Service

Before you outset, yous should add the designated license server to the Final Server License Servers group in Active Directory. Otherwise, y'all will not be able to issue RDS Per User CALs to users in the domain, and you will non be able to track or report the usage of RDS Per User CALs on the License Server.

one.one Start the Add together Roles and Features Wizard in Server Managing director
one.two Click Next

one.3 Select Role-based or feature-based installation, click Next

1.4 Select the local server, click Side by side
1.5 Select Remote Desktop Services, click Next

one.6 Click Next
1.7 Click Next again

1.8 Select Remote Desktop Licensing (click Add Features when prompted), click Next

one.ix Click Install

1.x Click Close when the installation is finished

2. Activating the server

The license server must be activated to issue RD CALs.
2.one In Server Manager, Click Tools → Final Services → Remote Desktop Licensing Manager

two.2 Right click the server proper noun, and select Activate Server

2.3 Click Next

ii.4 Select desired connection method. I'thousand selecting Automatic connection, which connects to the Microsoft clearinghouse over the cyberspace, by using https. If your license server does non have access to the cyberspace, yous can likewise choose to activate it through the web browser (of another computer, which is connected to the net) or over telephone. Click Next

2.5 You will be requested to provide some information about yourself. These iv fields are required, so enter information for each field

2.6 These fields are optional. Click next when yous are gear up

2.7 The server volition be activated
2.eight You lot can start the Install Licenses Wizard if you lot like from this page, but I chose not to

2.10If you correct-click the server name, and select Review Configuration, you can review the configuration of the RD license server.

3. Types of CALs

Each user and device that connects to a Remote Desktop Session host needs a client access license (CAL). There are two types of Client Access Licenses bachelor in this type of setup.

Per Device CALs
These are permanent CALs assigned to any calculator or device that connects to an RD Session Host Server more than once. The kickoff time a computer or device connects to an RD Session Host, its past default issued a temporary license. The second time a calculator or device connects to an RD Session Host, the license server issues information technology a permanent RDS Per Device CAL, if the license server is activated and enough RDS Per Device CALs are available. In other words, Per Device CALs can not be overallocated, meaning if you lot take 15 CALs, only 15 devices will exist able to make a connection to session hosts.

Per User CALs
Per User CALs give users correct to access Remote Desktop Services from any number of devices. They are not assigned to users permanently like Device CALs are to devices. Rather they are valid just for a set period of time, and are assigned to the user account in Active Directory. Licensing for Per User CALs is not enforced, so they tin can be overallocated, meaning even if y'all only have 15 CALs, more than fifteen users will be able to make a connection to session hosts. So its up to you to ensure that you lot stay in compliance with the Microsoft RDS Licensing agreement.

4. Install CALs

four.1 Right-click server, and select Install Licenses

iv.two The connection method y'all used during activation is retained (to change it, apply the properties dialog box of the license server). Click Next

four.3 Select appropriate License Plan, and and so click next.

iv.4 The next few steps will depend on the license programme you lot selected in the previous pace. These are the steps for Enterprise Agreement
iv.v Enter Agreement number, click Next

4.half-dozen Select Product Version, license type and quantity of licenses to install onto the license server. And so click Next and follow the wizard to consummate the license installation process.

The license server can now issue RDS CALs to clients.

5. Specify Licensing Mode and License server for RD Session Host Servers

The Remote Desktop Session Host Configuration Tool has been removed in Windows Server 2022 R2. And then yous will accept to specify licensing mode and licensing server through other ways. Since nosotros are not dealing with a full-blown deployment of Remote Desktop Services here, simply rather just session host servers that nosotros will use for the purpose of hosting shared desktops and evangelize applications on Citrix XenApp, we tin not define the licensing server in Server Manager. Rather, nosotros will have to utilise either PowerShell or Grouping Policy.

5.one Through PowerShell

Run the following iii cmdlets in PowerShell on the session host server

$obj = gwmi -namespace "Root/CIMV2/TerminalServices" Win32_TerminalServiceSetting

$obj.ChangeMode(4)

$obj.SetSpecifiedLicenseServerList("server02.shabaztech.com")

In cmdlet number two, the value of 4 specified that the licensing mode volition be Per User. If you desire to use Per Device licensing way, then you volition have to enter 2 instead.

Finally, run this cmdlet to verify that the specified license server was fix correctly.

$obj.GetSpecifiedLicenseServerList()

5.2 Through Grouping Policy

The settings tin can be found in the following location, and they are self-explanatory.

Computer Configuration → Policies → Admin Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Licensing

(The configured GPO must be linked to your session host servers)

Another interesting setting can be found at the following location

Reckoner Configuration → Policies → Admin Templates →Windows Components → Remote Desktop Services → RD Licensing

With this setting you tin can control which RD Session Host servers are issued RDS CALs by the license server. It must be configured in a GPO that is applied to the license server.

five.3 Remote Desktop Licensing Diagnoser

You lot can utilise RD Licensing Diagnoser to bank check licensing configuration details for a session host server. You tin too use it to help identify possible licensing problems.

Upper portion gives information about licensing configuration details on the session host server.
Middle portion gives diagnostic data and suggested resolutions for any bug.
Lower portion gives data on which license servers the session host is configured with.