Terminal Services / RD licensing set up on Server 2012

I don't know if it's just me or if Microsoft really overcomplicated how this works on Server 2012 (compared to 2008/2003)

We have one "Licensing Server".  Then we have machines joined to our AD domain.   All we used to need to do was set up terminal services on the client machine, point to our licensing server, and give it the extra user-CAL's it needed (something like that, it's been a while but I remember it was really simple)

Server 2012 seems quick a muck up...

I'm not even sure exactly what to install but the process of getting RD Licensing on the client machine. it seems to end up making me install EVERYTHING (RD Licensing, RD Gateway, RD Connection Broker, RD Virtualization Host, RD Session Host). I know I don't need everything but I didn't see any other way.

So where I'm at now, is that I did somehow get it working (more than 2 users are able to RDP simultaneously into the client machine currently),  but the user is seeing a warning pop up in their task menu saying:

'Remote Desktop Services will stop working in xx days. On the RD Connection Broker server, use Server Manager to specify the Remote Desktop licensing mode and the license server.'

I found this article:
but it has steps via Group Policy.

I don't know if that is necessary I'd rather not use GP because all these client machines are under one OU, but some are Server 2003 and use a different licensing server for example so I don't want to change the GP for the entire OU.

I may have set this up all wrong on this 2012 client machine I don't know.  Is there a way to set this up to be completely stand-alone? (be it's own licensing server and everything self-contained), because I can't find any way to point it to our licensing server (which doesn't run 2012 so maybe it won't be possible anyway)

If my question sounds confusing, let me first ask this:

- if the server is joined to OUR domain, can it still be a self-contained licensing server, or does the fact that it's joined to our AD mean we have to point it to our licensing server somewhere?

In other words, I don't necessarily mind setting this up as a stand-alone and not needing an external licensing server, but WILL THAT WORK if this machine is joined to our AD domain?  

Below are screenshots of how things look currently on the client machine.  This is working (3-4 users can be RDP'd in at once), but something will stop working in 72 days, so obviously I didn't do this 100% correct.

I don't currently see any way to point this client machine to using our licensing server.

(These are all screenhosts from the client machine)

RD Licensing Manager

Deployment Overview

When I right click and go to "Add..." on either the 'RD Licensing' or the 'RD Session Host' icons, I basically get an empty window  and have no servers to select  (nothing under Server Pool, nothing under Selected)

For example:


Again, I'd gladly make this a standalone session host/licensing server, I think that would be easier if it's possible and can be done even though the machine is joined to our AD domain.

Thanks for any assistance.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

DrDave242Senior Support EngineerCommented:
Do you already have a Remote Desktop licensing server running 2012 or later in your environment?
VasAuthor Commented:
No, the one we do have is a 2008 licensing server.

WIll I be able to just install all this as stand-alone on the client machine (does it matter if they are joined to our AD)?

Right now it is pretty much a stand-alone set up, just not sure what is missing exactly.

DrDave242Senior Support EngineerCommented:
Yes, you can install the needed role services on a single domain-joined machine. In fact, it's easiest to manage that way, unless that machine is also a domain controller.

You'll need the Session Host, Connection Broker, and Licensing role services on that machine; the Virtualization Host and Web Access services can be removed if you're not going to use them.

To specify a license server and licensing mode in Server Manager, click the Remote Desktop role on the main dashboard, then click the Tasks dropdown at the top of the Deployment Overview section and select Edit Deployment Properties.

In the properties window, click RD Licensing, then select the appropriate licensing mode and specify the license server and click OK.
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

VasAuthor Commented:
Hi DrDave,

Getting close I think, but here's where it's still stuck.

So I did what you said  (Tasks -> Edit Deployment Properties), and at first there wasn't anything configured for the type of licensing mode, so I set it to PER-User.

The local server name was already in the bottom screen.

I thought that would fix the issue but I logged out / in and still had an error which is this:

Task Error

This says to specify the

I went back into the settings and they did save, it shows Per User is selected and lists the FQDN of the local server in the 2nd box:

Deployment Properties - RD Licensing

So this does now appear configured after I made the change you suggested,  but it's still complaining about something.
DrDave242Senior Support EngineerCommented:
I've seen this happen for no apparent reason before. Try restarting the Remote Desktop service or rebooting the server, as this sometimes fixes it.
VasAuthor Commented:
Hi DrDave,

Still struggling with this. Rebooting didn't resolve the problem.

You mentioned I need "Session Host, Connection Broker, and Licensing role services", which are all there.

I do see the local server name if I right click Session Host or RD Licensing and select "remove" (I didn't remove anything, just mentioning that I do see the server name listed there)

For RD Connection Broker however, those items are grayed out (I can't add or remove):

connection broker

I suspect this is the problem? I don't know why it's grayed out however.

Also, do I need to create a "collection"?

DrDave242Senior Support EngineerCommented:
In Server Manager, open the Tools menu and select Terminal Services > RD Licensing Diagnoser. What does it report?
DrDave242Senior Support EngineerCommented:
In Server Manager, open the Tools menu and select Terminal Services > RD Licensing Diagnoser. What does it report?
VasAuthor Commented:
Ok yes it shows all kinds of issues there:


I think the user may have changed or removed some things as I know I installed 2 licenses on this server when I initially set this up, now I don't even see the 'Remote Desktop Licensing Manager' installed on this box  :/

I think I will remove all these RD related roles/services and start over.

It looks like the user tried to install Active Directory for some reason recently (but didn't promote it to a PDC), I had them remove that since they are joined to our domain and so don't need AD Services, not sure if that or something else broke all this.

In a nutshell, assuming I start fresh,  when installing all this again do I need to go through the install twice?  Once, selecting "Role-based or feature-based installation",  and then again selecting "Remote Desktop Services Installation".  

When I initially set this up I tried to do the minimum of what was needed but it always seemed something was missing and I had to go back and install everything in the end.

I really hate what Microsoft did to RD services in 2012.
DrDave242Senior Support EngineerCommented:
(Sorry for the double post earlier. That's happened to me a few times recently, and I'm not sure why.)

In a nutshell, assuming I start fresh,  when installing all this again do I need to go through the install twice?  Once, selecting "Role-based or feature-based installation",  and then again selecting "Remote Desktop Services Installation".
Remote Desktop Services Installation should be all you have to do, although if you select the Quick Start deployment, you'll have to go back and add the Licensing role service, as Quick Start doesn't include it...for some reason.

I really hate what Microsoft did to RD services in 2012.
I completely agree. Compared to previous versions, the RD management interface is just awful. Add in the goofy requirement for the Connection Broker service in a single-server deployment, the kind of licensing issue you're seeing (which I've run into multiple times), and the absence of good documentation, and you get a real mess.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
VasAuthor Commented:
Thanks, haven't heard back from our user so haven't been able to re-do the configuration but wanted to give you credit for your answers.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.