- Terminal Server License Server Group Name
- Terminal Server License Servers Group In Active Directory
- Event Id 4105
- Buy Terminal Server License
- Set Terminal Services License Server Group Policy
- Manually Add The Server To Terminal Server License Servers Group
In this article we’ll consider the installation, configuration and activation of Remote Desktop Licensing role on Windows Server 2019/2016, as well as the installation and activation of the RDS client access licenses (CALs).
I remind that after the installation of Remote Desktop Session Host role, users can use it only for 120 days of a trial period, and users can’t connect to an RDS host afterwards. According to Microsoft licensing scheme, all users or devices that used RDS features must be licensed. To register and issue remote desktop client access licenses (RDS CALs), there is a separate service in RDS role called Remote Desktop License Server.
Installing the Remote Desktop Licensing Role on Windows Server 2019/2016
You can deploy the Remote Desktop License service on any domain server; it is not necessary to install it on one of the servers in the RDSH farm.
Before you start the installation, add a new server to the Terminal Server License Servers domain 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.
You can install Remote Desktop Licensing using Server Manager. To do it, select Remote Desktop Services role in the Add Roles and Features Wizard.
Select Remote Desktop Licensing as the role service.
Wait till the role is installed.
Additionally, install the utility for diagnosing licensing problems on RDS servers — Remote Desktop Licensing Diagnoser (lsdiag.msc), which can be set using Server Manager: Features -> Remote Server Administration Tools -> Role Administration Tools -> Remote Desktop Services Tools -> Remote Desktop Licensing Diagnoser Tools (by default, when installing the RDS-Licensing service, only the Remote Desktop Licensing Manager console [licmgr.exe] is installed).
HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. AkismetThis is used to detect comment spam. Like rogues, ranger stats should be focused on Str & Dex, but this class should have more str than dex. HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. Avabel online for pc. For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: Show Details NecessaryHubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.LoginThis is necessary to sign in to the HubPages Service.Google RecaptchaThis is used to prevent bots and spam.
You can also install the RDS Licensing service and lsdiag.msc tool using PowerShell:
Install-WindowsFeature RDS-Licensing –IncludeAllSubFeature -IncludeManagementTools
Activating the RDS License Server on Windows Server
In order your RDS License Server could issue licenses to RDP clients, it must be activated. To do it, open the Remote Desktop Licensing Manager, right-click the name of your server and select Activate Server.
Locate the Terminal Server License Servers group. By default, the Terminal Server License Servers group is located in the Builtin container. Right-click Terminal Server License Servers, and then click Properties. On the Members tab, click Add. Click Object Types, select the Computers check box, and then click OK.
The RDS licensing server activation wizard will start, in which you 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 RDS license server. If there is no direct Internet access from the server, you can activate the server using a web browser or by phone.
Then you must enter some information about your company (some fields are mandatory).
It remains to click the Finish button.
If you right-click the server name in the console 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.
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 type assigned to a computer or a 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, only 10 hosts can connect to your RDS server;
- 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 license is associated with an Active Directory user and issued not permanently, but for a specific period of time (90 days, by default).If you try to use RDS 2019 Per User CAL in a workgroup (not in a domain), then the RDSH server will forcibly end a user session every 60 minutes with a message: “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, you need to use only device licensing – Per Device RDS CALs.
Note. We should note that 2016 RDS CAL may be installed only on a license server running Windows Server 2016, the installation of new CALs to the previous Windows Server versions is not supported. Those, you cannot install 2016 RDS CALs on a Windows Server 2012 R2 licensing host.
Installing RDS CALs on Windows Server 2016/2019
Now you must install the package of remote desktop client licenses (RDS CAL) you have 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 by phone) and the license program (in our case, it is Enterprise Agreement).
The next steps of the wizard depend on which license program you have selected. In case of Enterprise Agreement, you must specify its number. If you have chosen License Pack (Retail Purchase), enter the 25-character product key you got from Microsoft.
Specify the product 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 issue licenses (RDS CAL) to clients.
You can convert User CAL RDS to Device CAL (and vice versa) using the Convert Licenses menu item in the RD Licensing Manager console.
If you have run out of free RDS licenses, you 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()
How to Remove RDS CALs from a RD License Server?
If you want to transfer your RDS CAL license set from one Remote Desktop licensing server to another, you can remove installed CAL licenses pack from the licensing server using PowerShell.
Using the following cmdlet, you can list all the installed RDS CAL packages 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:rootCIMV2 PATH Win32_TSLicenseKeyPack CALL UninstallLicenseKeyPackWithId yourKeyPackId
You can also completely remove all CALs by re-creating the RDS license database. To do this, stop the Remote Desktop Licensing service:
Stop-Service TermServLicensing
Rename the file
C:WindowsSystem32lserverTLSLic.edb
to C:WindowsSystem32lserverTLSLic.edb_bak
and start the service:Start-Service TermServLicensing
After that, all RDS CAL licenses will be deleted, and you must reactivate them.
Specify a License Server Address on an RD Session Hosts
After the RDS License Server is activated and running, you can reconfigure RD Session Host to obtain CAL licenses from this server. You can set the license type and specify the name of the license server from the Server Manager GUI, using PowerShell or GPO.
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 the RDS license server. Click Add -> Ok.
If the licensing type is not set on the RDSH server, you will receive the error “Licensing mode for the Remote Desktop Session Host is not configured”.
You can 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 need:
$obj.ChangeMode(4)
Note. Enter 4 if the server must use Per User licensing type, and 2, if it is Per Device.
Then specify the name of the RDS License Server:
$obj.SetSpecifiedLicenseServerList('rdslic2016.woshub.com')
And check the current settings:
$obj.GetSpecifiedLicenseServerList()
When configuring RDS licensing parameters for RD session hosts via GPO, 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 in the following GPO section : Computer Configuration -> Policies -> Admin Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Licensing
There are 2 RD policies that we need to configure:
- Use the specified Remote Desktop license servers – the address of the License Server is set;
- Set the Remote Desktop licensing mode – select RDS CAL license type.
- TCP/135 – Microsoft RPC;
- UDP/137 – NetBIOS Datagram Service;
- UDP/138 – NetBIOS Name Resolutio;
- TCP/139 – NetBIOS Session Service;
- TCP/445 – SMB;
- TCP/49152–65535 – RPC dynamic address range
You can check for open ports using the PortQry utility or the Test-NetConnection cmdlet.
Try to check the License Server status and the number of the issued licenses using RD Licensing Diagnoser (Administrative Tools -> Remote Desktop Services -> RD Licensing Diagnoser).
If there are no warnings, and you see the message“RD Licensing Diagnoser did not identify any licensing problems for the Remote Desktop Session Host server”, then the RDSH server can successfully receive RDS CALs for remote users/devices.
Note. In our case, after we specified the new License Server address the following error started to appear on the RDP client: “The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license”. The problem can be solved by removing the L$RTMTIMEBOMB key from the registry.
Installing SFTP (SSH FTP) Server on Windows with..
October 2, 2019How to Approve and Decline WSUS Updates?
September 26, 2019How to View and Parse WindowsUpdate.log on Windows..
September 25, 2019Installing a Free Let’s Encrypt TLS/SSL Certificate on..
September 20, 2019RDP Authentication Error: CredSSP Encryption Oracle Remediation
September 10, 2019Terminal Server License Server Group Name
Hi and welcome everybody to the next blog post of a series about installing and configuring Citrix XenApp 7.13 on Windows Server 2016. After the sucessfull installation of the Microsoft Remote Desktop (RDS) Licensing component we now need to configure it.
So today we will configure Microsoft RDS Licensing. The RD Licensing Manager can be started over a Start Menu link or through a link in the Servermanager. It is not necessary to add RDS Licenses if you are in a lab environment because the License Server will issue temporary licenses for 180 days and in most cases this should be sufficient for a few tests or demos.
The first thing you will notice is that the License Server is not activated. You can see that on the red mark left to the server name.
If you right click on the server name you can open the configuration of the server. You can see that the Discovery Scope of the License Server is configured to Domain.
To change the scope the user we use to reconfigure this option needs to have Enterprise Admin privileges in Active Directory. Click CONTINUE.
In the next screen you can choose The forest. Click OK.
Choosing Forest makes this Licensing Server available to multiple domains within the forest. Click OK again to finish the configuration for the scope.
In the next step we will add this License Server to the Terminal Server License group. Without this configuration the License Server won´t issue CALs to users and no reporting will be possible. Click ADD TO GROUP.
In the next screen click CONTINUE.
Click OK in the next screen to finish the configuration.
The next screen shows green checkmarks for all configuration items. Click OK.
Terminal Server License Servers Group In Active Directory
Now right click on the server name again and start the Activate Server Wizard. Click NEXT.
Event Id 4105
There are a few options you can choose to activate the license server. I have internet access and therefor I will leave it on Automatic connection (recommended).
In the next screen type in your First name, last name, company and Country. Click NEXT.
Add further company information. Click NEXT.
With the next screen we are ready to activate the license server. Leave the checkmark next to Start Install Licenses Wizard now activated.
Buy Terminal Server License
The Activate Server Wizard opens. Click NEXT.
Again we have a few options to choose for a license program. Led drivers constant current dimmable. As Microsoft partner we have access to a few licenses. I will leave License Pack (retail Purchase).
Make sure an upcoming wedding celebration is a beautiful event attended by all the loving and supportive friends and family. Use one of our wide selection of premium wedding invitation templates that you can download for free. Our files are ready-made with professionally designed content for your convenience. Even though we're serious stationery lovers, it's okay if all you really want out of your wedding invitation is a piece of paper that informs guests of a date, time and a location.If a simple invite is more your style and you want to keep paper costs low you can go the DIY printable template route—just remember anytime you take on a sizable wedding task solo there may be a couple more. For an extra personal touch, choose an invitation that includes your uploaded photos, featured or overlaid with text. Create your own wedding monogram and add it to your invitation design to make it extra special. It’s easy to design your invitation, download the image or PDF file, and have it printed at your local print shop on specialty paper. Editable wedding cards free download.
On the next screen we need to type in a License code. Click ADD and NEXT.
We´re done with adding Licenses. Click FINISH.
Now you should be able to see the newly added Licenses in the RD Licensing Manager.
Set Terminal Services License Server Group Policy
That´s your Microsoft RDS Licensing server on Windows Server 2016.
Manually Add The Server To Terminal Server License Servers Group
Cheers,
Sinisa
Sinisa