![](/uploads/1/2/7/1/127150778/348362998.jpg)
Sep 30, 2017 I seem to have issues deploying a 21GB OVA to vCenter using either the vSphere Web Client or the vSphere Client (HTML5). It seems to do well until it gets to 50%, then it stalls and sits there indefinitely with no errors. This is same result no matter which build of 6.5 I have used. I have tried multiple browsers.
VMware plans to deprecate the Flash-based vSphere Web Client with the next numbered release (not update release) of vSphere. The next version of vSphere will be the terminal release for which vSphere Web Client will be available.
The vSphere GUIs, including the vSphere Web Client and HTML5-based vSphere Client, are tools that are used every day by IT to manage the operation of their virtual data center. VMware is constantly striving to make these tools performant and easy to use. However, with the vSphere Web Client, customers were frustrated because it was based on Flash technology that resulted in less than ideal performance and constant update requirements. Additionally, Adobe has recently announced plans to deprecate Flash.
It has always been VMware’s intention to eventually replace the vSphere Web Client with a modern GUI administration tool. The HTML5-based vSphere Client is that worthy successor. The vSphere Client was introduced first in the Fling, then supported with vSphere 6.5 and has now been in customer hands for 1.5 years and production tested for over 9 months. Since its introduction, the vSphere Client has received overwhelmingly positive responses from the vSphere community and customer base. Customers have said things like:
“Thank you thank you thank you thank you thank you thank you thank you thank you thank … for creating this [vSphere Client] interface, my god it is nice to use :-)”
“If VMware can hold its various teams to the high standard set by the [vSphere Client], it should have nothing to worry about for years to come.”
With the recently released vSphere 6.5 Update 1, the vSphere Client got even better and is now able to support most of the frequently performed operations. With each iteration of the vSphere Client additional improvements and functionality are being added. By the time the vSphere Web Client is deprecated, the vSphere Client will be full featured but with significantly better responsiveness and usability. You will not be left with an incomplete toolset!
The vSphere Client will be the primary GUI administration tool for vSphere environments starting in the next release. Customers should start transitioning over to the vSphere Client if they have not already done so as the vSphere Web Client will no longer be available after the next vSphere release.
We post this blog now to give customers a fair warning and ample time to prepare for the eventual vSphere Web Client deprecation. This also gives customers a chance to express their concerns both online and at VMworld. At VMworld, customers will have many opportunities to learn more about the vSphere Client in various breakout sessions, labs, and of course by speaking with the experts in the Solutions Exchange.
![Ova Vmware Vsphere Client Ova Vmware Vsphere Client](/uploads/1/2/7/1/127150778/435734069.jpg)
Some key sessions at VMworld 2017 are listed below:
vSphere Clients Roadmap: HTML5 Client, Host Client, and Web Client
Technical – Intermediate [US: SER1411BU | EU: SER1411BE]
vSphere Client (HTML5) has been growing and evolving in public view, quickly incorporating customer feedback and adding functionality.
Technical – Intermediate [US: SER1411BU | EU: SER1411BE]
vSphere Client (HTML5) has been growing and evolving in public view, quickly incorporating customer feedback and adding functionality.
Discussion of vSphere Web Client (HTML5) and the Transition Experience
Technical – Intermediate [US: SER1792GU | EU: SER1792GE]
Group Discussion Come provide feedback directly to the product management team on the VMware vSphere Web Client (HTML5) released in VMware vSphere 6.5, which has also been released weekly in Fling form.
Technical – Intermediate [US: SER1792GU | EU: SER1792GE]
Group Discussion Come provide feedback directly to the product management team on the VMware vSphere Web Client (HTML5) released in VMware vSphere 6.5, which has also been released weekly in Fling form.
Acting as One: Plug in to vSphere
Technical – Advanced [US Only: SER3101PU]
Panel Discussion If you have ever wondered how to deploy and update multiple solutions with the VMware vSphere client, test custom solutions without having to set up complex infrastructures, transition from flex to HTML plug-ins, or run plug-ins without affecting vSphere client performance, you’ll want to hear from our panel of developers, who are working to provide a seamless experience for solutions integrating with the new vSphere HTML client.
Technical – Advanced [US Only: SER3101PU]
Panel Discussion If you have ever wondered how to deploy and update multiple solutions with the VMware vSphere client, test custom solutions without having to set up complex infrastructures, transition from flex to HTML plug-ins, or run plug-ins without affecting vSphere client performance, you’ll want to hear from our panel of developers, who are working to provide a seamless experience for solutions integrating with the new vSphere HTML client.
Additional Resources
Issue:
In vSphere 6.5, option to save the VM export in OVA format seems to be missing in both web client and HTML5 client (Right click VM > Template > Export OVF Template).
Workaround:
Use ovftool to export the VM as either OVF or OVA. Path locator formats to get the source VM are documented in ovftool user guide. In the below example VM named iaas1 is exported from under CSA datacenter (vm is the default folder name).
Example:
C:Program FilesVMwareVMware OVF Tool>ovftool vi://@vcsa1.prasan.com/CSA/vm/iaas1 c:iaas.ova
Enter login information for source vi://vcsa1.prasan.com/
Username: [email protected]
Password: **********
Opening VI source: vi://administrator%[email protected]:443/CSA/vm/iaas1
Opening OVA target: c:iaas.ova
Writing OVA package: c:iaas.ova
Transfer Completed
Completed successfully
Enter login information for source vi://vcsa1.prasan.com/
Username: [email protected]
Password: **********
Opening VI source: vi://administrator%[email protected]:443/CSA/vm/iaas1
Opening OVA target: c:iaas.ova
Writing OVA package: c:iaas.ova
Transfer Completed
Completed successfully
Side Note:
Issue: The OVF export is only saving the vmdk, and the export is missing the .ovf and .mf files
Cause: Browser pop up blocker blocks the export of .ovf file causing only the vmdk to be exported. Allow pop up in the browser settings and restart the ovf export again to download all the files.
![](/uploads/1/2/7/1/127150778/348362998.jpg)