Hi everyone,
I realise that similar questions have been asked before but I'm still having trouble. I've configured a 2012 R2 RDS farm as follows:
DC.mydomain.local-DC, RD Licensing, SQL for HA
RDCB.mydomain.local - connection broker
RDGW.mydomain.local - RD Gateway & Web Access
RDSH1.mydomain.local - Session Host (Server Desktop)
Externally, cloud.mydomain.co.uk points to the external IP of the Gateway server. I have a public certificate (GoDaddy) with cloud.mydomain.co.uk on it. I've also configured HA for the connection broker using the name cloud.mydomain.co.uk. Internally cloud.mydomain.co.uk resolves to the IP of the connection broker.
The problem is that when I connect to a resource via the RDWeb page, I get a pop-up advising that the name on the certificate doesn't match rdcb.mydomain.local. I had assumed that setting up HA would effectively hide this name from clients (i.e. they'd see cloud.mydomain.co.uk at all stages of the connection). If I ignore the certificate error it works fine but I'm sure there must be a way of getting around this, does anyone have any ideas?
Many thanks,
Matt
Matt Denham | Systems Engineer | BOM Group Ltd.