Deploying new 2016 RDS farm
The following are in place
- 1 Connection broker
- 1 RDHS
- We are not pushing remote apps or allowing outside RDS connections directly to the FARM. So RD Gateway and Web Access is not configured. RDS will be used internally only for now
- Domain\users are added to the RDHS and Connection Broker's remote desktop group
- A DNS record of remote.internal.company with the IP address of the connection broker
When i tested with a standard user account, using the address remote.internal.company, I log directly into the connection broker. I do not get directed to the RDHS. I'm not sure why it's not redirecting me
Am I supposed to have the DNS record point to the RDHS? I'm not sure what I am doing wrong
The issue is that in 2012 and later, RDS introduced the concept of "collections." You need to define the collection in server manager. And then when you connect, the collection name MUST be specified for the connection broker to properly redirect.
And... Drumroll... The GUI does not provide a way to find or specify what collections re in your environment. Microsoft decided to use RDWA for that... Even internally.
If you use RDWA, the dot-RDP files it generates have the collection name property specified and properly formatted and things work. The only other way to do this is to manually save then edit an RDP file in a text editor like notepad. Which gets ugly fast.