• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 109
  • Last Modified:

RDS Licensing on Server 2012

We have recently installed a MS 2012 Domain Controller. The customer has a 2008 R2 Terminal Server and requires a license server. We installed RDS Licensing on the 2012 DC and it refuses to activate in the Server Manger Console. Additionally a balloon notification appears when logging onto the DC.

"remote desktop services will stop working in 119 days.."

We have only installed 2 services under RDS, Remote Desktop Session Host and Remote Desktop Licensing. Under RD Licensing Manager we have successfully activated the license Server and installed some TS per User Licenses. In Licensing Diagnoser the License mode is "not configured". And Licenses available for clients is "0".

Is there a way to configure the Session Host Controller or do we have to install more services under RDS Role? We are aware that the full RDS role cannot be installed on the 2012 DC server, but is it possible to have a RDS License server on the DC?
1
KCITS
Asked:
KCITS
  • 2
1 Solution
 
Cliff GaliherCommented:
You've got multiple things going on here:

First, the balloon popping up on the DC when you log in tells me that you (perhaps accidentally, if I've read your intention properly) installed RDSH on the DC, not just RDLicensing.  Otherwise the DC wouldn't be complaining about RDS expiring.

The second issue is getting your RDS server to get licenses. You can configure this via group policy or you can configure this on the 2008 R2 RDS server itself using the terminal services configuration MMC. You *cannot* configure this on your 2012 server.  You'll have to specify the licensing server name and the type of licensing mode you want to use.  Once the mode is set, it then knows which type of license to check for against the licensing server. Until you set the mode, the available licenses is rightfully 0. So that is (for now) expected behavior.

As to your final question, you can have the RDLicensing role on the DC, but like any role on a DC, you assume an increased footprint vulnerable for attack. In most deployments, it isn't a topology I'd recommend. Starting with 2008, the preferred way to distribute TS/RDS settings to users has been with RDWeb (and optionally RDGateway) so you usually will have a two-server RDS deployment anyways. The RDWeb, RDGateway, and RDLicensing role can all coexist, keeping both your RDSH and DC's pristine as intended.  If at all possible, that's what I'd recommend. This topology is clearly the way Microsoft is architecting RDS moving forward, as each new version from 2008 to 2012 R2 has refined this methodology and has increasingly dropped settings for other topologies.  If you want to future-proof a bit, *now* is the time to rethink your architecture.
0
 
KCITSAuthor Commented:
Hi Cliff

Thank you for your detailed answer, considering your first comment, Yes we have installed RDSH. I s it possible just to remove this role while leaving the RD Licensing on the server?
0
 
Cliff GaliherCommented:
Yes.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now