• Set Rds License Server Registry Search
• Flexlm License Server
• Rds License Server In Azure
• Rds Licensing Mode Registry

If this is happening after the license grace period AND you already had a setup a license server, please try the below steps. Login to the server and open Registry by typing regedit.exe in Run or cmd prompt.(please note that this should be opened as Administrator. Server 2012 RDS: No Remote Desktop License Servers Available By David K. Sutton Using a VMware template, I recently deployed the 9th Windows 2012 Remote Desktop Services server in our RDS collection.

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 afterward. 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 onthe 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 untill 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).

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 to issue licenses to RDP clients, your RDS License Server must be activated. To do it, open the Remote Desktop Licensing Manager, right-click the name of your server and select Activate Server.

The RDS licensing server activation wizard will start. Here 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 of 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 ending 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.

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 being run, 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.

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)

Set Rds License Server Registry Search

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).

Flexlm License Server

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.

Using a VMware template, I recently deployed the 9th Windows 2012 Remote Desktop Services server in our RDS collection. After adding the new host server to the collection and attempting to launch a RemoteApp session, I received the following error:

RemoteApp Disconnected

The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license. Please contact the server administrator.

Assuming your licensing configuration is valid and you have licenses available, if you receive the above error the problem is likely an expired “GracePeriod” registry key. In our case, this “GracePeriod” key found its way into the registry at some point when this template was built. And since it was built many months ago, this grace period has since expired. You’d think RDS would be smart enough to see the license server in the domain and act accordingly, in this case, talk to the license server, confirm there are available licenses and then either ignore the grace period key or remove it. But nope, it just gives you the above error instead.

Lucky for you the fix is easy. You simply delete this key manually.

Rds License Server In Azure

Open up the registry editor and browse to:

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerRCM

You should see a key called “GracePeriod”. Right-click this key and then click “Permissions.” Assign yourself (or Administrators, assuming you are part of that group) “Full Control” and then DELETE the key. You won’t be able to delete it unless you give yourself at least read/write permission (Full Control is just expedient). Now reboot the server and everything will be right as rain.

If you deploy your RDS hosts via a template like I do, it’s probably a good idea to delete the GracePeriod key from the registry in that template. Because you know you will forget to do this next time!

Rds Licensing Mode Registry

Thanks to RobBot for providing the solution.