How To Install Cal License In Windows 2012 Server

In this article, we'll consider the installation, configuration, and activation of the Remote Desktop Licensing part on Windows Server 2019 and 2016, besides equally the installation and activation of the RDS client access licenses (CALs).

I remind you that subsequently the installation of the Remote Desktop Session Host role, users tin use it only for 120 days of a trial catamenia (evaluation license), and users can't connect to an RDS host afterward. According to Microsoft licensing rules, all users or devices that use RDS features must be licensed. To register and event Remote Desktop Client Access Licenses (RDS CALs), there is a separate Windows service in the RDS role called Remote Desktop License Server.

Contents:

• Install the Remote Desktop Licensing Role on Windows Server 2019/2016
• Activating the RDS License Server on Windows Server
• RDS CALs: Types of Remote Desktop Customer Access Licenses
• Installing RDS CALs on Windows Server 2019/2016
• RDS CAL Usage Reports
• How to Remove RDS CALs from an RD License Server?
• Configuring RDS Licenses on RD Session Hosts

Install the Remote Desktop Licensing Role on Windows Server 2019/2016

You can deploy the Remote Desktop License service on whatever domain server. It is non necessary to install it on i of the servers on the RDSH farm.

Before you lot first the installation, add a new server to the Final Server License Servers domain security group (or make sure you have the permission to change this group membership), otherwise, the server won't be able to issue RDS Per User CAL to the domain users.

Yous can install Remote Desktop Licensing using Server Manager. To do it, select the Remote Desktop Services role in the Add Roles and Features Sorcerer.

Select Remote Desktop Licensing every bit the role service.

It remains to expect until the installation of the role is completed.

The RDS-Licensing service is managed using the Remote Desktop Licensing Manager console (licmgr.exe).

In Windows Server, information technology's easier to install roles and features using PowerShell. To install the RDS Licensing Service and RD Licensing Diagnoser, just run ane command:

Install-WindowsFeature RDS-Licensing –IncludeAllSubFeature -IncludeManagementTools

To list the RDS services installed on the host, use the command:

Become-WindowsFeature -Name RDS* | Where installed

Activating the RDS License Server on Windows Server

In order to issue licenses to RDP clients, your RDS License Server must be activated. To do it, open the Remote Desktop Licensing Manager (licmgr.exe), correct-click the name of your server, and select Activate Server.

The RDS licensing server activation wizard volition start. Hither y'all will need to select the activation method you adopt. If your server is continued to the Internet, information technology tin automatically connect to Microsoft servers and actuate the RDS license server. If there is no straight Internet access from the server, you can activate the server using a web browser or by phone.

Then you must make full in some information near your company (some of the fields are required).

It remains to click the Finish push.

If y'all right-click the server proper name in the console and select Review Configuration, y'all can verify that the RDS License Server is activated and can be used to actuate RDSH clients in your domain.

• This license server is a fellow member of the Last Server License Servers group in Active Directory. This license server will be able to effect RDS Per User CALs to users in the domain, and you will be able to runway the usage of RDS Per User CALs.

• This license server is registered as a service connectedness point (SCP) in Active Directory Domain Services.

RDS CALs: Types of Remote Desktop Client Access Licenses

Each user or device that connects to Remote Desktop Session hosts must have a client access license (CAL). There are two types of RDS CALs:

• Per-Device CAL – is the permanent license blazon assigned to a calculator (device) that connects to the RDS server more than than in one case (when a device is first continued, a temporary license is issued to it). These licenses are not concurrent, i.e., if you accept 10 Per Device licenses, but 10 hosts can connect to your RDS server. The current OVL RDS CAL is called: WinRmtDsktpSrvcsCAL 2019 SNGL OLV NL Each AP DvcCAL;
• Per-User CAL – is the type of license that allows a user to connect to the RDS server from any number of computers/devices. This type of license is associated with an Active Directory user and issued non permanently, but for a specific period of time. The license is issued for a period of 52 to 89 days (random number).  The current Open Value license of this type is called WinRmtDsktpSrvcsCAL 2019 SNGL OLV NL Each AP UsrCAL.

  If you try to use RDS 2019 Per User CAL in a workgroup (not in a domain), then the RDSH server will forcibly ending a user session every sixty minutes with a message: "Remote Desktop License Issue: There is a trouble with your Remote Desktop license, and your session will be disconnected in lx minutes". Therefore, for RDS servers in a Windows Workgroup surround, you need to use the only device licensing (Per Device RDS CALs).

.

Note. Nosotros should annotation that the 2016 RDS CAL may be installed but on a licensing server running Windows Server 2016 or 2019. Installing RDS CALs to the previous Windows Server versions is non supported. Those, you cannot install 2016 RDS CALs on a Windows Server 2012 R2 licensing host.

When trying to add new RDS CALs 2019 on Windows Server 2016, an mistake will appear:

RD Licensing Manager The license lawmaking is non recognized. Ensure that you have entered the correct license code.

Installing RDS CALs on Windows Server 2019/2016

Now you lot must install the pack of Remote Desktop client licenses (RDS CAL) yous take purchased on the License Server.

Right-click your server in Remote Desktop Licensing Director and select Install Licenses.

Select the activation method (automatic, online, or by phone) and the license program (in our case, it is Enterprise Agreement).

Many enterprise understanding numbers for RDS have already been leaked on the Internet. I call up information technology won't be a problem to find the numbers (4965437), you don't even demand to look for rds cracks or activators.

The next steps of the wizard depend on which license programme you have selected. In the instance of an Enterprise Understanding, y'all must specify its number. If you have chosen License Pack (Retail Purchase), enter the 25-character product key you got from Microsoft or a partner.

Specify the production version (Windows Server 2019/2016), license type (RDS Per user CAL), and the number of licenses to be installed on the server.

Afterward that, the server tin can consequence licenses (RDS CAL) to clients.

You tin catechumen RDS User CALs to Device CALs (and vice versa) using the Convert Licenses bill of fare item in the RD Licensing Manager panel.

If yous take run out of free RDS licenses, you lot tin revoke previously issued RDS Device CALs for inactive computers using the post-obit PowerShell script:

$RevokedPCName="lon-bc1-123"
$licensepacks = Become-WmiObject win32_tslicensekeypack | where {($_.keypacktype -ne 0) -and ($_.keypacktype -ne iv) -and ($_.keypacktype -ne 6)}
$licensepacks.TotalLicenses
$TSLicensesAssigned = gwmi win32_tsissuedlicense | where {$_.licensestatus -eq ii}
$RevokePC = $TSLicensesAssigned | ? sIssuedToComputer -EQ $RevokedPCName
$RevokePC.Revoke()

Up to xx% of Per-Device RDS CALs can exist revoked. Per-User CALs cannot exist revoked.

RDS CAL Usage Reports

In the RDS License Console, you lot can generate a license usage study. To do this, select Create Report -> CAL Usage from the server context menu.

However, I adopt to use PowerShell to written report RDS CAL usage. The post-obit script will show the remaining number of licenses in all RDS CAL packs:

Import-Module RemoteDesktopServices -ErrorAction Stop
Set-Location -Path 'rds:' -ErrorAction Terminate
$licenses = (Get-Item -Path RDS:\LicenseServer\LicenseKeyPacks\* | Where-Object Name -Like "-Per User-*").Name
$full=0;
$issued=0;
foreach ($license in $licenses) {
$count=(Get-Detail -Path RDS:\LicenseServer\LicenseKeyPacks\$license\TotalLicenses).CurrentValue
$total= $total + $count
$count2=(Get-Item -Path RDS:\LicenseServer\LicenseKeyPacks\$license\IssuedLicensesCount).CurrentValue
$issued= $issued + $count2
}
$available = $total - $issued
Write-Host "Total Licenses available: $available"

You can run this PowerShell script via Zabbix and set an alert if the remaining number of licenses is less, for instance, 5.

The following Powershell script volition let you lot to generate a Per User CAL Report:

Import-Module RemoteDesktopServices -ErrorAction Stop
Set-Location -Path 'rds:' -ErrorAction Terminate
$path = "C:\Reports\RDS_CAL_Usage.csv"
$fileName = (Invoke-WmiMethod Win32_TSLicenseReport -Proper noun GenerateReportEx).FileName
$fileEntries = (Become-WmiObject Win32_TSLicenseReport | Where-Object FileName -eq $fileName).FetchReportEntries(0,0).ReportEntries
$objArray = @()
foreach($entry in $fileEntries){
$objArray += $entry | select User, ProductVersion, CALType, ExpirationDate
$objArray[-1].User = $objArray[-1].User.Split('\') | select -Last 1
$time = $objArray[-1].ExpirationDate.Split('.') | select -beginning one
$objArray[-ane].ExpirationDate = [datetime]::ParseExact($time, "yyyyMMddHHmmss", $null)
}
$objArray | Consign-Csv -Path $path -Delimiter ',' -NoTypeInformation

How to Remove RDS CALs from an RD License Server?

If you want to motion your RDS CAL license packs from one Remote Desktop licensing server to another, you can remove the installed RDS CAL license pack from the licensing server using PowerShell.

Using the following cmdlet, you can listing all the installed RDS CAL packs on the server:

Get-WmiObject Win32_TSLicenseKeyPack|select-object KeyPackId,ProductVersion,TypeAndModel,AvailableLicenses,IssuedLicenses |ft

Find the KeyPackId value for the RDS CAL package that you want to remove and run the command:

wmic /namespace:\\root\CIMV2 PATH Win32_TSLicenseKeyPack Call UninstallLicenseKeyPackWithId yourKeyPackId

You can besides completely remove all CALs by re-creating the RDS license database. To practise this, finish the Remote Desktop Licensing service:

End-Service TermServLicensing

Rename the file C:\Windows\System32\lserver\TLSLic.edb to C:\Windows\System32\lserver\TLSLic.edb_bak and start the service:

Start-Service TermServLicensing

After that, all RDS CAL licenses will exist removed, and you must reactivate them.

Configuring RDS Licenses on RD Session Hosts

After the RDS License Server is activated and being run, you tin reconfigure RD Session Host to obtain CAL licenses from this server. You tin set the license type and specify the name of the license server from the Server Managing director GUI, using PowerShell, or Group Policy.

To change the name/address of the licensing server on the RDS host, open Server Manager -> Remote Desktop Services -> Collections. In the upper right menu "Tasks" select "Edit Deployment Properties".

In the deployment properties, go to the RD Licensing tab, select the Remote Desktop licensing mode, and set the RDS license server. Click Add -> Ok.

You can change the RDS license server address and CAL type using PowerShell:

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

And so specify the license type you need:

$obj.ChangeMode(iv)

Note. Enter 4 if the server must use Per User licensing type, and 2, if it is Per Device.

And then specify the proper noun of the RDS License Server:

$obj.SetSpecifiedLicenseServerList("rdslic2016.woshub.com")

And check the current settings:

$obj.GetSpecifiedLicenseServerList()

If you desire to assign the RDS licensing server parameters via Group Policy, you need to create a new GPO and link it to the OU with RDS servers (or you can specify the name of the RDS licensing server using the Local Group Policy Editor – gpedit.msc). The RD licensing settings are located under the following GPO section: Computer Configuration -> Policies -> Admin Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Licensing.

There are two Remote Desktop settings that we need to configure:

• Use the specified Remote Desktop license servers – the address of the License Server is ready;
• Set up the Remote Desktop licensing mode – select RDS CAL license blazon.

RDSH hosts use the following network ports to obtain an RDS license from the RDS Licensing server. Brand certain that they are not blocked by firewalls (or Windows Defender Firewall):

• TCP/135 – Microsoft RPC;
• UDP/137 – NetBIOS Datagram Service;
• UDP/138 – NetBIOS Name Resolution;
• TCP/139 – NetBIOS Session Service;
• TCP/445 – SMB;
• TCP/49152–65535 – RPC dynamic accost range

You can check for open ports using the PortQry tool or the Test-NetConnection cmdlet.

Effort to check the RD License Server condition and the number of the issued licenses using the Remote Desktop Licensing Diagnoser tool (lsdiag.msc or Administrative Tools -> Remote Desktop Services -> RD Licensing Diagnoser). RD Licensing Diagnoster can be installed on RDSH servers using Server Managing director (Features -> Remote Server Administration Tools -> Role Administration Tools -> Remote Desktop Services Tools -> Remote Desktop Licensing Diagnoser Tools).

If the RDSH server is not configured to use an RDS license server, the following warnings will appear in the Licensing Diagnoser console:

• Licenses are not available for this Remoter Desktop Session Host server, and RD Licensing Diagnose has identified licensing problems for the RDSH.

• Number of licenses bachelor for clients: 0

• The licensing mode for the Remote Desktop Session Host server is not configured.

• Remote Desktop Session Host server is within its grace menses, but the RD Session Host server has non been configured with whatsoever license server.

If you installed RDSH on the Windows Server Evaluation edition, do not forget to catechumen it to the full version according to the guide. Without conversion, RDSH services on such a host volition simply work for 120 days, even if you target it to an activated RDS license server.

If there are no warnings, and you see the bulletin "RD Licensing Diagnoser did non identify any licensing bug for the Remote Desktop Session Host server", then the RDSH server can successfully receive RDS CALs for remote users and/or devices.

Note. In our case, afterwards we specified the new License Server address the post-obit error started to announced on the RDP client: "The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license". The problem tin can exist solved by removing the Fifty$RTMTIMEBOMB key from the registry on the RDSH server.

Source: http://woshub.com/install-activate-rds-licensing-role-windows-server/

Posted by: gainesfreace.blogspot.com

Share this post