If your UAGs are going into a DMZ there’s a chance that they wont be able to resolve internal domain names, (you can specify internal IP addresses of course). Take a copy of the Thumbprint, from the Horizon Connection Server you will be pointing the UAG at, keep it handy you will need it in a minute. To allow users to access Horizon machines externally, you need to ensure you have granted Remote Access Rights in Horizon Administrator, Note: This is in addition to any Entitlements you have already setup for the machine pools. Select the edition to deploy (based on your licence) > Next. ![]() Untick CEIP > Set the admin, (needed for the web front end), and root (needed for console login) passwords. Select the storage you want to deploy the appliance to > Next.Ĭonfusingly, (as we have picked single NIC?) set them all to the correct port group > Next.Ĭomplete the DNS and IP settings > Give the appliance a name > scroll down. I’m deploying into a DMZ so there will be no shortcutting the firewall! > Single NIC > Next. Pick where you want to deploy the appliance (Cluster etc.) > Next. Select your Datacenter and optionally folder > Next. Navigate to, and select the OVA file you have downloaded from VMware > Next. I’ve covered deploying OVA files before, but essentially download the OVA, and within your vSphere client select deploy OVF template. Her I’m simply deploying one internal Horizon Connection Server, and one VMware UAG in my DMZ. ![]() You can deploy multiple UAGs and have them behind a load balancer, or point individual UAGs to separate Horizon Connection servers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |