Overview

In my previous post I did a step-by-step walk through the installation and configuration of a Citrix licensing server. It was the first part in my series showing how you can create a small scale Citrix remote access solution in a home lab. In parallel to this, I’m looking at configuring a remote desktop 2012 environment; to support this and the windows component of citrix I’ll need a remote desktop license server and this post will provide a quick high level overview of the steps involved. Like my previous post it will make assumptions on your knowledge and wont detail basic VM level configuration.

As with my Citrix Licensing post, the resourcing requirements aren’t all that demanding, the OS minimum needs should also cater for the RDS2012 licensing needs so I’ll be using my standard 1vCore & 4GB RAM VM. The only difference, as per the Citrix licensing server will be using vmxnet3 as the NIC type, requiring VM tools for full functionality. Once the build is completed, set the IP, Hostname and join your domain as normal.

License Server Installation

Load server manager and select ‘Add Roles and Features’ click next (and optionally select the check-box not to be bothered about the hints page again)

Select the ‘Role Based or feature-based installation’ and click next, select your server, in my case BNELIC02 and hit next. Select the ‘Remote Desktop Services’ box and ‘Next’ three times. On the ‘Role Services’ screen check the box next to ‘Remote Desktop Licensing’ and click next.

Select the ‘Restart Destination server automatically if required’ and click ‘Install’ – as indicated dont be surprised if your VM restarts 1 or more times during while installing.

Once finished, click ‘Close’ and you will see an extra tree-view item in server manager ‘Remote Desktop Services’, click on it, ignore the error on the overview tab relating to RD Connection Broker Services and click ‘Servers’. Right click the license server and select ‘RD Licensing Manager’

License Server Activation

When first loaded, you will notice an action requiring review (review link under configuration column) – click ‘Review’ to continue.

The dialogue will tell you that the problem is due to the license server not being in the ‘Terminal Server License Servers’ group in AD, click ‘Add to Group’ to resolve followed by OK. We’re not finished yet since the server still needs to be activated. We have two steps remaining, 1) activating the server with microsoft (this allows it to track key issue) and 2) adding a license pack of RDS CAL’s

Right Click the server in the tree-view on the left hand site of the window and select ‘Activate Server’, click Next, select ‘Automatic Connection’ and click Next. The service will attempt to connect Microsoft before prompting you for additional information. Complete and Click next.

You will be asked for additional information again, complete as appropriate and click next. The service will again contact Microsoft to active your server, once complete cancel the ‘add license’ dialogue and verify that your service looks as per below.

License Installation

From the activated license server, right click the server name and select ‘Install Licenses’ you will be asked for the license type, and based on this will be prompted for the license details i.e a key for a retail edition, or license number and authorization number for open licenses.

Summary

In this post we have created a license server VM, installed the RDS 2012 license server role, activated the server with Microsoft and installed a RDS CAL. In an earlier post we handled the same for the Citrix licensing. Combined we have created the supporting infrastructure for a Citrix and/or RDS 2012 remote access platform which we’ll explore in my future posts.

Any questions please get in touch via social channels or good ole’ email.