How To Install Cal License In Windows 2016 Server

In this commodity, we'll consider the installation, configuration, and activation of the Remote Desktop Licensing part on Windows Server 2019 and 2016, too as the installation and activation of the RDS customer access licenses (CALs).

I remind you that after the installation of the Remote Desktop Session Host function, users can use it merely for 120 days of a trial period (evaluation license), and users can't connect to an RDS host afterward. According to Microsoft licensing rules, all users or devices that apply RDS features must exist licensed. To register and effect Remote Desktop Customer Access Licenses (RDS CALs), there is a divide Windows service in the RDS role chosen 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 Client 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 tin deploy the Remote Desktop License service on any domain server. Information technology is not necessary to install it on 1 of the servers on the RDSH farm.

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

You lot can install Remote Desktop Licensing using Server Director. To practise it, select the Remote Desktop Services role in the Add Roles and Features Wizard.

Select Remote Desktop Licensing as the function service.

It remains to wait until the installation of the office is completed.

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

In Windows Server, it'southward easier to install roles and features using PowerShell. To install the RDS Licensing Service and RD Licensing Diagnoser, just run i command:

Install-WindowsFeature RDS-Licensing –IncludeAllSubFeature -IncludeManagementTools

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

Get-WindowsFeature -Name RDS* | Where installed

Activating the RDS License Server on Windows Server

In order to consequence licenses to RDP clients, your RDS License Server must exist activated. To practice it, open up 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 beginning. Here yous will need to select the activation method you prefer. If your server is connected to the Internet, it can automatically connect to Microsoft servers and activate the RDS license server. If at that place is no straight Internet access from the server, you can activate the server using a web browser or by phone.

So you must fill up in some data nigh your company (some of the fields are required).

Information technology remains to click the Cease push.

If you right-click the server name in the panel and select Review Configuration, you can verify that the RDS License Server is activated and can be used to activate RDSH clients in your domain.

• This license server is a member of the Terminal Server License Servers group in Agile Directory. This license server will exist able to issue RDS Per User CALs to users in the domain, and y'all will be able to runway the usage of RDS Per User CALs.

• This license server is registered as a service connexion 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 accept a customer access license (CAL). There are two types of RDS CALs:

• Per-Device CAL – is the permanent license blazon assigned to a computer (device) that connects to the RDS server more than once (when a device is first connected, a temporary license is issued to it). These licenses are not concurrent, i.e., if you have 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 blazon of license is associated with an Active Directory user and issued non permanently, but for a specific flow of time. The license is issued for a period of 52 to 89 days (random number).  The current Open Value license of this blazon is called WinRmtDsktpSrvcsCAL 2019 SNGL OLV NL Each AP UsrCAL.

  If yous endeavour to use RDS 2019 Per User CAL in a workgroup (non in a domain), then the RDSH server will forcibly ending a user session every 60 minutes with a bulletin: "Remote Desktop License Issue: There is a problem with your Remote Desktop license, and your session will be disconnected in 60 minutes". Therefore, for RDS servers in a Windows Workgroup environment, yous need to use the only device licensing (Per Device RDS CALs).

.

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

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

RD Licensing Manager The license code is not recognized. Ensure that yous have entered the correct license code.

Installing RDS CALs on Windows Server 2019/2016

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

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

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

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

The next steps of the wizard depend on which license programme you have selected. In the case of an Enterprise Agreement, yous must specify its number. If you lot have chosen License Pack (Retail Purchase), enter the 25-character production fundamental y'all 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.

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

You can catechumen RDS User CALs to Device CALs (and vice versa) using the Convert Licenses menu item in the RD Licensing Manager console.

If you have run out of free RDS licenses, yous can revoke previously issued RDS Device CALs for inactive computers using the following PowerShell script:

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

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

RDS CAL Usage Reports

In the RDS License Panel, yous can generate a license usage written report. To do this, select Create Report -> CAL Usage from the server context menu.

Nonetheless, I prefer to apply PowerShell to written report RDS CAL usage. The post-obit script volition testify the remaining number of licenses in all RDS CAL packs:

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

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

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

Import-Module RemoteDesktopServices -ErrorAction End
Set-Location -Path 'rds:' -ErrorAction Stop
$path = "C:\Reports\RDS_CAL_Usage.csv"
$fileName = (Invoke-WmiMethod Win32_TSLicenseReport -Name GenerateReportEx).FileName
$fileEntries = (Get-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[-i].User.Split('\') | select -Last 1
$time = $objArray[-1].ExpirationDate.Split('.') | select -first ane
$objArray[-1].ExpirationDate = [datetime]::ParseExact($fourth dimension, "yyyyMMddHHmmss", $zippo)
}
$objArray | Export-Csv -Path $path -Delimiter ',' -NoTypeInformation

How to Remove RDS CALs from an RD License Server?

If y'all want to move 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 list all the installed RDS CAL packs on the server:

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

Discover the KeyPackId value for the RDS CAL package that you lot desire to remove and run the command:

wmic /namespace:\\root\CIMV2 PATH Win32_TSLicenseKeyPack Phone call UninstallLicenseKeyPackWithId yourKeyPackId

Y'all tin likewise completely remove all CALs past re-creating the RDS license database. To do this, stop the Remote Desktop Licensing service:

Cease-Service TermServLicensing

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

Showtime-Service TermServLicensing

Later on that, all RDS CAL licenses will be removed, and you must reactivate them.

Configuring RDS Licenses on RD Session Hosts

After the RDS License Server is activated and beingness run, yous can reconfigure RD Session Host to obtain CAL licenses from this server. You tin gear up the license type and specify the name of the license server from the Server Manager GUI, using PowerShell, or Group Policy.

To change the proper noun/address of the licensing server on the RDS host, open up Server Manager -> Remote Desktop Services -> Collections. In the upper correct 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 tin change the RDS license server address and CAL type using PowerShell:

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

Then specify the license type you demand:

$obj.ChangeMode(4)

Annotation. Enter 4 if the server must use Per User licensing blazon, and 2, if information technology is Per Device.

And so 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, yous need to create a new GPO and link it to the OU with RDS servers (or yous can specify the name of the RDS licensing server using the Local Group Policy Editor – gpedit.msc). The RD licensing settings are located nether the following GPO department: Computer Configuration -> Policies -> Admin Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Licensing.

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

• Use the specified Remote Desktop license servers – the accost of the License Server is set;
• Set 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. Make certain that they are not blocked by firewalls (or Windows Defender Firewall):

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

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

Try to check the RD License Server status 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 tin can be installed on RDSH servers using Server Manager (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 utilize an RDS license server, the following warnings will appear in the Licensing Diagnoser panel:

• 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 available for clients: 0

• The licensing way for the Remote Desktop Session Host server is non configured.

• Remote Desktop Session Host server is within its grace catamenia, only the RD Session Host server has not been configured with whatever license server.

If you installed RDSH on the Windows Server Evaluation edition, practise not forget to convert it to the full version according to the guide. Without conversion, RDSH services on such a host will merely piece of work for 120 days, even if you target information technology to an activated RDS license server.

If there are no warnings, and yous see the message "RD Licensing Diagnoser did not place any licensing problems for the Remote Desktop Session Host server", and then the RDSH server tin successfully receive RDS CALs for remote users and/or devices.

Note. In our case, after we specified the new License Server accost the following fault started to appear on the RDP client: "The remote session was asunder because in that location are no Remote Desktop License Servers bachelor to provide a license". The trouble can be solved by removing the 50$RTMTIMEBOMB key from the registry on the RDSH server.

How To Install Cal License In Windows 2016 Server,

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

Posted by: cunninghamgiceit.blogspot.com

Share this post