The way that you deploy vCenter Single Sign-On and the type of user who installs vCenter Single Sign-On affects which administrator user accounts have privileges on the Single Sign-On server and on vCenter Server.

During the vCenter Server installation process, certain users are granted privileges to log in to vCenter Server and certain users are granted privileges to manage vCenter Single Sign-On. The vCenter Server administrator might not be the same user as the vCenter Single Sign-On administrator. This means that when you log in to the vSphere Web Client as the default Single Sign-On administrator (admin@System-Domain), you might not see any vCenter Server systems in the inventory. The inventory appears to be empty because you see only the systems upon which you have privileges in the vSphere Web Client.

This also means that when you log in to the vSphere Web Client as the default vCenter Server administrator, you might not see the vCenter Single Sign-On configuration tool. The configuration tool is not present because only the default vCenter Single Sign-On Administrator (admin@System-Domain) is allowed to view and manage vCenter Single Sign-On after installation. The Single Sign-On administrator can create additional administrator users if necessary.

The vCenter Simple Install process installs vCenter Single Sign-On, the Inventory Service, and vCenter Server on one system. The account you use when you run the Simple Install process affects which users have privileges on which components.

Deploying vCenter Single Sign-On in Basic mode means that a standalone version of vCenter Single Sign-On is installed on a system. Multiple vCenter Server, Inventory Service, and vSphere Web Client instances can point to this standalone version of vCenter Single Sign-On.

Deploying vCenter Single Sign-On as a cluster means that two or more instances of vCenter Single Sign-On are installed in high availability mode. vCenter Single Sign-On high availability mode is not the same as vSphere HA. All instances of vCenter Single Sign-On use the same database and point to the same identity sources. Single Sign-On administrator users see the primary Single Sign-On instance when they connect to vCenter Server through the vSphere Web Client.