The variables are set to appropriate string values for each of these items.
When I adjust these values manually in a PowerCLI session, I am able to confirm the correct values are set in the OVF Config. However, when the appliance is imported into vCenter, the vApp options for the Networking show blank rather than the values that were set here. I noticed the keys shown on the vApp are different than the ones listed above. Here are the keys from the vApp:
When I tried adjusting to use these keys to configure the OVF, errors shown based on incorrect keys.
What am I missing? There are no issues when you deploy the OVA manually in vCenter. Is anyone else having this issue?
So, interesting discovery. The example above used New-VM to import the vApp from the Content Library. The one here used Import-VApp and pulled the OVA from the current system. As you can see, the OVF Config settings carried fine through the VApp creation. Is there anyway to import a VApp from a Content Library and retain the settings or is there something I'm missing between the New-VM and Import-VApp functions?
I'm new to working these scripts and going through the Command Reference was where I found the New-VM option to import with an OVF Config. Why would the OVF Config be ignoring the settings like this in one instance but not the other?