Changing the published name of an RDP collection breaks new connections

I am trying to get rid of the error notification below:

I have the following configuration:

• Server 2016 w/ latest updates
• single server handling RD Web, RD Gateway, RD Connection broker
• 3 RD Session host servers
• SSL certificate for remote.example.com
• Created an internal DNS record that points remote.example.com to RDG.example.LOCAL

I have tried doing the following, but it always gives me the error below when I try to connect:

• Change the RD Published Name
• https://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80
• Add an RDP property for alternate full address
• https://serverfault.com/questions/524092/rds-rdweb-and-remoteapp-how-to-use-public-certificate-for-launching-apps-on-s

Any input on what I can do to resolve this?

Andy Morales (Blog)