This error can be resolved by using vCenter server to do the deployment of the OVA file.
vCenter server is listed as a prerequisite in the documentation:
If vCenter server is not available then the following workaround could be used:
Extract the OVA to a directory.
Delete the manifest file from the directory (vtdm-appliance.mf).
Edit the OVF file (vtdm-appliance.ovf> to delete the property elements from the Product section element.
Deploy using the OVF file.
Once deployed and booted login as root on the console in vSphere Client using the default password and change the properties that you need to (the root password being one):
cd to /usr/local/etc/default
Change the properties that you need to; for example:
Save the changes
Restart the appliance: shutdown -r now
Once restarted you can login again with your new root password if needed.
Do not change the apiUser or shareUser values - they are in the file for future enhancements.
With the hostname not being set explicitly during deployment, a name is generated. If you are concerned about collisions, or need static IP... then disable the network adapter before booting the appliance, then do the above but instead of restarting use power off, then enable the adapter and boot again.