Click the PowerShell icon located on the Windows task bar.

As the script starts, a couple of questions ask you to provide the following information.

1. Enter cd 'C:\Users\Administrator\Documents\HOL\Unified Access Gateway' to navigate to the directory with the Unified Access Gateway deployment scripts.  Press ENTER.
2. Enter .\uagdeploy.ps1 .\uag-HA1.ini VMware1! VMware1! false false no  Press ENTER.

The first VMware1! is the root password for the Unified Access Gateway appliance.
The second VMware1! is the admin password for the REST API management access.
The first false is to NOT skip the validation of signature and certificate.
The second false is to NOT skip SSL verification for the vSphere connection.
The no is to not join the VMware CEIP program.

The deployment will begin and you can follow the progress in the same window or in your vSphere Web Client, which you opened at the beginning of this set of exercises.

After successfully finalizing the deployment, the script will automatically power on the UAG-HA1 VM.

The Received IP address presented by the script log is a temporary IP. The final IPs for NIC 1 and NIC2 are assigned to the Unified Access Gateway appliance during the first boot. You can return to the vSphere Web Client to validate that as described in the next step.

Now, you will deploy the second appliance, called UAG-HA2, passing the uag-HA2.ini file as parameter.

1. Enter .\uagdeploy.ps1 .\uag-HA2.ini VMware1! VMware1! false false no   Press ENTER.

The first VMware1! is the root password for the Unified Access Gateway appliance.
The second VMware1! is the admin password for the REST API management access.
The first false is to NOT skip the validation of signature and certificate.
The second false is to NOT skip SSL verification for the vSphere connection.
The no is to not join the VMware CEIP program.

The deployment starts and you can follow the progress on the same window or on your vSphere Web Client, which you opened at the beginning of this set of exercises.

1. Click VM and Templates.
2. Expand RegionA01.
3. Click UAG-HA1.
4. Click View all 2 IP addresses.  Note the IP Addresses displayed for the VM.

Repeat steps #3 and #4 for UAG-HA2, the IP addresses for this appliance should be different from UAG-HA1.

Note: If the Unified Access Gateway appliance does not finalize the configuration during the first startup, you receive an error message from vSphere Web Client. If that happens, wait for the appliance to finalize, and refresh the entire Google Chrome browser.

1. Click the New Tab button to open a new tab.
2. Browse to https://uag-ha1-intranet.corp.local:9443/admin or click the UAG Internal Admin Console bookmark.
3. Enter admin for the username.
4. Enter VMware1! for the password (created for the Admin API in the Deploy OVF Wizard).
5. Click Login.
6. Repeat steps 1-5, opening a new tab and log in on the second appliance using the following URL https://uag-ha2-intranet.corp.local:9443/admin

A successful login redirects you to the following screen on both Appliances, where you can import settings or manually configure the Unified Access Gateway appliance individually.

1. Click Select under Configure Manually in the UAG-HA1 administration console.
2. Click the tab to return to the UAG-HA2 administration console.
3. Click Select under Configure Manually in the UAG-HA2 administration console.