Create the only vCenter Single Sign-On instance in a standalone vCenter Single Sign-On installation or the first vCenter Single Sign-On instance in a deployment with multiple vCenter Single Sign-On instances.
About this task
These instructions let you install or upgrade vCenter Single Sign-On only. You must install or upgrade vCenter Single Sign-On and upgrade Inventory Service before upgrading vCenter Server. For most deployments, you can install vCenter Single Sign-On, the vSphere Web Client, vCenter Inventory Service, and vCenter Server together on a single host machine by using vCenter Server Simple Install. See vCenter Single Sign-On Deployment Modes and Use Simple Install to Upgrade vCenter Server and Required Components.
For more information about vCenter Single Sign-On, see How vCenter Single Sign-On Affects vCenter Server Upgradesand the vSphere Security documentation.
vCenter Server 5.5 supports connection between vCenter Server and vCenter Server components by IP address only if the IP address is IPv4-compliant. To connect to a vCenter Server system in an IPv6 environment, you must use the fully qualified domain name (FQDN) or host name of the vCenter Server. The best practice is to use the FQDN, which works in all cases, instead of the IP address, which can change if assigned by DHCP.
Download the vCenter Server installer. See Download the vCenter Server Installer.
- In the software installer directory, double-click the autorun.exe file to start the installer.
- Under Custom Install, select vCenter Single Sign-On, and click Install.
- Follow the prompts in the installation wizard to review the Welcome page and accept the end user patent and license agreements.
- If the prerequisites check screen shows any problems, cancel the installation, correct the problems, and restart the installer.
- Select the deployment mode Standalone vCenter Single Sign-On Server.
- Set the password for the vCenter Single Sign-On administrator account.
This is the password for the user firstname.lastname@example.org. vsphere.local is a new domain that is created by vCenter Single Sign-On. After installation, you can log in to vCenter Single Sign-On and in to vCenter Server as email@example.com.
By default, the password must have at least eight characters, at least one lowercase character, one uppercase character, one number, and one special character. See the vSphere Security documentation for information about changing the password policy. The following characters are not supported in passwords: non-ASCII characters, semicolon (;), double quotation mark ("), single quotation mark ('), circumflex (^), and backslash (\).
- Enter the site name for vCenter Single Sign-On.
Choose your own name for the vCenter Single Sign-On site.
- Accept or change the HTTPS port for vCenter Single Sign-On.
- Accept or change the default vCenter Single Sign-On installation folder.
- Review the installation options and click Install.
vCenter Single Sign-On is installed.
After vCenter Single Sign-On is installed or upgraded, the following default identity sources and users are available:
All local operating system users. These users can be granted permissions to vCenter Server. If you are upgrading, those users who already have permissions keep those permissions.
Contains all users who have administrator access to the vCenter Single Sign-On server. Initially, only the user administrator is defined.
What to do next
To deploy vCenter Server with multiple vCenter Single Sign-On instances, install an additional vCenter Single Sign-On at an existing or new site. See Install an Additional vCenter Single Sign-On Node at an Existing Site or Install an Additional vCenter Single Sign-On Node at a New Site. If your vCenter Server deployment requires only one vCenter Single-Sign-On instance, install the vSphere Web Client. See Install or Upgrade the vSphere Web Client.
To add other identity sources, such as a native Active Directory (Integrated Windows Authentication) domain or an OpenLDAP directory service, see Add a vCenter Single Sign-On Identity Source.