VMware is the global leader in virtualization software, providing desktop and server virtualization products for virtual infrastructure solutions. VSphere Client on Mac OS X - YouTube Running the vSphere Client on a Mac OS X is something the Mac users want to be able to do. This video demonstrates the fact that it is possible.
After you develop your vSphere Web Client extension, you can follow these recommendations to ensure that your extension is successfully deployed to the vSphere Web Client or the vSphere Client .
To improve the performance of your plug-in package, the initial download and deployment time after the first time the user logs into the vSphere Web Client, must be less than a minute.
■ | To ease the testing and debugging of your plug-in package, you must include the build number in the dot-separated version number of the plug-in package when you register the plug-in as a vCenter Server extension. | |||||||||||
To prevent deployment issues when you try to deploy a new version of a registered plug-in package, make sure that you modify the version property of your plug-in package in the plugin-package.xml manifest file. | ||||||||||||
■ | To prevent deployment issues when you try to deploy a plug-in package with the same version, make sure that you unregister the plug-in package by removing the plug-in as a vCenter Server extension point. You must also manually delete the cached files of the plug-in package that are stored on the Virgo server from one of the following locations:
| |||||||||||
To avoid issues with the vSphere Web Client performance, make sure that your plug-in package has only one version registered with the vCenter Server. You must not change the value of the key property of the vCenter ServerExtension data object between releases. | ||||||||||||
■ | To verify easily the deployment of your plug-in package and monitor for any issues related to your plug-in, you must know how to work with the Virgo server log files. You can find these log files in one of the following locations:
The vsphere_client_virgo.log file contains the log information that the Virgo server generates. Problems usually start with the [ERROR] tag. Use your plug-in package name or the bundle symbolic name to detect errors caused by your plug-in. | |||||||||||
To log information about your plug-in package, you must use the default logging mechanisms of the vSphere Web Client. Use the Apache Log4j logging framework to provide debugging information for your plug-in package. The Virgo server uses the Simple Logging Facade for Java (SLF4J) logging API. |
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 For Mac Download
More from my site
