The VMware Unified Access Gateway (UAG) is a virtual appliance primarily used to allow secure external access to your organization’s applications. These application can be native windows applications, software as a service (SaaS) applications, and desktops. VMware UAG is typically deployed in a DMZ. For more information see: https://docs.vmware.com/en/Unified-Access-Gateway/index.html

Problem

A while ago a customer had an issue with deploying the VMware Unified Access Gateway. The customer imported the OVA and did the necessary config to deploy the OVA. Once installed the OVA didn’t start and came back with a strange error message:

Cannot initialize property ‘gateway2’. Network ‘DAAS-01_BE’ has no associated network protocol profile.

Normally during the import of the OVA, using the Flash-based vSphere Web Client, a network profile is automatically created and the appliance will start without any issues. However, in this case the network profile was somehow not created.

The fix

The fix is quit an easy one. Just add a Network Protocol Profile to the Distributed Virtual Switch (DVS).

How to add a Network Protocol Profile to the DVS

First of all go the VMware vSphere Web Client. Click on the Network view. Select the network to which the UAG is connected. Select Configure. Choose Network Protocol Profile. Click Add.

Give in an appropriate name. For example the same name as the DVS.

Supply the relevant IPv4 configuration.

That’s IT!!! You can now try to redeploy the UAG appliance(s).
P.S. Do not forget do this for all the networks to which the UAG is connected.

I hope this was helpful. If there are any questions just leave a comment and I will try to reply as soon as possible.