Windows 2000 Server Terminal Services usually uses a license server in the local domain; however, you might want to have a central license server for audit purposes or use a server in another domain. Perform the following steps to designate the license server you want a Terminal Services server to use: Start regedit.exe. Registry Keys for Terminal Services The relevant configuration options for terminal servers, terminal server sessions, users, and clients can be found in different places in the registry. The administration tools and Group Policies, described in the previous chapters, usually change several registry values. Apr 06, 2019 Remote Desktop Services (Terminal Services) https. In RD Licensing Diagnoser on Server 2016, I get a message that the licensing mode for the Remote Desktop Session Host server is not configured. How does one set this. I cannot find the 'RD Session Host Configuration Tool' like I we have used in the past with Windows Server 2008 R2 to. Jun 16, 2018 New licensing registry keys will be created the next time you try to access launching your applications, thus allowing the Citrix Receiver to successfully virtualize your application thereafter. If you haven't done so already, please consider creating a system restore point prior to proceeding.
A fully functional and activated 2012 Remote Desktop Session Host server displayed the following message:
This was a simple setup on one server with the: connection broker, Session Host and Licensing server with 2012 CAL’s installed.
Even though the licensing seems to be configured correctly, in server manager:
and powershell:
Citrix Terminal Server License Registry
Licensing diagnostics:
Terminal Server License Server Group
everywhere you look, everything seems to be OK. But the license manager shows something odd:
Set Terminal License Server Registry
No licenses are being used? This server was used since late 2012. Some interesting things could also be found in the event logs, the following events appear:
EventID: 1130
Source: TerminalServices-RemoteConnectionManager
Source: TerminalServices-RemoteConnectionManager
The Remote Desktop Session Host server does not have a Remote Desktop license server specified. To specify a license server for the Remote Desktop Session Host server, use the Remote Desktop Session Host Configuration tool.
and:
EventID: 1128
Source: TerminalServices-RemoteConnectionManager
Source: TerminalServices-RemoteConnectionManager
The RD Licensing grace period has expired and the service has not registered with a license server with installed licenses. A RD Licensing server is required for continuous operation. A Remote Desktop Session Host server can operate without a license server for 120 days after initial start up.
The solution was to delete the REG_BINARY in
Terminal Server License Error Registry Fix
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerRCMGracePeriod
Terminal Server License Registry Key Windows 7
Only leaving the default.
![Terminal Server License Registry Terminal Server License Registry](https://www.tbngconsulting.com/hs-fs/hub/240153/file-3708046810-png/images/registry_editor-resized-600.png?t=1510085828591)
Note: you must take ownership and give admin users full control to be able to delete this key.
Windows Terminal Server License Registry Key
After a reboot the server should be working again, licenses are now being used:
Terminal Server 2003 License Registry Key
Although everything seemed to be ok and configured correctly with valid licenses, it seems that the setup was still in a 180 day grace period, even though it was correctly configured.
A possible bug in RDS 2012?
A possible bug in RDS 2012?