Remote Desktop Services - Certificate Confusion

[J_Worth]

Hello Everyone!

 

We are trying to setup an RDS Farm and are confused with what certificates we need to use.

 

Our setup is as follows:

 

Server 1 - Internet Facing (remote.domain.com (joined to domain.local))

- RD Gateway

- RD Web Access

- RD Licensing

- RD Connection Broker

 

Server 2 - Non-Internet Facing (Session1.domain.local)

- RD Session Host

 

Server 3 - Non-Internet Facing (Session2.domain.local)

- RD Session Host

 

The confusion lies in signing the remoteApps. As they reside on a server that has a .local domain how can I get these to be signed by a Public Certification Authority?

 

We are currently looking a purchasing a Wilcard certificate - *.domain.com and obviously this cannot be used for the session hosts.

 

So my final question is how can I sign these remoteApps so that they can be used externally without any issues.

 

I hope that the above makes sense!

 

Thanks in advance.

 

J.Worth

[Guest Guest]

You can sign the hosts with the wildcard cert, RD doesn't care that they have the wrong domain name.

 

On your DNS server create a zone for domain.com and add them in there as session1.domain.com session2.domain.com and both session1 and 2 as farm.domain.com

Now x.domain.com and x.domain.local are the same hosts.

Point your gateway to farm.domain.com and configure any options on the RD host using .domain.com in place of .domain.local

 

Now all PCs in the chain look like they are called x.domain.com regardless of whether they are really .local

Edited July 10, 2012 by Guest

[J_Worth]

Hello,

 

Thanks for your quick reply. In the back of my mind this is what I would have done, but just wanted to make sure it was the right way to proceed with this!

 

Thanks again!