Installing the HTML5 Web Client v2.0

This is a quick note on installing the HTML5 Web Client v2.4.  I have not used the HTML5 client in a while and I am curious to see ow it has changed.  As well, recently they added in an update option which will help me keep it current easier.

Get the bits here.  You need to have both the SSH access and BASH shell enabled on your VCSA (or PSC). You enable SSH in the Admin area of the vSphere Web Client and BASH in the VCSA command line (more info can be found here).

Now deploy via Deploy an OVF template.  You will need to use DHCP or provide a Static IP.  No other IP config is possible during deploy if you use the vSphere Client – and I had to use the C# client since deploy with the vSphere Web Client stayed on initializing for a very long time.

It did not power up successfully for me.  I got a “Cannot initialize property vami….” error message.  I used the info in this article to configure some vApp properties – IP, DNS, domain, gateway, mask, search domain kind of stuff.  It still did not work for me, and so I than created a Network Profile.  I configure it without an IP pool but did all the other stuff and now the VM would start.  Good grief.

Now we need to make some HTML5 application changes – like connect it to SSO.

So lets connect to https://fqdn:5490 and authenticate with root / demova.

You will need to enter your SSO credentials and NTP info.



In at least three different versions – now at 2.4 it still will not work with me.  I try various legit credentials.


I have confirmed that the date / time is correct and in sync.  I confirm that I have good DNS on the H5 appliance – I can ping by short or long name my vC.  I have confirmed I am using the correct and good credentials.

So now I am irritated, and ready to be radical.  So I log into the CLI of the H5 appliance, and I do a CLI configure.


And it works.  WTF?  Note that I use the root account rather than administrator or whatever.  It looks like the H5 application needs to log into the VCSA rather than connect to SSO.

But is it really working?


So it is working.  Finally.

I did access the :5490 after it was working and added an NTP server.  Still used the root account for the VCSA and it worked fine.  In previous versions you can log into :5480 to check network info but that doesn’t seem to work any longer..


=== END ===

Leave a Reply