Share via

RDWeb HTML5 client on On-Prem Deployment: Change internal resource URLs to public ones.

Thomas Ward 10 Reputation points
2024-06-06T13:20:01.4866667+00:00

On our RDWeb HTML5 deployment per https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/remote-deskt... 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 the system is using for the logon page, etc. 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?

Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,376 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Karlie Weng 16,076 Reputation points Microsoft Vendor
    2024-06-07T06:02:00.6733333+00:00

    Hello,

    You can specify a specific Gateway server in your rds deployment. (Server manager - collection - properties - rd gateway.)

    If the Answer is helpful, please click Accept Answer and upvote it.