I have a problem that is plaguing us and wonder if anyone here is an RD Services expert.
We have Two Server 2012 R2 RDP Servers. The setup is this:
Server 1:
RD Connection Broker
RD Session Host
RDP1.domain.local
External Host name: rdp.mydomain.com (NAT through firewall)
Server 2:
RD Connection Host
RDP2.domain.local
No external ip.
On Both servers we put our wildcard certificate: *.mydomain.com.
When we connect using https://rdp.mydomain.com/RDWeb we get the prompt that *.mydomain.com certificate doesn't match rdp(1|2).domain.local do you
want to continue or not.
When continuing, it takes a full 25-30 seconds hanging on "Securing remote connection" If we're redirected to the RDP2 server by the connection
broker then the delay is nearly THREE MINUTES.
I know it has to do with this certificate mis-match. but I don't know how to get over it. I can't create a self-signed certificate for domain.local
because that would not work for our clients at all. I can't get an externally signed domain.local certificate since it's an internal domain.
I tried once using Set-RDPublishedName to set the published name on the server but it caused more problems (I can't remember now what they were.)
How do I get over this problem?