vSphere Web Client URL Patterns

Although I don’t think vSphere Web Client is a good choice as main GUI for vSphere administration, it has done one thing right and well – it has a unique URL for almost everything you can browse the vSphere Web Client. The benefit is that you can bookmark a URL and open to the page without many clicks.

The URL for vSphere Web Client looks pretty long and could be intimidating at first impression. Like most of the things around us, the URLs have good patterns. I’ll analyze them and break them down to different parts. Once you finish this blog, you should be able to hack them by yourself.

Lost VMs or Containers? Too Many Consoles? Too Slow GUI? Time to learn how to "Google" and manage your VMware and clouds in a fast and secure HTML5 App.

URL Samples
The home URL of the vSphere Client is as follows, which shows the login page.

After successful user login, the following first page shows up:

From the first page, you can click to many different managed objects to monitor or manage. The following are a few URLs to some main object types.

vCenter Home:

As you would try out and observe, most of the URLs point to the Getting Started tab, which is not quite useful but still takes the first tab. If you want to go to a different tab, you would try out other extension IDs.

Let’s pick a virtual machine to different tabs:

Related Objects:;context=com.vmware.core.model%3A%3AServerObjectRef~E21E5AD2-E136-4F99-BD4F-43C6BE8EAA50%3AVirtualMachine%3Avm-135~core

As you can see the extension ids are pretty self explanatory. If a virtual machine monitor tab’s extension id is vsphere.core.vm.monitor.issues.commonView, would the host’s monitor tab be like vsphere.core.host.monitor.issues.commonView? That is what I tried with host and it worked. The trick does not work with the manage tab though.

Host Manage:;context=com.vmware.core.model%3A%3AServerObjectRef~E21E5AD2-E136-4F99-BD4F-43C6BE8EAA50%3AHostSystem%3Ahost-123~core

URL Patterns

As we’ve analyzed many URLs, it’s time to generalize the pattern. Here are the URL formula:


For one vCenter, all the part up to the extension-id is fixed. The extension-id can be different and rederers different pages. Most of the extensions need more information like vCenter instnance info, and managed object ID. These URLs comes with the following pattern:


All the vCenter UUID, managed object reference can be retrieved from the vSphere API, or vSphere MOB. They don’t change so it’s safe to use them unless removed. If you know these values, you can type them as shell command in a browser.

This entry was posted in Virtualization and tagged , , . Bookmark the permalink. Post a comment or leave a trackback: Trackback URL.

Post a Comment

Your email is never published nor shared. Required fields are marked *


You may use these HTML tags and attributes <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>


    My company has created products like vSearch ("Super vCenter"), vijavaNG APIs, EAM APIs, ICE tool. We also help clients with virtualization and cloud computing on customized development, training. Should you, or someone you know, need these products and services, please feel free to contact me: steve __AT__ doublecloud.org.

    Me: Steve Jin, VMware vExpert who authored the VMware VI and vSphere SDK by Prentice Hall, and created the de factor open source vSphere Java API while working at VMware engineering. Companies like Cisco, EMC, NetApp, HP, Dell, VMware, are among the users of the API and other tools I developed for their products, internal IT orchestration, and test automation.