When using XenDesktop 7.0 with a hosted shared desktop or app publishing scenario you will have to install a vda-agent onto the Windows Server to be able to publish apps or shared desktops.

During the install there is no check for existence of a RDS licensing server. In theory you can use the 120 day evaluation period to test with. But what when you’re done testing and want to make it permanent by adding RDS licensing?

Using Windows Server 2008 R2 or earlier is pretty straightforward. Because the Windows Server 2008 R2 RDS licensing  in my case already existed, even with older Windows Terminal services licensing, there was no need for a evaluation period.

Windows Server 2012 RDS is another story, this gives some extra headaches. Because we’re using Citrix as a connection broker we don’t have a complete Microsoft Remote Desktop Services Deployment in place.

First we need to add a RD licensing server role because this is the first Windows Server 2012 RDSH in the environment. So far so good.

Second we need to activate the license server, this succeeded too.

Next we need to assign the license server to the RDSH server and make sure the right licensing mode is used (we use PerUser licensing).

This is where the problems arise. Microsoft assumes you use a complete Remote Desktop Services deployment including a RD broker. Therefor you cannot set the properties of a RDSH via the GUI (with Server Manager) or through command line (with PowerShell) as shown in the screenshots below.



How to solve it?

To set the correct license server and the mode it is operating in, we need to use a (local) group policy or change it directly in the registry.

The group policy setting the Remote Desktop licensing mode is located in:

Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Licensing

This can be configured by using either the Local Group Policy editor or the Group Policy Management console.


The other way is to manually change it on the RDSH using the following registry keys:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services

LicenseServers <license server>
LicensingMode 2 for PerDevice; 4 for PerUser



After changing these settings, reboot your RD Session Host and you will see RD licensing is now in place and working!

Tagged with:

9 Responses to How to configure RDS 2012 licensing in a Citrix XenDesktop 7 scenario

  1. Maksim Teltsov says:

    This is a good solution.

  2. Heinrich Fourie says:

    Thanks for this, spent hours looking on the server, thought I was going crazy. Typical M$.

  3. topokin says:

    I do not know what I could be doing wrong, but this procedure seems not to be working in my case.

    I actually use the Local Group Policy Editor and I can see the result of my configuration in the Registry, but yet my RDP-Servers are not getting license.

    Anywhere else to look?

  4. Gerben says:

    You’ve probably done it, but one thing to check is your license server: is it 2012 also?. Are you using user based or device based licenses? Check the spelling on the hostname(especially zeros letter “o” and number 1 and letter “l”), can you resolve it using DNS?

  5. CJHarms says:

    Great post. Issue also exists for 2012 R2 RDS Hosts / XenApp Hosts.

  6. arun kumar says:

    is this process applicable for window 2008r2 and xendesktop

  7. Gerben says:

    not really, because xendesktop 5.6 is not to be used with RDS2008R2, you can however use policies to manage licensing with 2008R2

  8. Arian van der Pijl says:

    Microsoft has a KB Article specially for this;
    Guidelines for installing the Remote Desktop Session Host role service on a computer running Windows Server 2012 without the Remote Desktop Connection Broker role service.

    Interestingly enough, Microsoft does not use GPO’s but directly advices to edit the RDS host itself.
    It might because RDS Server GPO’s do interfere with the normal way of administering a RDS collection?

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>