Hi there,
I have set up a test environment with the following:
1 RD Gateway
1 RD Web
1 RD Broker
2 RD Session Hosts
All servers are running Windows Server 2012 R2.
The domain is: exampledomain.local
The ssl cert is a wildcard for *.exampledomain.net
For local domain PC's I've created a GPO and set the SHA1 thubprint and also credential delegation settings.
1) For domain joined PCs, if I open up a web page and browse to the RDWEB website, I still have to enter the login details once. The solution for this seems to be to edit the RDweb page to use Windows authentication (http://anandthearchitect.com/2014/01/20/rds-2012-r2single-sign-on-using-windows-authentication-for-rdweb-page/). One possible consequence of doing this seems to be that you have to specify that you're accessing the site from a private connection. This would pose a security risk when accessing from a public computer. Is there any way around this or any other way of doing this?
2) For external PCs connecting through the gateway, I get a certificate prompt stating that the cert was issued to *.exampledomain.net but the server it is connecting to is broker.exampledomain.local. One possible solution I've found on the web(https://msfreaks.wordpress.com/2013/12/23/windows-2012-r2-remote-desktop-services-part-2/) is to create a high availability RDS broker farm, give that the name broker.exampledomain.net, and create a DNS entry for it (same as the Broker). However, I've just come across this script: https://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80 that seems to indicate it would do the same. If this is the case, what would happen in the case of multiple brokers (high availability)? Would I need to set the farm name and then run the script on each broker or is just setting the farm name enough?
3) Firewall ports: on the external firewall, do I need to open port 3389 UDP to the RD Gateway server or is just 443 enough?
Thanks,
HA