Copy the ‘server-configure.bat’ file we downloaded earlier locally to our vCenter Server. This will be done from an administrator command prompt directly from our current Windows-based vCenter Server. The first bit of configuration involves us generating some configuration files for the new Web Client. Once the VM has deployed and booted successfully you should be sitting at a screen similar to that below.Īlthough it states to browse to a certain address to manage the VM – DON’T! There is still some configuration we need to perform before our HTML5 Web Client will work. Doing so is quite simple – basically just point it towards your datastore of choice and set up networking as you prefer it. Now that we have the OVA we can go ahead and deploy it. The first thing you need to do is head to the VMware Flings site and pull down a couple of required files the first being the OVA containing the actual HTML5 client, and since we are a using the Windows version of vCenter in this example we will also need the ‘server-configure.bat’ file which will generate a few required configuration files we need in order to connect our HTML5 Web Client to our SSO instance.

Now we are seeing this same type of HTML5 technology being used with the vSphere HTML5 Web Client fling being released. Just this year with the release of vSphere 6.0 Update 2 we saw something called the “Embedded Host Client” make its way into a release – allowing us to manage our individual ESXi hosts with an HTML5 based interface built right into the product.

However, even by restricting new features only to the Web Client adoption has been slow – partly due to change, no one likes change, but mostly due to the slowness and the overall sluggishness that is experienced using the flash-based vSphere Web Client. VMware has long stopped adding newly released features and functionality into the old С# client in hopes to push their customers into using the vSphere Web Client.

StarWind Virtual Tape Library (VTL) OEM.

Vsphere web client