So this was originally posted under the Workspace ONE discussions since it was for the Workspace ONE Access appliance. However, after a bit of testing, it looks to be more of a PowerCLI handling of OVF Configurations between New-VM and Import-VApp. The original post is here:
I'm trying to import a VApp using a PowerCLI script that can either take a file location on the local system or a VApp that has been saved to a Content Library. The Import-VApp line works as expected once you configure the OVF Configuration and the resulting VM has the following settings configured:
However, when I use New-VM to pull the same OVA stored in a Content Library, none of the associated network configuration settings survive the import as shown here:
It's interesting that the Timezone setting and host name configurations do make it through. What is going on between how these two commands handle the VApp import?