I currently don't have access to a vCenter 6.5 instance, so this is more a guess.
Which of the client do you use, the flash based client, or the HTML5 client?
OVF Support is not yet integrated in HTML 5 client
Hello, same issue in our environment. Does anybody solve that?
We also have this problem, but only on 1 of 2 different vCenters. Both of our vCenters are running the same version. The one that works, was upgraded from a Windows vCenter 6.0. The other was upgraded form a VSCA 6.0. A workaround until the problem is solved, is to use the Windows client connected directly to a host.
I'm am new to virtualisation and VMWare in general.
I also stumbled uppon this issue, while testing with the trial version.
I was planning on buying the "VMware vSphere Essentials Kit" for a customer of mine, but since I've stumbled uppon this issue, I'm not really sure about it anymore.
Unless,... when I do buy this can I download the "vcenter appliance 6.0" instead of the 6.5 ?
I was gonna try that, but the trial only allows me to download the 6.5
(the work around doesn't really work for me, since when I'm trying to do that the client says my esxi is controlled by a vcenter server and doesn't allow me to do it)
Would really appreciate it if someone could answer me this.
Thanks in advance.
There's now a resolution posted which is to upgrade VCSA to 6.5.0b (184.108.40.20600 Build Number 5178943).
My VCSA is now: 220.127.116.1100 Build Number 5178943
I still can't export OVF template. Message remains: "This version of vCenter Server does not support Export OVF Template using this version of vSphere Web Client. To Export OVF Template, login with version 18.104.22.168 of vSphere Web Client."
OVF is broken in vSphere 6.5
If the update to 6.5b didn't fix the issue, you can deploy the OVF manually using the OVFTool. This article has some instructions on the process. The parameters may be different, but the OVFTool should get the job done.
any resolution for this problem?
I have upgrade my Vcenter on version 6.5 update 1 5973321, but this problem still appears
because of that i can't deploy vmware vreplication appliance
2 people found this helpful
New KB is published with resolution.
Please follow the steps mentioned in the KB in order to correct the behavior.