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
See the full change log in the official fling repository.
Update vSphere HTML5 Web Client Fling
Open a browser and visit https://ApplianceIP:5490. Authenticate using default root credentials (Username: root; Password: demova).
We are presented now with the appliance dashboard. Notice current version listed: Current vSphere Client version 3.27.0 build 7055108. Click on “Update vSphere Client” link on top of the page.
A confirmation pop-up window appears immediately. Click on “Yes” button to confirm”.
The update process starts. Notice the “Stop Server” link changed to “Updating…”. We begin to see logs scrolling down in the “Logs” window.
Logs are updating…
Finally, the web server starts, we see the status back to the green “Running”. Current version is still listed as 3.27.0, and the logs window still shows the last message as “vSphere Client Web Server application is being initialized”. This is why it’s a Fling and not a supported product 🙂
Update vSphere HTML5 Web Client Fling – Confirm
Click on “Logout” button and re-authenticate. Current version is updated now to our target: 3.29.0 build 7157335.
To have a second confirmation, login to the vSphere HTML5 Web Client Fling interface and click on the About top menu. We see again same version.
This concludes my demonstration. Happy VM managing 🙂