Almost every week a new beta version of the vSphere HTML5 Web Client is released. As you already know the community loves this product: the site has more than 1400 comments, 63 bugs and a huge changelog with lot of improvements and bug fixes. The huge enthusiasm is understandable, because the HTML5 based client provides a modern, flat based much cleaner interface. Of course the most important advantage is the rocket speed response time.
This year in March I also tested the first version. (For Hungarian readers: Zoli has also posts here and here) Since then, VMware has released the vSphere 6.5 VCSA including a “supported version” of the vSphere H5 Client. (bulid 4598948)
Unfortunately upgrading of this vSphere Client inside the VCSA is not possible currently. The only way to have the latest Fling (which is 2.19 – Build 4810256) is using the vSphere Web Client Appliance. The installation method is pretty much the same, as with the Bulid 3680819, but since the 1.17 – Build 4202128 a new way is available through the Fling Appliance Management Interface (FAMI). This web interface eliminates most of the CLI part – theoretically:) Let’s check it.
- Download the OVA, deploy it and boot it. You will get the following on the console:
- On the VCSA6.5 the default shell must be changed to bash, this can be done via SSH.
- Now we can use the Fling Appliance Management Interface (FAMI), which is available at https://H5_Appliance_IP_Address:5490 (On the port 5480 we can modify the IP, GW, DNS, hostname of the appliance). With the FAMI the VCSA registration can be done.
- Looks great! Now we have two H5 Clients: the integrated one inside the VCSA and the latest one as an OVA appliance. Let’s check the latest H5 Client with opening the https://H5_Appliance_IP_Address/ui Unfortunately there is no UI, but an error message was waiting for me
A server error occurred.
 An error occured while sending an authentication request to the vCenter Single Sign-On server – An error occured when processing the metadate during vCenter Single Sign-On setup – null.
Check the vSphere Client server logs for details
Oookay. Look into the logs
root@vcsa65 [ ~ ]# /etc/init.d/vsphere-client show_log
At the end:
[2016-12-29T11:54:02.900Z] [INFO ] cm-catalog-manager-pool-5 c.v.v.s.c.impl.SecurityTokenServiceImpl$RequestResponseProcessor Request message has expired. Server message: ns0:MessageExpired: The time now Thu Dec 29 12:54:03 UTC 2016 does not fall in the request lifetime interval extended with clock tolerance of 600000 ms: [ Thu Dec 29 11:44:02 UTC 2016; Thu Dec 29 12:14:02 UTC 2016). This might be due to a clock skew problem. [2016-12-29T11:54:02.900Z] [INFO ] cm-catalog-manager-pool-5 c.v.v.s.c.impl.SecurityTokenServiceImpl$RequestResponseProcessor Server returned 'request expired' less than 0 seconds after request was issued, but it shouldn't have expired for at least 600 seconds. [2016-12-29T11:54:02.900Z] [ERROR] cm-catalog-manager-pool-5 com.vmware.vise.vim.security.sso.impl.SsoUtilInternal Time sync error: VC Server and local machine's clocks are out of sync by more than the accepted tolerance. [2016-12-29T11:54:02.900Z] [ERROR] cm-catalog-manager-pool-5 com.vmware.vise.vim.security.sso.impl.NgcSolutionUser Solution user login failed. com.vmware.vim.sso.client.exception.TimeSynchronizationException: Server returned 'request expired' less than 0 seconds after request was issued, but it shouldn't have expired for at least 600 seconds.
So it is a clock skew problem, however I added an NTP server to the H5 Appliance. Double checked both side (VCSA6.5 and H5 Appliance), NTP servers added, time synchronized, results: Login is displayed. Below some screenshots.
One of the latest improvement in the v2.19 is the Dashboard functionality: When pressing the Home, you will get an overview at the vCenter level.
Looks great, but still a lot of functionality is missing (check this table – at vSphere6.5 level). Hope the H5 client will be the one soon with full feature set.