Server 2012 RD Licensing mode is not configured

Hi,

I have installed a brand new Server 2012r2 to be used a remote desktop server.
I have a second server that has the licensing function.

Whenever I log in as administrator the message "Remote Desktop licensing mode is not configured" keeps popping up.
pop up error message licensing
I have installed the Remote Desktop Services Connection broker and used deployment properties to set the licensing server. It is configured as "Per User" and the correct server is set.

If I use Get-RdlicensingConfiguration in powershell it also gives me the correct licensing server.

Should I be worried after the grace period is over that users wont be able to logon?

Thanks in advance,

Joachim
LVL 1
ItxxAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
MaheshConnect With a Mentor ArchitectCommented:
Please logon to licensing server and locate below reg key
HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\Grace Period

Delete any values present in this folder except default value
If you face any issues, take ownership of that registry key and assign you full control and then delete all values
Then reboot the server and check if it works

If still it fails, you need to enter licensing server manually on RD licensing server
From elevated PowerShell Prompt run below commands

$LSServer = gwmi -Namespace "Root/CIMV2/TerminalServices" Win32_TerminalServiceSetting
$LSServer.GetSpecifiedLicenseServerList()

Open in new window


The above command will tell you if any licensing server is registered, if found none

Run below command
$LSServer.SetSpecifiedLicenseServerList("Licenseserver.domain.com")

Replace server name with yours

Then reboot the server and see if it works
Original article:
http://www.blackforce.co.uk/2014/02/17/2012-rds-server-the-remote-desktop-session-host-server-does-not-have-a-remote-desktop-license-server-specified
0
 
Cliff GaliherCommented:
You should be concerned. Does your RDCB server have the RDSH server added as a part of the deployment? That is the first common mistake I see.
0
 
ItxxAuthor Commented:
Yes, it is only one server. Maybe I'm doing something wrong.
I have just tried removing the Remote Desktop features and installing it again.

I used Add roles and Features and installed Remote Desktop Services including Connection Broker, Licensing & Session Host.
Afterwards I've ran the wizard again and used Remote Desktop Services installation -> Standard deployment -> Session-based desktop deployment and install the RD Connection Broker server.

Then I edited the deployment properties and installed the licensing server.
0
 
ItxxAuthor Commented:
That worked for me!

I didn't have the GracePeriod registry but running the Powershell commands fixed it for me.

Many many thanks.
0
 
MaheshArchitectCommented:
Ya, that's true, some has found GracePeriod Registry \ some not, however forcing license server through PowerShell fix the issue most of the time.

Thanks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.