Install the Remote Desktop Licensing Role Service and License Manager on Server 2012

I am trying to install the Remote Desktop Licensing Role Service and License Manager on Server 2012 that is NOT joined to a domain. We have two server 2003 'jump server'  boxes that both have unlimited Terminal Services licenses. I want to move those licenses from those two servers to the two server 2012R2 standard VM's that will be replacing them. I have tried a few things with limited success. The broker service does not need to be running since all we're going to be doing is RDP-ing into these two new servers. Keep in mind these two servers are NOT on a domain.

I found this:

From what I can tell, the Remote Desktop Licensing and Remote Desktop Session Host roles need to be installed. It also looks like I need to add the License Server role too in step 3? I'm confused. How do I successfully transfer all the licenses to the new servers?
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.

jimlock720Author Commented:
Another title for this question is Remote Desktop (Terminal Services) Configuration on a Server Standard 2012, standalone installation
Casey WeaverManaged Services Windows Engineer IIICommented:
You'll need to install the RDS Licensing role on the 2012 servers. Then install your 2003 licenses on the 2012 boxes. Then tell your 2003 boxes to use the 2012 license server instead of the 2003 server currently in place. You can skip all the steps there regarding setting up AD or the RDS Host role. All you need is the licensing role added. Install your licenses like you did the day you brought the 2003 server up. Then point your 2003 servers at your 2012 server for licensing.
jimlock720Author Commented:
I've requested that this question be closed as follows:

Accepted answer: 20 points for Casey Weaver's comment #a40637634
Assisted answer: 0 points for jimlock720's comment #a40637608

for the following reason:

Thank you for your answer. I take it that installing more than the RDS licensing role would be overkill since all we're doing is having 12 people RDP into the servers at the same time? So install ONLY the RD Licensing role and ignore the AD stuff? I'll give that a try but that's really only step one right? According to another article I read, transferring the licenses also involves calling the Microsoft Clearinghouse etc etc. Here's the article:

I'd like to get this exactly right the first time around because these are production servers. Also, the two old 2003 servers are going to be deleted and wiped once the two new servers are fully functional. So if I install the RDS Licensing role first then transfer the licenses as shown in the article things should work out ok?
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

jimlock720Author Commented:
Hopefully you can provide further clarification on this.
Casey WeaverManaged Services Windows Engineer IIICommented:
I might be a little confused on what you're using the two new servers for. AD is just active directory, if you already have a domain controller on the network (or you're not using active directory at all) then that's why I said you can skip the AD step, you don't need to install AD for this.

To have the servers act as licensing services, at least one of your servers needs to have the RDS licensing role installed and activated on the network. Then yes, you will need to call Microsoft to have them migrate your licenses. This shouldn't be too big of an issue, and if things go wrong you're trial licenses should keep you running long enough to get it straightened out.

Finally, if they are actually logging into the server that's doing the licensing, then yes you need to the host role installed as well.

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
jimlock720Author Commented:
Ahh ok that clears it up a bit. People will be logging into the new server so I'll install the host role too. Neither of the servers involved is on a domain. I think microsoft assume that all servers are on a domain and that's why they include all the AD stuff. It's nice to know I can ignore that. Thanks for the clarification.
Casey WeaverManaged Services Windows Engineer IIICommented:
I think the assignment is being done incorrectly, unless the user needs further clarification.
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.