When a node is deployed to have Internet-enabled desktops, you must create a CNAME record in your DNS server that maps the fully qualified domain name (FQDN) that was specified in the deployment wizard to the node's load balancer's auto-generated public FQDN.
About this task
When a node is deployed with the Internet Enabled Desktops option set to Yes (the default), the deployed Unified Access Gateway is configured with a load balancer IP address that has an auto-generated public FQDN in the form
vmw-hcs-nodeID-uag.region.cloudapp.azure.com, where nodeID is the node's UUID and region is the Microsoft Azure region where the node is located.
In the deployment wizard, you provided:
Your FQDN (for example,
ourApps.ourOrg.example.com). This FQDN is the one which your end users use to access their desktops.
An SSL certificate that is associated with that FQDN and which is signed by a trusted certificate authority.
Your DNS server must map those two FQDNs. When the addresses are mapped, your end users can enter your provided FQDN as the server address in the Horizon Client or use with HTML Access to access their desktops.
Use these steps to locate a node's load balancer FQDN.
The node must be successfully deployed into your Microsoft Azure environment, according to the steps in Getting Started with VMware Horizon Cloud Service on Microsoft Azure.
- In the Administration Console, navigate to , and click on the node to open its details page.
- On the Summary tab, scroll down to the information section labeled Unified Access Gateway.
- Locate the Load Balancer FQDN field and copy its value.
The value is the auto-generated public FQDN in the form
vmw-hcs-nodeID-uag.region.cloudapp.azure.com, where region is the Microsoft Azure region and where nodeID is the node's UUID
- In your DNS server, map that load balancer FQDN to the one that was provided when the node was deployed