13 thoughts on “PowerCLI: Import-vApp OVA: Hostname cannot be parsed.

  1. Thanks a lot for this! I was fighting with the script for hours!
    This is the power of #vCommunity

    1. Hi Kannan,
      Step 5 is to update the William Lam deployment script mentioned in the first paragraph, as the line $NestedESXiApplianceOVA= from the default script points to the ova package and once you unzip the ova and present the .ovf and supporting files, you will need to redirect that cmdlet to look at the .ovf
      In regards to 6, it just means, run the script once you’ve updated the file location to point to the ovf file.
      Hope that explains it better.

  2. Thank you, this post just saved me a couple hours of tearing my hair out trying to figure out why it wasn’t deploying.

  3. areyou kidding me!! this fixed it (using the vghetto nested ps script)! thank you SO MUCH, i would never have though to try this, even though i saw other pages/posts saying there are problems with OVA files and powerCLI vm-deply .
    really, thank you for taking the time to write this post!

Leave a Reply

Your email address will not be published. Required fields are marked *