RDS Licensing without a RD Connection Broker? No problem.

One of the things that I see happening in our labs and often in customer environments is problems with configuring RD Session Host licensing when you do not have a RD Connection Broker in the mix. With the introduction of Microsoft Windows Server 2012 Remote Desktop Services, came the dependency of the RD Connection Broker when configuring RDSH licensing. This becomes very evident when trying to accomplish this in the Server Manager GUI. The next logical step, of course, is to attempt this via PowerShell. If you have also tried this, you will have realized that it cannot circumvent the RD Connection Broker requirement either.  After an attempt with the GUI and PowerShell, what is left?  The answer is Group Policy.

RDSH licensing configurations can be set on a per host basis with the Local Group Policy Editor or more centrally with Group Policy Management Editor and apply to multiple hosts at once. The group policy settings in question can be found here:
Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Licensing\
 Or for a more visual representation:



The first setting to configure is "Use the specified Remote Desktop license servers" with the FQDN of the RD Licensing server, as seen below:


The next setting to configure is "Set the Remote Desktop licensing mode" as Per User or Per Device. I have set it to Per User as seen below:


Once all of this has been set, then the Group Policy Object will need to be linked to the appropriate OU where the RDSH servers are listed. A Group Policy update or reboot will need to be ran on the RDSH servers before the new settings take effect.  After that, all should be well.

Comments