Have to build an easy RDS 2012 R2 Farm:
- 1 Session Host
- 1 Connection Broker, combined with the RDS Web Site Role
- 1 RDS GW in the DMZ
The Setup was easy, and it works very fast, but with a lot of annoying prompts for the user (certificate mismatch, two logon prompts...).
But what a pain it is to make the farm work right! The best artcle we found is http://www.rdsgurus.com/ssl-certificates/windows-2012-r2-how-to-create-a-mostly-seamless-logon-experience-for-your-remote-desktop-services-environment/. Microft obviousely
forgot to write any documentation about 2012 RDS. There is nearly nothing in Technet and MS Library. The only thing available from Microsoft are some Wiki articles.
From what I have read, public certificates have to be used on all systems except on the session hosts, and the "internal names" have to changed to external names.
We tryed to change the published FQDN Name with the powershell command Set-RDClientAccessName, but this command does not work when there is only one Session Broker server installed. For this purpose, we found another PS Script from Microsoft on https://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80.
This script worked and the FQDN name is changed, but the connection from the client to the RDS farm doesn't work at all anymore: We are getting an error message that access is denied due to "authorization policies". We have never modified the default
client and ressource access policies on the RD Gateway.
Thank you in advance for any advice regarding these problems.
Franz