A fully supported version of the HTML5 client is released with vSphere 6.5, and the official name will be vSphere Client.  We won't be renaming this Fling, but may start saying things like 'vSphere Client Fling' in addition to the other terms we've used before. Fling features are not guaranteed to be implemented into the product.
Apr 12, 2016

We do not install the Windows vCenter into the default folder.
So the server-configure.bat is using %programfiles%, which is not the folder we install.

To get the batch working, we needed to replace the %programfiles% three times inside the script.

Apr 12, 2016

Same thing here. Not a huge problem but worth noting.

Apr 12, 2016

We will add this into the instructions. Unfortunately we haven't found an easy way to detect the install path, so everyone'll just have to make that edit on their own.

Thank you for pointing out this case.

Apr 12, 2016

It may be worthwhile to either have those paths be variables that get set at the top of the script.. that would prevent an ugly edit from accidentally getting done.

Apr 12, 2016

Upon further investigation, I didn't notice before, but they are:

These are the two paths that need editing, and they're the first two (non comment) lines in the bat file:

REM Path to javas' keytool
SET KEYTOOL=%PROGRAMFILES%\VMware\vCenter Server\jre\bin\keytool.exe

REM Path to vecs binary
SET VECS_CLI=%PROGRAMFILES%\VMware\vCenter Server\vmafdd\vecs-cli.exe

These are the paths that will need editing.

Apr 13, 2016

At the very end of the script you will find the third line you will need to edit:
SET CLIENT_DIR=%PROGRAMDATA%\VMware\vCenterServer\cfg\vsphere-client

Apr 13, 2016

Thanks! Will add this into next revision of instructions too.

Apr 12, 2016

Just a thought, for the last step in the upgrade workflow I think you should change "start" to "restart". Restart would work whether the service is started or not whereas start has no effect if it is already running.

Apr 12, 2016

Hah, looks like I missed the step to stop the service so disregard ;)

Apr 09, 2016

how do we upgrade to the 3732571 rpm build? tried the gui but didn't work. then ran

rpm -ivha --force /home/vsphere-h5-client-

and it appears to have worked, I am just making sure haha

Apr 11, 2016

When I try to upgrade using this:

rpm -ivha -–force /home/vsphere-h5-client-

the command-line states the upgrade performed successfully, but when I check the appliance's VAMI it still shows Appliance Version: Build 3680819

Is there another way to check the version?

Apr 11, 2016

If you go into the H5client page, and check the top right for "Help -> About..." you should see the build number there.

I think the VAMI page did not update because the RPM we have is only for updating the H5client code, not any of the VAMI page at all.

Apr 09, 2016

You caught us. We did a small test with some users to try out the upgrade flow. Stay tuned for a wide announcement, hopefully within a few business days.

Apr 08, 2016

Excellent work! Nice, responsive interface, clean installation instructions, well done! Looking forward the the continued improvement and additions to this!