1 person found this helpful
I've had a similar issue with 6.5d. As a workaround, you can either deploy the OVF/OVA directly to the host (https://<HostIPorHostName>/ui), or use the OVF Tool CLI, documented here... OVF Tool Documentation.
ex> ovftool -ds=storage1 -n=myVM C:\testVM.ovf vi://user1:firstname.lastname@example.org/?ip=18.104.22.168
I hope this helps... though VMware really does need to fix this issue ASAP, especially with everything moving towards virtual appliances.
Thanks I did end up deploying using the host and this was successful. Lots of posts regarding this issue so hopefully they will resolve soon.