Importing Unified Access Gateway Image as an Amazon Machine Image (AMI).Deploying Unified Access Gateway on Amazon Web Services.Deploying the Unified Access Gateway Appliance.Deploying Unified Access Gateway on vSphere with Two NICs Through PowerShell.Deploying Unified Access Gateway with vSphere.Deploying Unified Access Gateway on vSphere with One NIC Through vSphere Web Client.Unified Access Gateway OVA and PowerShell Files.Once the Connetion Server is reacheable from the Unified Access Gateway, remote users can connect the corporate Horizon infrastructure. This time the Connection Server is reachable since the DNS name is resolved with no issues and all components are marked as green. When the appliance has booted, login to the UAG appliance and check the Connection Server connectivity. Now Reboot the appliance to apply the changes. When done save the file with the :wq command. Uncomment (remove the #) the Domains line and specify your DNS Search Domain (in the example nolabnoparty.local). Using a tool like PuTTY, SSH the UAG by entering the root credentials.Įdit the file /etc/systemd/nf with the vi command. If you want to use the FQDN instead, you have to edit the /etc/systemd/nf file in the UAG appliance. modify an entry in the nf file in the UAG applianceĪn easy solution to allow the Unified Access Gateway appliance to reach the Connection Servers can be achieved by entering the IP Address instead of the FQDN in the Connection Server URL field.the use of the IP Address instead of FQDN.To fix this issue, there two possible workaround: This problem occurs when the FQDN of your Connetion Server is a. local domain.ĭespite the correct DNS and Search suffix settings configured, once the appliance is rebooted after the deployment the Horizon Destination Server (Connection Server) is unreacheable from the UAG appliance. Once the Unified Access Gateway (UAG) has been deployed and configured, the VMware UAG DNS is not able to name resolve the Connection Servers if the FQDN includes the.
0 kommentar(er)
