Solved

Server 2012 Remote Desktop Services Licensing Issues

Posted on 2015-01-10
3
80 Views
Last Modified: 2015-05-28
I recently joined a Server 2012 Remote Desktop to an SBS domain. I only installed the roles of licensing manager and remote desktop services. Everything works well, however i keep getting a popup telling me i still run on trial licenses and they are expire in xx days. I need to install the remote desktop broker. this is only a small network and should not have to use the broker
Checking the licensing manager i have all green ticks and the licenses are activated. When checking the available licenses it shows as 12  licenses and issued 0 licenses . That would indicate something is not right. Can any of the RDP experts help me out here. Below is a report I ran. Thanks

CAL Usage Report                        
RD License Server:      APPSERV01                  
Report Date:      Sunday, 11 January 2015 2:11:00 PM                  
                        
CAL Version      CAL Type      Installed CALs              CALs in Use      CAL Availability
Windows Server 2012              RDS Per User CAL      12      0      Available
                        
No Per User License has been Issued                        
                        
No Per User License Issuance has failed                        
                        
No Per Device License has been issued
0
Comment
Question by:co_ol
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 58

Expert Comment

by:Cliff Galiher
ID: 40542697
The connection broker is a very important role in 2012 and should always be deployed. Without the RDCB, the only way RDS works, in your case letting RDSH find the licensing server, is through manual registry edits or significant group policy changes. I *strongly* recommend deploying an RDCB and managing the deployment via server manager in 2012.
0
 

Accepted Solution

by:
co_ol earned 0 total points
ID: 40792782
Connection Broker was not required in my particular setup. The licensing server needed to be configured in Group Policy
0
 

Author Closing Comment

by:co_ol
ID: 40800031
Further research allowed me to find the solution myself. After adding the server in group policy settings the licensing went from a trial version to a full version. The licensing check wizard came up with no errors.
0

Featured Post

Free eBook: Backup on AWS

Everything you need to know about backup and disaster recovery with AWS, for FREE!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

What to do when Windows Update is not working correctly? What tools can I use to detect the cause of the malfunction problem? What does this numeric error code mean? These and other questions that you have been asking in the past are answered here (…
A procedure for exporting installed hotfix details of remote computers using powershell
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
This tutorial will walk an individual through the process of installing of Data Protection Manager on a server running Windows Server 2012 R2, including the prerequisites. Microsoft .Net 3.5 is required. To install this feature, go to Server Manager…

732 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question