The other day I was rebuilding my lab using William Lam’s vGhetto vSphere Automated Lab Deployment script for vSphere 6.5. In the past I have run the 6.0 script successfully. As part of the script, there is an OVA of a host profile that William has made for the deployment, this is used for the configuration of the host.
This particular time I came across an error right after starting the process and immediately after connecting to the nesting host. It was a bit of a strange error, pointing to the Import-vApp cmdlet but also saying, “Invalid URI: The hostname could not be parsed,” which sounded as though to be a DNS issue, I spent a little bit of time going through my DNS settings, making sure that the computer from which I was running the script was able to resolve the hostname. I moved off my MacBook using PowerCLI Core and tested from my Windows machine using PowerCLI 10.0, and received the same error.
I did some quick research and found nothing related to the specific error message and started to look at it piece by piece. I decided to pull apart the OVA file and try and run just the OVF – SUCCESS! There appears to be an issue with the OVA and the Import-vApp cmdlet in both PowerCLI Core and PowerCLI 10.0. I am yet to test the OVA in vSphere via the WebClient, but I suspect it may work as it should.
To pull apart the OVA, I recommend using 7ZIP and opening the .ova file and copy/paste the content.
- Download and Install 7ZIP
- Relaunch explorer
- right click OVA file -> 7ZIP -> extract to /<foldername>
- check for the VMDK, OVF and description file are all present
- Change your ESXI $NestedESXiApplianceOVA= to the .ovf file
- rerun script.