Discovering vSphere web client 5.1

When the web client was first announced last year, I was really excited with what it had to offer. I was personally even more excited because I really thought, I would finally have no need to run a windows VM on my mbp.

Then I had a rude awakening which triggered me to write this post. Basically, even though you could access the web-client via the browser on OS X, there is still an element called the “Client Integration Plug-in” that cannot be installed on OS X. :(. This and a few more things just killed all my motivation to use the web-client. I figured if I was going to run a VM to access a fully functional client, I might as well run the C# client. But now things have changed a bit.

To start off, the client integration part has still not changed, it still does not fully work on OS X. I just tried it on 10.8 with no luck. So what does this really mean? Lack of inability to install this will keep at least two options away from you that I know of.

  1. Ability to launch the console of the VM
  2. Ability to transfer files to and from datastores
These are the only two that I am aware of, I am not sure if there are any other gotchas yet. But clearly these are not the end of the world. Another thing that I found disappointing was the inability to access VUM from the web-client. Seriously? Why?
So now that I am done with all the trash talking. Lets talk about why should you still get on the web-client bandwagon soon.
  1. I have been told, support for OS X is on the roadmap (that should address the client integration plugin issue)
  2. The VUM plug-in is coming soon
  3. All/most new enhancements of 5.1 are visible and accesible via the web-client ONLY
  4. 5.1 will be the last release for the traditional C# client we have used for all these years. Going forward, web-client is the only way.

So there, #4 should be enough to motivate one to move forward. But let’s keep the draconian approach out for a little bit. The web-client has had a major face lift and IMO has a much better UI. Sure, you will feel lost in the beginning but you will notice the web-client will provide you a much better user experience. The UI is well thought out and has a much better work flow.

To start off, one can now assign searchable tags to objects inside vCenter and yes one object can have more than one tag assigned to it. I am sure this will be a very helpful new feature in large environments.

How many times have you started doing something in vCenter only to realize you have to go back to a different object to get some info. But you can’t without canceling the wizard and what you are doing. In comes work in progress, this is a pretty handy way to address those situations where you can pause what you are doing and come back to it when you are ready.

Another one that I find very useful is the log browser. Basically it gives you the ability to view the logs for your vCenter and all yours hosts in one place. Isn’t that nice? Single pane of glass is what we always wanted. And yes it will let you see all the logs of your host, and you can switch between the type of logs using the drop down list as shown below.


These are simply some of the new features that the web-client has to offer among so many more. During the beta, I noticed the OS X compatibility issue but was hopeful for it to be fixed before GA. That didn’t happen but at least its on the road map. The VUM plugin is coming soon along with most other third party plug-ins. Keep in mind, dont be shocked if future third party plug-ins are only available for the web-client. It only makes sense for the vendors to develop for the client that will stay.

Lastly, if you want to make use of all the enhancements in 5.1, the web-client is a must. I was originally not too impressed by the original web client last year, but I must say the 5.1 is not just as good as the traditional c# client but better. Moreover as mentioned above, the traditional client is going away, now will be a good time to get to know your new friend.

VNC and vSphere 5 for Mac users

The other day I was testing out the vSphere web client and posted about some of the challenges fot the unfortunate mac users. Sveeny took the time to comment on the post a work around which has been secretly used by many vSphere outlaws for years. I mentioned the lack of ability to install the client integration plug-in on OS X which pretty much keeps you from not only accessing the VMs console but also disallowing connecting any virtual devices connected on the client machine.

Sveeny mentioned that one can use VNC for this and he is right, he said:

A little workaround for the console issue. You can enable vnc for every vm.
First you have to enable VNC on the firewall.
then you have to set the following parameters in the vm advanced config:
RemoteDisplay.vnc.port: 5900 (for every vm on a host a different from 5900-5999)

Open finder press +k and enter vnc://esxhost:5900

Here are some detailed info on setting this up.

However there a few things I wanted to point out that doesn’t make me a fan of this approach.

To start, the connection is made by using the hostname/IP of the host the VM is running on followed by the port that was assigned to the VM. This means on your DRS enabled cluster, your VNC connection may not be the same all the time as the VMs will move around. This will probably not be a good idea for large clusters where DRS can have more fun. Not to mention with DPM turned on this can be even more fun.

I am sure a lot of complaining and crying went around before the firewall finally showed up in ESXi. Going back and opening up ports for VNC is perhaps less secure than leaving it closed. Yes, the firewall on each host will have to be configured to allow VNC connections to that hosts.

I also see this as an added overhead. Not in terms of computing resources as much as in man hours and actual $. Why? Remember each VM in your environment that you want to connect via VNC will have to be configured appropriately. Each .vmx will have to be updated for this to work. Also, I am unsure about how well connecting virtual devices from client machines work with VNC.

And finally I have been unable to confirm if connection via VNC is supported. From what I understand, this is an unsupported setup.

Overall, this is not a bad work around if you are desperately in need for access to the console and are running an OS/browser that does not support the client integration plug-in for the web client. But my preference and recommendation will be to hope and cry for client integration plug-in to work on the OS X at the least. And obviously Chrome, after all its one of the most popular browser. Knowing the web client is still fairly new, I am sure all these capabilities will come in with time, this is just my way of crying and saying “VMware, please hurry up”.

vSphere Web Client and OS X

So I finally decided to install the Web Client server in my lab. Everything was pretty straight forward as far as installation goes. Ones you get through the wizard, you will basically have to register the Web Client with the vCenter server. This happens on the server where the web client server is installed via the browser. You will go to https://web-client-server:9443/admin-app/ where server is the name/IP of the web client server. Keep in mind this requires flash to be installed on the server. I am not a big fan of installing flash unless absolutely needed, so here is the workaround thats mentioned in this kb article.

If you don’t want to install flash on the web-client server, simply type the following command on your web-client server:

admin-cmd.bat register https://web-client-server:9443/vsphere-client https://vCenter-server username password

Be sure to replace the portions in blue above with your info (web-client server, vCenter server, username, password).

Once the registration is complete, you can simply head over to https://web-client-server:9443/vsphere-client and login. However, be warned, though this is a great alternative to the vSphere client, it does not have all the functionalities and even less if you are an unfortunate Mac user.

 At the bottom left of the screen, you will notice where it says “Download Client Integration Plug-in”, and if you are a Mac user you will be disappointed. Why? Because this will not install, you will be prompted with with a message as displayed below:


So whats the big deal?

To start off, client integration does a couple of important thing that I am aware of:

  1. Allows you to access a virtual machine’s console in the vSphere Web Client
  2. Allows you to connect virtual devices that reside on a client computer to a virtual machine (think USB devices on a client machine)

So if your an OS X user, you will not be able to perform those tasks using your web-client. Will this kill you? Probably not but it’s disappointing to see that OS X has been left out for now. I have heard that support for OS X is in the roadmap for the future. When exactly? No clue. I guess after crying for years, VMware listened to the Linux users and released the web-client and I think its only a matter of time before the Mac world starts to see all the features.

Don’t get me wrong. The web-client doesn’t cover all the features a traditional vSphere client has but it’s ver 1 and I am sure it will get there soon. If you are a Mac user, keep in mind the functionality of the web-client on OS X is even more limited.Will I still use it? Absolutely, this will replace the traditional client we have known for years one day.