RDS License Server - Windows 2012

Hello.  We are standing up a new environment in Windows 2012 that will require multiple users to access server desktops.  To accommodate this, we understand we need to implement RDS Licensing to handle more than 3 users at a time.  Currently we have a Windows 2008 R2 Server setup that is handling users accessing Remote sessions under the grace period license, this was a temporary setup until the 2012 could be completed.

We have setup a Windows 2012 system with the basic RDS License Server and applied our licenses. This looks good and is operational when viewing the Remote Desktop Licensing Manager, everything is working as expected.  

We have installed the Remote Desktop Services, used the quick setup per articles on the web which installed the RD Gateway, RD licensing, RD Connection Broker, RD Session Host, and RD Web Access.  We have initially started with our setup here.  In looking at the different aspects, it is not providing any errors or indicating something is not configured.

However, if you view the RD Licensing Diagnoser, it indicates that "Licenses are not available for this Remote Desktop Session Host server, and RD Licensing Diagnoser has identified licensing problems for RD Session Host Server."  The remote Desktop Session Host server is withing its grace period, but the RD Session Host server has not been configured with any license server.  This clearly is not seeing Remote Desktop Services or the Licensing Manager.

The question, we are simply using this box as you could say a 'jump' machine to access other systems as this resides in AWS.  There is a plethora of information on the web, but we are having trouble pealing apart the pieces we need for simple setup of the RD Session Host so users can RDP to the system they need.  The simple setup in Windows 2008 is no more. ;)

 So, any guidance and direction would be appreciated and helpful in terms of best / simple practices in getting this setup.

Thanks
jnordengAsked:
Who is Participating?
 
jnordengConnect With a Mentor Author Commented:
Thanks for pointing me in the right direction.

I have applied the following and this corrected it.  Thinking the biggest issue is the reg key wasn't getting set.

$obj = gwmi -namespace "Root/CIMV2/TerminalServices" Win32_TerminalServiceSetting
$obj. SetSpecifiedLicenseServerList("licserver.domain.local")

Then, go into the registry and manually set the licensing mode:

HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\Licensing Core\LicensingMode


Reboot server to apply reg key.
0
 
LesterClaytonConnect With a Mentor Commented:
I too don't like the way they made RDS configuration, which requires you to use Server Manager to do everything and all the servers inside your Remote Desktop pool.

In a nutshell, any RDS server that users will actually log on to - i.e. the Windows Session Host servers - needs to be configured to talk to an RDS license server.  You can configure the licensing configuration on individual servers using the following powershell command:

Set-RDLicenseConfiguration -LicenseServer <String[]> -Mode <LicensingMode> {PerDevice | PerUser | NotConfigured} [-ConnectionBroker <String> ] [-Force] [ <CommonParameters>]

Open in new window


Simple example: my License server is mgmt34, and my RDS session host is mgmt35, and I am licensing it per user, I'd open up a powershell session on mgmt35, and run

Set-RDLicenseConfiguration -LicenseServer mgmt34  -Mode PerUser

Open in new window


This will hopefully fix the problems you have.
0
 
jnordengAuthor Commented:
Thanks, that is a good start and glad someone else isn't too excited about the change.  

My RDS Session Host and License server are on the same system.  That's why I'm so confused about the two areas of the product not seeing each other.  

I have run the powershell statement you provided, but it tells me that my server is not a valid license server.

Thoughts?
0
 
jnordengAuthor Commented:
The information provided pointed me in the right direction, but wasn't complete.  Thanks for getting me started. :)
0
All Courses

From novice to tech pro — start learning today.