vSphere 5.5 – Central SSO & Web Client – Single Pange of Glass Management 3

In my last post I wrote about the multi-site deployment of the vCenter Single Sign On server and how to achieve a single pane of glass to manage multiple vCenter servers using Linked Mode. Today I discussed the topic with a colleague and me tough it’s worth also sharing the outcome.

The discussed was about achieving the single pane of glass without using Linked Mode for the participating vCenter servers and indeed there is also an option to achieve exactly this.

This deployment foresees to install the vSphere Web Client as well as the Single Sign On server on a dedicated (virtual) machine to act as central component for multiple vCenter servers. All vCenter servers which should be a part of your central management pane will use these central components instead of a local installation. The vCenter server and the Inventory service will be installed locally as usual. The database for the vCenter server can be local or also a central (high available) database.

vCenterDeploymentOverSource: VMware vCenter Server 5.5 Deployment Guide

When installing the vSphere Web Client you simply connect to the locally installed SSO server and when going through the vCenter server installation you connect to the central system which hosts the SSO as well as the Web Client.

vCenterSSOConnectionI just wanted to share that this is also a possible deployment which could be absolutely sufficient to “link” multiple vCenter servers together in a single pane of glass. I’m going to cover a high available SSO & Web client deployment in a dedicated post.

Print Friendly, PDF & Email

Related Post

It's only fair to share...Tweet about this on TwitterShare on LinkedInEmail this to someone

Leave a comment

Your email address will not be published. Required fields are marked *

3 thoughts on “vSphere 5.5 – Central SSO & Web Client – Single Pange of Glass Management

  • Chris

    Excellent work, very useful! Look forward to the promised follow up article around HA deployment.

    Do you have any insight if this would work in the following situations:
    1. Using SRM 5.5. (Two vCenters, one in each site, with a single SSO server and web client server. Of course your HA setup would be used here to make sure the SSO is redundant across sites).
    2. Using Horizon View. This would mean one web client view for both server and VDI vcenters.
    3. How would this affect plugins (e.g. NetApp VSC 5, or NSX) which integrate to the Web client but tie into a specific vcenter server?

  • Jay

    The behavior where multiple vCenters are listed in one web client is solely the result of having multiple vCenters registered to the same SSO. While it’s useful to have a a central web client, if you install it on multiple different systems, alongside vCenter Server, all vCenters will still appear in all of those web clients.