On our RDWeb HTML5 deployment per https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/remote-desktop-web-client-admin#how-to-pre-configure-settings-for-remote-desktop-web-client-users we have set up the client.

However, while our RDGateway and other components are all set to ‘connect.example.com’ for the URL and server name to use, the RDWeb client is defaulting to rdgateway01.internalonly.example.com which isn’t usable from the outside.  As such, connections that aren’t on our internal VPN or internal network are failing.

With the old (and I mean REALLY old) preview versions, this URL was the correct ‘connect.example.com’ settings.  Since the new version, however, it looks like there’s no way to configure this.

Is there any way to tell RDWeb to use the proper URL publicly rather than use the internal FQDN that is NOT set in the RD Gateway and RD Broker systems?

​On our RDWeb HTML5 deployment per https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/remote-desktop-web-client-admin#how-to-pre-configure-settings-for-remote-desktop-web-client-users we have set up the client. However, while our RDGateway and other components are all set to ‘connect.example.com’ for the URL and server name to use, the RDWeb client is defaulting to rdgateway01.internalonly.example.com which isn’t usable from the outside.  As such, connections that aren’t on our internal VPN or internal network are failing. With the old (and I mean REALLY old) preview versions, this URL was the correct ‘connect.example.com’ settings.  Since the new version, however, it looks like there’s no way to configure this. Is there any way to tell RDWeb to use the proper URL publicly rather than use the internal FQDN that is NOT set in the RD Gateway and RD Broker systems?  Read More

​