You can use VMWare's OVFTool to convert from OVF to OVA and vice-versa.
install-path\ovftool.exe C:\path\source.ovf C:\path\dest.ova
install-path\ovftool.exe C:\path\source.ova C:\path\dest.ovf
If the webclient is letting you down, you can also use PowerCLI to expand datastores.
First, as usual, expand the volume on the storage level. Then, fire up PowerCLI, log on to the vCenter/host and run the following script, replacing the name of the datastore you wish to expand:
$name = 'Datastore1' $datastore = Get-Datastore $name $esxi = Get-View -Id ($Datastore.ExtensionData.Host | Select -Last 1 | Select -ExpandProperty Key) $datastoreSystem = Get-View -Id $esxi.ConfigManager.DatastoreSystem $expandOptions = $datastoreSystem.QueryVmfsDatastoreExpandOptions($datastore.ExtensionData.MoRef) $datastoreSystem.ExpandVmfsDatastore($datastore.ExtensionData.MoRef,$expandOptions.spec)
Not straightforward to find on the website (but with a little bit of Googling, here it is): an overview of the system requirements for VMware Fusion. All versions are listed:
A very nice article explaining how to migrate from an external Platform Service Controller to an embedded one:
A note about versioning: use the same version of the converge tool as the version of your vCenter and PSC. Otherwise the converge will most likely fail (as it did when using 6.7 tool on a 6.5 environment).
If for some reason the deployment of the VMWare vConverter agent fails, you can also copy the installer to the machine you wish to P2V and manually install it.
On the machine VMWare vConverter is installed, navigate to the location where it's installed (by default: C:\Program Files (x86)\VMware\VMware vCenter Converter Standalone), and look for the file VMware-Converter-Agent.exe. Copy over this file over to the target machine and run it to install the agent. Accept the defaults, including the TCP-port (unless your setup requires you to change it). Once finished, a service will have been installed and you will be able to connect to it using vConverter.
Found this article online about how vSphere virtualizes NUMA and how this is relevant to the configuration of vCPUs in your VMs:
In the event of migrating your old vCenter Server to a new version (or from Windows to the appliance), it may become necessary to first clear out old historical data. Not only will this speed up the migration process considerably, it will also prevent certain issues which may block the migration from completing successfully.
VMWare provided a KB with database scripts which allow you to selectively purge historical data and decreasing the database size: KB 2110031.