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 07, 2016

I've got the h5client appliance set up with a windows vCenter 6.0 U1 server, installed it following the instructions, but it doesn't let me log in using the admin account I use for the regular webclient. Error: Unable to authenticate user. Please try again.
Logging in with the root account works, all settings like dns and time are ok. Any idea why it fails to log me on? Any logs I can check? First feedback tip: On the root config webpage, add a button to check the vcenter connection.

And something else, when checking for updates I got this error:
Failed to check for updates(Error validating the digital signature of the update manifest. Please contact your vendor.) on Thursday, 2016 April 07 11:22:26 UTC+2

Apr 07, 2016

"When checking for updates" - Where are you doing this?

You can try running "/etc/init.d/vsphere-client tail_log" on the H5client appliance and see if there's any errors there.

Your situation does sound weird though. Can you try pinging your PSC from the H5client appliance, maybe that's the issue?

Apr 11, 2016

I've checked for updates by logging in with the root account on the web page, choosing the update tab and pressing the button Check Updates.

I can ping the PSC, that's not an issue.
The only entries I see using the vsphere-client tail_log command are core dump rotations every hour. If I attempt to login on the webpage, nothing is logged.

Apr 11, 2016

Can you email me your webclient.properties file (feel free to obscure whatever you need)?

You should find my email in an earlier comment on this page (search for vmware.com)

Apr 14, 2016

Same error here when doing an update through the interface on 5480:

Failed to check for updates(Error validating the digital signature of the update manifest. Please contact your vendor.) on Thursday, 2016 April 14 20:54:54 UTC+2

Apr 14, 2016

We don't support updating through the 5480 UI, it's actually designed for a different use. I misread this before.

The instructions for updating are available in the Instructions tab on this page, or under "Upgrade Flow" in the instructions pdf. It involves manually downloading the rpm to the appliance and then applying it. We will improve this flow in the future.

Apr 06, 2016

I deployed the OVA (Windows vCenter) but once done, I can't even ping it.
All settings are correct in Options -> vApp Options -> Advanced -> Properties.
Is it supposed to work when connected to a dVS ?

Apr 06, 2016

Works fine with vDS. Did you create an IP Pool for this? You'll need to do that and associate the vDS port group to the IP Pool.

Apr 06, 2016

Will try that ! Thank you.

Apr 04, 2016

We have our vCenter windows install on D:\ drive.
It is apparent from the .bat file and from the /etc/vmware/vsphere-client/vsphere-client/webclient.properties files that C:\ is hardcoded.
Could we please get updates in the instructions to clarify which files need to be edited IF the vCenter server has been install on a drive other than C:\
Thanks in advance,
Justin Rowling

Apr 05, 2016

Will do! Thanks for the feedback. We'll see if we can do this in some better way.

Apr 01, 2016

I tried it, and completely satisfied. it`s so snappy

at first I faced with common error;
HTTP Status 400 – An error occurred while sending an authentication request to the vCenter Single Sign-On server – An error occurred when processing the metadata during vCenter Single Sign-On setup – java.net.UnknownHostException:

by restarting init.d nothing happened.
I filled out th DNS IP adr in web client and this issue fixed.