8/23/2021

Terminal Server License Registry

44

As you read in Chapter 1, each device that connects to a terminal server in application server mode needs a TSCAL. A Terminal Services license server is used to install, distribute and manage these TSCALs. Without a license server, the terminal server will stop accepting connections after 90 days.

If you're in a Win2K domain environment, you should install the Terminal Services Licensing service on one of your domain controllers. All terminal servers in the domain will automatically find the license server. To install Terminal Services Licensing service, select the Add/Remove Programs Control Panel applet, select Add/Remove Windows Components, and select the Terminal Services Licensing check box, as Figure 2.9 illustrates.

To renew RDS grace period, you need to find the following registry key and delete it. “HKEYLOCALMACHINE SYSTEM CurrentControlSet Control Terminal Server RCM GracePeriod” Before you can delete the registry key, you need to change ownership. You can do that by following these steps: Right-Click on the key. Click on “Permissions”. The next time the client connects, an attempt is made to upgrade the validated temporary Terminal Server CAL token to a full Terminal Server CAL token. If no license tokens are available, the temporary Terminal Server CAL token will continue to function for 90 days. The license is stored in the client's registry. In the registry key HKLM SYSTEM CurrentControlSet Control Terminal Server RCM Licensing Core change the value of the DWORD parameter with the name LicensingMode from 5 to: 2 – if Per Device RDS licensing mode is used.

Windows Components Wizard

Windows Components

You can add or remove components of Windows 2000.

To add or remove a component, click the checkbox. A shaded box means that only part of the component will be installed. To see what's included in a component, click Details.

Components:

To add or remove a component, click the checkbox. A shaded box means that only part of the component will be installed. To see what's included in a component, click Details.

Components:

^ Script Debugger

1.1 MB j^j

□ ^Terminal Services

14.3 MB

Jf Terminal Services Licensing

0.9 MB ■

D É Windows Media Services

19.1 MB _

Description: Configures this computer as a Terminal Services license server that provides client licenses.

Description: Configures this computer as a Terminal Services license server that provides client licenses.

Total disk space required: 1.5 MB

Space available on disk: 4623.3 MB

Details..

Total disk space required: 1.5 MB

Space available on disk: 4623.3 MB

Details..

Figure 2.9: Installing the Terminal Services Licensing service.

Figure 2.9: Installing the Terminal Services Licensing service.

When installing Terminal Services Licensing service, you can select whether you want the server to serve licenses to the domain or the entire enterprise (forest), as Figure 2.10 shows. To set up a license server for the domain, you must be a member of the Domain Administrators group. To create an enterprise license server to distribute TSCALs to the entire forest, you must be a member of the Enterprise Administrators group.

Terminal Services Licensing Setup -'

Provide the information needed to set up this computer as a license server.

Terminal Services Licensing Setup -'

Provide the information needed to set up this computer as a license server.

Specify the role of the license server and the location of the license server database. Make this license server available to:

(* jYour entire enterprise Your domain orworkgroup

Install license server database at this location:

C:WINNTSystem32LServer

Figure 2.10: Choosing a domain license server or enterprise license server.

If you're in an NT 4.0 domain, you'll need to install Terminal Services Licensing service on a member server running a flavor of Win2K Server. When installing the service, you'll also need to specify a location for Windows to store the license database.

At this point, you should also install the Terminal Services Licensing service enhancements hotfix. This hotfix is described in and available from the Microsoft article 'Terminal Services Licensing Enhancements' at http://support.microsoft.com/support/kb/articles/q287/6/87.asp.

Activating the License Server

After you've installed Terminal Services Licensing service on the appropriate server or servers, you'll need to activate the license server. This activation sets up the server to accept TSCALs that you purchase from Microsoft. To activate the Terminal Services Licensing service, launch the Terminal Services Licensing application from Administrative Tools and select Activate Server from the Action menu.

After the initial welcome screen, the wizard, which Figure 2.11 shows, will ask you to select a method for connecting to Microsoft. For any of these methods, you will need the product ID displayed on the welcome screen, but the wizard will provide this number when necessary.

reattimepublishers.com'

reattimepublishers.com'

Figure 2.11: The Terminal Services Licensing Wizard.

The four connection methods are:

Internet—If you select this option, the wizard will then ask you to complete a form containing your company's information and an email address. Your 35-character PIN is emailed to the address you provide.

World Wide Web—If you select this method, the wizard will instruct you to go to https://activate.microsoft.com and fill out your company information. Your PIN will be sent to you through email.

Fax—For this option, the wizard will have you select your country, then ask for your company information and fax number. Next, you're instructed to print the form and fax it to Microsoft, who will respond with your PIN by fax.

Telephone—In this method, you select your country and are provided with the appropriate customer service number. A representative will take your company information and provide your PIN immediately.

After you select your connection method, the wizard asks how you purchase licenses from Microsoft, as Figure 2.12 shows. If you're a Select or Open License customer, be sure to have your account number available when you attempt to install licenses. Select the Other radio button if you're not a Select or Open License customer. You purchased your TSCALs through a retail channel and have the paper license numbers included in the package.

Figure 2.12: Selecting your licensing program.

After you complete the wizard, you'll be emailed, faxed, or told a 35-character PIN. After you enter the PIN, your Terminal Services Licensing service is active and ready to accept license packs.

^ If you're using the telephone connection method, I recommend typing the PIN and license codes into the wizard while the representative is still on the line to be sure that you enter it without errors. If you write it down incorrectly, you'll have to call again.

Installing Licenses

After activation, the server will immediately begin handing out permanent CALs to Win2K devices. To issue permanent CALs to non-Win2K clients, you'll need to install license packs on the Terminal Services Licensing service. To do so, use the licensing wizard in the Terminal Services Licensing application.

The license program and connection method you selected when activating the server determines how you obtain license pack codes. If you need to change the connection method or license program, you can do so in the properties of the server in the Terminal Services Licensing application. The licensing wizard will ask you for the license code, then activate the number of CALs included in the code, as Figure 2.13 shows.

Figure 2.13: The Terminal Server Licensing wizard.

After CALs are installed on the server, non-Win2K clients will be issued a permanent license upon their second connection to the terminal server and Win2K clients will have their built-in license activated.

How Does the Terminal Server Find the License Server?

The Microsoft article 'Description of Terminal Services License Server Discovery' at http://support.microsoft.com/support/kb/article/q232/5/20.asp explains how a terminal server finds a license server. The method used is different depending on the environment.

Win2K Domain

• The Terminal Services License Service must be installed on a Win2K domain controller in the domain.

Terminal Server 2003 License Registry Key

• The Terminal Services server must be running on a Win2K domain controller or a Win2K member server with one or more Win2K domain controllers in the same domain.

• The Terminal Services-based computer looks for the license server by using a remote procedure call (RPC) to all Win2K-based domain controllers in the same domain and querying them for the Terminal Services Licensing service. The client chooses one of the license servers at random, then requests a license key pack from that license server. The license server passes the request to the enterprise license server if no license key pack is available.

• If the Terminal Services server cannot find a license server in the domain, the Terminal Services server queries the directory service for the enterprise license server.

Terminal Server License Registry

NT 4.0 Domain

Terminal Server Licensing Registry

• The license server must be running on a Win2K member server and all domain controllers must be running NT 4.0.

• The Terminal Services-based computer issues broadcasts on a mailslot. All Terminal Services license servers that receive the broadcast respond. The Terminal Services-based computer selects one of the licenses servers at random.

Workgroup Environment

• The Terminal Services server and licensing server are in a workgroup.

• The Terminal Services-based computer issues broadcasts on a mailslot. All Terminal Services licensing servers that receive the broadcast respond. The Terminal Services-based computer selects one of the license servers at random.

^ If you're running Terminal Services in a separate but trusted domain or forest, you can instruct your Terminal Services servers to use a specific license server by adding the following registry value:

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTermServiceParametersDefaultLic enseServer

Reset terminal server license registry

Create this value as a REG_SZ value and give it the NETBIOS name of the license server. The server needs to be able to find the Terminal Services license server by its NETBIOS name, so you may need to use an LMHOSTS file if you're not running WINS in your NT 4.0 domain.

Continue reading here: Summary

Exploits downlodsihyper. Was this article helpful?

Are you tired of getting the error remote desktop licensing mode is not configured and the Remote Desktop Services will stop working in xx days? Learn how to fix it.

Do you want to get rid of the Remote Desktop licensing mode is not configured or Licensing mode for the Remote Desktop Session Host is not configured error as quickly as possible?

Well, if you are a system administrator who works with Remote Desktop Services (RDS) and uses Windows Server 2016 or Windows Server 2012 R2 very frequently then at some point you may have encountered the Remote Desktop licensing mode is not configured error.

Usually, this error appears as a notification popup in the bottom right-hand corner of the screen saying:

Remote Desktop licensing mode is not configured

Delete Terminal Server License Registry

Remote Desktop Services will stop working in xx days. On the RD Connection Broker server, use Server Manager to specify the Remote Desktop licensing mode and the license server.

And when you click on this notification popup, it doesn’t redirect you anywhere and it gets simply disappeared which is a quite frustrating situation.

On the Remote Desktop Licensing Manager, if there are valid licenses installed and everything seems accurate, and still, a popup appears that says Remote Desktop services will stop working on specific days then this circumstance is bound to scare almost anyone.

So, if you want to know how to fix remote desktop licensing mode is not configured error on Windows server then follow our handy guide which we brought to you today. So, without further ado, let’s begin.

Do you know? How to Shutdown or Restart Remote Desktop Connection Windows 10

How to Fix Remote Desktop Licensing Mode is Not Configured

Although, various expert users suggest different solutions to get rid of the remote desktop licensing mode is not configured on the RD connection broker server error and there are multiple methods available on the web for dealing with this issue as well. But here we are going to share only those active methods that are extremely easy to execute and work ideally in almost all situations.

So, let’s check out how to fix Remote Desktop licensing mode is not configured error on Windows Server:

Method 1: Using Windows Registry Editor

There are several ways to set the RDS licensing mode, but doing it via the Windows Registry Editor is the most convenient way. Here’s how to change the licensing mode for Remote Desktop session host using the registry editor and get rid of the error message Remote Desktop Services will stop working in xx days:

Step (1): At first, press Windows + R keys together and then type regedit in the Run dialog box and press Enter key.

Step (2): In the left pane of the Registry Editor, navigate to the following registry key:

HKLMSYSTEMCurrentControlSetControlTerminal ServerRCMLicensing Core

Step (3): Now in the right pane, double-click on the LicensingMode to edit its value and then change the Value data according to your requirement:

  • Set the Value data 2 for Per Device RDS licensing mode
  • Set the Value data 4 for Per User RDS licensing mode

Step (4): Finally, click on the OK button to save the changes.

Now, restart your computer and check if the Remote Desktop licensing mode is not configured issue on Windows Server has been resolved or not.

Once you changed the licensing mode, now everything will be reported accurately and the Remote Desktop session host will recognize the licensing configuration.

You might also like to know: How to Use Remote Desktop Connection in Windows 10

Method 2: Using Local Group Policy Editor

If you are the administrator who has high-level access to the system then you can also use the Local Group Policy Editorto change the licensing mode for remote desktop session host.

Here’s how to change RDS licensing mode using Group Policy and solve the remote desktop licensing mode is not configured on Windows server error:

Step (1): First of all, press Windows + R keys together and then type gpedit.msc and press Enter key.

Step (2): On the Local Group Policy Editor, navigate to the Computer Configuration > Policies > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Licensing.

Step (3): Now double-click on the “Use the specified Remote Desktop license servers” setting and then select Enabled option. Finally, enter the names of the license servers (host name or IP address) and then click on the OK button.

Step (4): Similarly, double-click on the “Set the Remote Desktop licensing mode” setting and then select Enabled option. Finally, set the licensing mode (Per Device or Per User) and then click on the OK button.

Once all these changes are done, close the Local Group Policy Editor and then restart your computer.

Now open the Remote Desktop Licensing Diagnoser and you shouldn’t see any errors like the remote desktop licensing mode is not configured on windows server or any kind of issues regarding your licenses.

Conclusions

So these are the two easiest methods you can use to solve the Licensing mode for the remote desktop session host is not configured issue on Windows server. Now no need to get scared after seeing the notification popup saying the Remote Desktop Services will stop working on the RD connection broker server.

If you need any more help related to the Windows Server 2016 or Windows Server 2012 Remote Desktop licensing mode is not configured error or have any other queries regarding remote desktop services then feel free to let us know in the comments below.

You may also be interested in checking out: