Running VMware Unified Access Gateway on Hyper-V

Ok okkkkkk, I know that could be weird at first sight but I had a request from a customer to assist in the deployment of UAG 3.9 on Hyper-V in a “Dual DMZ” configuration.

The Back End UAG is deployed on vSphere but the the front-end should run on the DMZ hypervisors who are…. Windows 2019 Core / Hyper-V

So when we look at the files required to perform this installation we need to download 2 files :

  • Unifed Access Gateway (UAG) 3.9 PowerShell scripts to get all scripts to deploy the appliance
  • Unifed Access Gateway (UAG) 3.9 for Microsoft Azure to have .vhd file so Hyper-V disk format file.

Trying to deploy the .vhd with the script will failed,so the first thing to do is to convert the the .vhd to .vhdx using PowerShell :

And now we can edit the .ini file to deploy the Appliance as a Reverse Proxy for Horizon :

# UAG virtual appliance unique name (between 1 and 32 characters).
# If name is not specified, the script will prompt for it.
# Full path filename of the UAG Hyper-V .vhdx virtual machine image
# The file can be obtained from VMware
# Hyper-V datastore folder
ds=E:\Hyper-V\Virtual Hard Disks
# Hyper-V Network names.



# vSphere Network names. For pre 3.3 UAG versions, a vSphere Network Protocol Profile (NPP) must be associated with every referenced network name. This specifies
# network settings such as IPv4 subnet mask, gateway etc. UAG 3.3 and newer no longer uses NPPs and so for static IPv4 addresses a netmask0, netmask1 and netmask2
# value must be specified for each NIC. Normally a defaultGateway setting is also required.


proxyDestinationUrl=https://<IP or FQDN of Back End UAG/LTM>

Once edited for our environment we can launch the deployment :

And check at the end that everything’s ok :

You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *