What a release schedule! The team behind vSphere HTML5 Web Client Fling is doing a beautiful job here, one release every other week. I previously blogged about v3.32 of the plugin and the vApp goodies it brought. Here we are in front of a new release, v3.33, with another great set of vApp and VM improvements.
You may already know I’m a big fan of vSphere HTML5 Web Client Fling, so you should be not surprised that I follow closely the development of this fling. Last few days like everybody else in the tech world I was busy with Meltdown and Spectre vulnerabilities, but I still managed to notice that the development team released a new version: vSphere HTML5 Web Client Fling v3.32.
In an earlier post I showed how to install vSphere HTML5 Web Client Fling. The biggest difference between fling version and the vCenter 6.5 supported version is that the fling gets updated more often. In this post I will show how easy it is to update vSphere HTML5 Web Client Fling.
I will start from the base version 3.27.0 build 7055108. My target is to update the fling to version 3.29.0 build 7157335. Even if only 2 weeks passed since 3.27.0 release, there are few new features available:
Configure advanced CPU Identification Mask
Select PVRDMA adapter type for a VM network
Configure traffic filtering and marking rules on distributed port groups
Export and import distributed switches and distributed port groups
VMware agrees that Flash is not the solution for the long-term. Our long-term direction is to utilize HTML5. In vSphere 6.5, we have released a supported version of an HTML5 based web client which we call “vSphere Client”. What’s New in vSphere 6.5: vCenter management clients
This vSphere HTML5 Web Client evolved from an application initially published as a Fling (“Flings are apps and tools built by our engineers and community that are intended to be played with and explored”). The Web Client made available in vCenter is a fully supported version of the fling. However, VMware updates the fling version of the client more often. Even if the fling version is not supported, it’s still good to play with what will eventually graduate to a supported version.
In this article I will guide you through the initial configuration of vSphere HTML5 Web Client Fling. We will install the fling in parallel with the existing vCenter Server and will make no permanent changes at vCenter level. If you want to update an already existing installation of the fling, check this article: How to Update vSphere HTML5 Web Client Fling.
I will start the process with the download of the OVA file. Go to the VMware Fling repository and download the latest version available (in my case v3.27 – Build 7055108, released on 4th November 2017). Check “I have read…” checkbox and choose the OVA file from the drop down list (in my case h5ngcVA-220.127.116.11-7055108_OVF10.ova). You can then click on “Download” button and wait for the archive to be downloaded.