-
1. Re: UAG 3.2 install via Powershell not using staticv4 address
a.p. Jan 30, 2018 12:31 PM (in response to hammord)It works perfectly for me.
Can you confirm that you create a Network Protocol Profile, and set all of the three below mentioned .ini entries to the same network name?
sample:
netInternet=DMZ
netManagementNetwork=DMZ
netBackendNetwork=DMZ
André
-
2. Re: UAG 3.2 install via Powershell not using staticv4 address
nettech1 Apr 21, 2018 10:27 AM (in response to hammord)Did you create Network Profiles in your vCenter to match the network labels in your answer file?
-
3. Re: UAG 3.2 install via Powershell not using staticv4 address
markbenson Mar 13, 2019 4:03 AM (in response to hammord)hammord - is this resolved now? The issue will be with your .ini file.
If you still have the issue, attach your .ini file with ip0= entry etc, and someone will help.
-
4. Re: UAG 3.2 install via Powershell not using staticv4 address
hammord May 10, 2019 3:18 PM (in response to markbenson)I tried again using the 3.5 script and this time it prompted me that I was missing netmask0=. I added the netmask0 and the script worked flawlessly!
-
5. Re: UAG 3.2 install via Powershell not using staticv4 address
BenFB May 14, 2019 9:55 AM (in response to hammord)Yes, that is a required field.
Using PowerShell to Deploy VMware Unified Access Gateway
Deploying Unified Access Gateway Without Network Protocol Profile (NPP)
As of UAG 3.3 the Network Protocol Profile (NPP) requirement has been removed.
Release Notes for VMware Unified Access Gateway 3.3
- Removed dependency on Network Protocol Profile (NPP) - It is no longer necessary to set up an NPP or an IP Pool to deploy Unified Access Gateway. Instead, the IPv4 netmask, IPv6 prefix, and default gateway are specified when Unified Access Gateway is deployed. This helps with improved vSphere deployment flexibility.