When trying to start the “Deploy OVF Template” wizard from vSphere Web Client 6.5, you may meet this error:
This version of vCenter Server does not support Deploy OVF Template using this version of vSphere Web Client. To Deploy OVF Template, login with version 220.127.116.11 of vSphere Web Client.
This error was reported for earlier versions of vSphere 6.5 and VMware released this KB article. VMware added a fix in VMware vCenter Server Appliance 6.5 b.
The issue reappeared in some cases after a new upgrade to the latest vSphere 6.5 Update 1 and it’s treated in the second KB article.
Into the Lab
If you see this error into a lab where you are running under severe resources constraints, I could have an easier resolution for you.
Normally, when you do run in an environment where you cry for every resource you spend (such as running nested ESXi in your home lab), you try to squeeze every resources out of your vCenter Server Appliance. Even the tiny VCSA instance will still require a whooping 10GB of RAM.
In such cases you were already looking for every possible VCSA service that you could disable. Chances are that you will find Content Library service in the list of your stopped services.
Go to Home -> Administration -> System Configuration -> Objects -> Services and filter by “Content Library”. You could be seeing something similar
Notice State listed as Stopped and Startup Type listed as Manual. You have just found the root cause of the OVF error. Start the Content Library service (and change Startup Type to Automatic if you need this feature always on).
As soon as the service State is Running, you can resume your OVF deployment.
Happy OVF template deploying!