Hi,
I'm setting up the following in my lab to test before a production deployment:
RDSH01 - RD Session Host 1
RDSH02 - RD Session Host 2
RDSH03 - RD Session Host 3
RDSBG - RD Connection Broker
Everything seems to work great if I point my RDP client at one of the session hosts via a DNS round robin, it redirects me to whatever server has my disconnected sessions on and new sessions get put on servers with the least connections, great, however, I have the following questions...
- I've read on other threads that I should be pointing my RDP client at the Broker, not at a Round Robin DNS containing the Session hosts. That said, its working just connecting to the hosts and redirecting and load balancing accordingly. Is this the right approach? (I've got RDS.domain.local pointing at RDSH01, RDSH02 and RDSH03)
- I'm currently using a Self Signed Cert for RDS.domain.local which is great when initially connecting, however when I get redirected to another host it comes up with a warning for eg. RDSH02.domain.local as the Session Hosts have no certs on them.
From what I've read, you don't need to put certs on every Session Host as the connection goes via the broker but when I connect to the broker I get told I'm not authorised, I can only connect to the Session Hosts.
What am I missing here?
Many thanks,
Dave