vSphere Web Client

Quick Tip - Enabling HTML5 VM Console in the vSphere Web Client for IE

05.08.2014 by William Lam // 13 Comments

One of the biggest feature that I was most excited for with the initial release of vSphere 5.5, was the full support for Mac OS X with the vSphere Web Client. For many Mac OS X users including myself, this meant you could finally upload OVF/OVA, have support for remote device management such as mounting an ISO or floppy image and the biggest one of them all is having a supported native VM Console (based on HTML5)!

During the early Alpha/Beta release of vSphere 5.5, I started to use the VM Console for Mac OS X quite a bit. One thing that I had noticed was the HTML5 VM console was only used when you are running on a Mac OS X system. If you are on Windows or Linux system, it would still default to VMRC if you did not have the CIP (Client Integration Package) installed which included the VMRC. If you did not have CIP installed, then it would then default to the HTML5 VM Console as an alternative.

Last night, I saw a tweet from Steve Kaplan which seemed to indicate this behavior had changed:

I luckily had a Windows system that did not have CIP installed and took a quick look and found the following:

On both Chrome and Firefox, the HTML5 VM Console was available, you should see a "Launch Console" under the Virtual Machine summary page
On Internet Explorer (9,10 & 11), the HTML5 VM Console was not available and there was no "Launch Console" link

It appears that the behavior did in fact change between Beta and GA of vSphere which was kind of a shame ...

Not being satisfied with the answer, I was still hoping I could help find a solution for my buddy Steve. I think it would still be useful to be able to view the Virtual Machine console w/o having CIP installed, especially if you don't require the functionality of CIP. Thinking about it a for a bit, I had an idea that was worth a shot. I decided to change the User-Agent on the Internet Explorer to make it show up to the vSphere Web Client as Firefox versus Internet Explorer to see what would happen.

To my surprise, as you can see from the screenshot above, it worked! I guess the vSphere Web Client specifically looks for the browser type and if it is Internet Explorer, we only provide the CIP installer versus using the HTML5 VM Console. I'm not exactly sure why that is the case, but at least there is a work around. Here are the instructions if you wish to change the User Agent on IE. I also found that this worked on both IE10 and 11 but not IE9.

Disclaimer: This may not be officially supported by VMware, but you probably already know the drill 😉

This is a nice workaround if you are using the vSphere Web Client, but if you do not want to go through this hassle you can ALWAYS access the HTML5 VM Console by generating the URL itself and this will always work on ALL browsers without any workarounds. Here is a nice script that I created which will handle this for you. Web Client 0, Customer 1 🙂

vSphere Web Client Plugin for Custom Attributes

02.07.2014 by William Lam // 19 Comments

I just learned about a very cool vSphere Web Client Plugin that was developed by a fellow vExpert, Patrick Haefner who shared this during the South Germany VMUG back in February of last year. The custom vSphere Web Client Plugin allows administrators to view Custom Attributes in the vSphere Web Client which is currently not available today. The Custom Attributes vSphere Web Client is hosted on the VMUG site and you will need to register to access the download page found here.

Disclaimer: This plugin is not officially supported by VMware, please use at your own risk.

To install the Custom Attributes plugin, you just need to extract the contents of the zip file and you will should see a directory called haif-customfields-ui. You will need to copy this directory to your vCenter Server which is running the vSphere Web Client. This plugin should work on both vSphere 5.1 and 5.5.

For Windows vCenter Server:

Stop the vSphere Web Client service
Copy haif-customfields-ui to C:\Program Files\VMware\Infrastructure\vSphereWebClient\plugin-packages
Start the vSphere Web Client service

For VCSA (vCenter Server Appliance)

Stop the vSphere Web Client service by running /etc/init.d/vsphere-client stop
Copy haif-customfields-ui to /usr/lib/vmware-vsphere-client/plugin-packages
Start the vSphere Web Client service by running /etc/init.d/vsphere-client start

Once the vSphere Web Client has been started, you can now login and for Virtual Machines or ESXi hosts which have Custom Attributes, you should now see a new portlet displaying the Custom Attributes as seen in the screenshot below.

I think this is a really cool plugin and shows how extensible the vSphere Web Client is by leveraging the vSphere Web Client SDK. With a bit of imagination, you can pretty much build anything! Though today Patrick's plugin only allows you to view the Custom Attributes, perhaps if there is enough requests, he may add the ability to modify Custom Attributes. Awesome work Patrick and thanks for sharing it with the community!

Big thanks to Ruediger M. who works as a VMware SE in Germany for sharing this awesome information. This is definitely a plugin I will be installing in my environments 🙂

Quick Tip - Useful Flash Player optimization for the vSphere Web Client & other Flash WebApps

11.15.2013 by William Lam // 11 Comments

I recently picked up a useful tidbit from engineering on a Flash Player optimization setting that can be helpful when using the vSphere Web Client or any other Flash web application for that matter. The particular setting is the Website Storage Settings which controls the amount of temporary data that can be stored by the Flash Player on your local disk and by default this is limited to 100Kb. This limited storage footprint is actually done on purposes as a security feature of Flash.

However, at some point the Flash Player will reach this limit and prompt the user to allow additional disk space to be consumed and this is where you may see the vSphere Web Client crash and you would to go through the motions of logging back in.

To avoid this scenario, you can change the default 100Kb to unlimited for a particular site which I was recommended so that I would not hit this problem. I do want to stress that this is not a VMware best practice but more of a general Flash Player best practice but I think it is something to be aware of and could help from a usability perspective.

To check your current settings, Adobe has made it very simple by just navigating to the following URL: http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager07.html

A panel will load and you will get access to a variety of Flash Player settings including the Website Storage Settings which is what the link above will default to.

You will now be able to browser to the particular website, in our case we will be looking for either the hostname or IP Address of your vSphere Web Client Server and you will be able to see its current usage as well as limit. To change the default, you just need to click on the website and then move the toggle at the top to the far right which will show up as "unlimited". I would recommend you make this change for all your vSphere Web Client servers that you access. It would have been nice to see our vSphere Web Client automatically detect this and recommend the change or automatically default to this setting.