Hi,
I just set up a new RDS deployment scenario with two servers.
Each servers have this role : RDWeb, RD Broker, RD Gateway & RD Session Host
Licensing server and SQL Server is on another server, I switch from the internal database to the SQL database for HA Broker scenario.
HA work great, I can turn off one of the two servers, users can reconnect on the second (I use a Round Robin DNS for remote.mydomain.com and use a split DNS for the mydomain.com because of an internal domain in .local)
I have configured all the role to use the public FQDN name (remote.mydomain.com) and I set up a public certificate (mono-CN).
By using the Set-RDPpublishedName.ps1 script (https://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80) all works perfectly, include the SSO which is native
with 2012.
The issue is :
- When users pointing to the server1 IP (remember that I use Round Robin DNS), I don't have any warning ; from internal or external network the users just click on the published App and it just works.
- When users pointing to the server2 IP, the prompt you've got the first time (see the screenshot below) says all is pointing to remote.mydomain.com but after this prompt I have a certificate Warning because the broker use internal name of server2.mydomain.local for published App. This is not critical because the user can validate the warning and the publishedApp starts normally.
If I try to use the Set-RDPpublishedName.ps1 script on server2, I've got an error which says I don't have any RDP deployment on this server (server2 was installed from Server Manager of Server1).
Is anyone have a solution for me for force server2 to use my FQDN name instead of the local name ?
Thank you a lot !
SunbeamTech