Remote Desktop License Server issue with Server 2012 R2

I have a new Server 2012 R2 machine connected to a domain where the DC is a Windows Server 2008 Standard machine.

The new server is not running any server roles other than Remote Desktop. The machine is only running a parts & service database program.  Users typically run Remote Desktop to get onto the 2012 server, and run the database there.

I installed the CALs for Remote Desktop on the Server 2012 machine.  However, a yellow balloon message popping up in the system tray area is:
"Remote Desktop Services will stop running in X days if this computer does not contact at least a valid Server 2008 license server. On the RD connection broker server, use Server Manager to verify or configure licensing settings."

We do have CALs installed on the 2008 server from years ago.  I'm confused because I thought I had correctly gone through the wizard to install the Server 2012 RD CALs on the Server 2012 machine.  I'm not sure how to resolve this.  

Thanks for any help.
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.

Connor HutchinsonCommented:
I installed the CALs for Remote Desktop on the Server 2012 machine

The question is, WHAT are those CALs? Did you purchase totally new 2012 CALs? Or you just use the earlier codes from the 2008 purchase?
DaveWWWAuthor Commented:
They're totally new cals.
Cliff GaliherCommented:
This is most often caused when someone familiar with older versions of TS/RDS goes and installs the roles instead of using the scenario wizard.  You'll need to install the connection broker role if you haven't already and then configure the licensing service via Server Manager once the RDCB is installed.  This includes telling the RDS server the name of the licensing server (no, it doesn't figure this out on its own, even if they are on the same machine), setting the mode (user or device) and creating collections.

2012 is a very different beast when it comes to RDS. The connection broker is now a full warehouse of topology information and without things just don't work right. You can force it manually with regedits or many local group policy settings, but it isn't scalable and can be very fragile. It is far better to stick to the planned deployment strategy of including the RDCB with all deployments. The new scenario wizard does this automatically.

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
DaveWWWAuthor Commented:
Thanks - that was exactly the problem!
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 2008

From novice to tech pro — start learning today.