Upgrading vCenter from 5.0 to 5.1 U2
I just wanted to share some notes and steps on upgrading vCenter 5.0 to 5.1. The steps for upgrading from 4.x is probably similar to the steps provided below as VMware also supports in place upgrade from 4.x on 64-bit systems.
One change with this upgrade scenario is that it is not supported to migrate vCenter to new server during upgrade to 5.1. Instead, you can migrate during upgrade to 5.0 and then you can do inplace upgrade from 5.0 to 5.1.
5.1 also introduces Single Sign-On service which needs to be evaluated carefully before deploying. In regards to installation of SSO on the same server with vCenter; when installed, it discovers the AD domain joined and also recognizes existing local system users.
Once SSO is deployed, the following components are installed
- STS (Security TokenService)
- Administration server
- vCenter Lookup Service
- RSA SSPI service
References to check out:
- Interoperability: http://www.vmware.com/resources/compatibility/sim/interop_matrix.php
- Upgrade guide: http://pubs.vmware.com/vsphere-51/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-51-upgrade-guide.pdf
- Release notes for 5.1: https://www.vmware.com/support/vsphere5/doc/vsphere-esx-vcenter-server-51-release-notes.html
- Release notes for 5.1 Update 1: https://www.vmware.com/support/vsphere5/doc/vsphere-vcenter-server-51u1-release-notes.html
- Release notes for 5.1 Update 2: https://www.vmware.com/support/vsphere5/doc/vsphere-esxi-51u2-release-notes.html
- Compatibility Guide: http://www.vmware.com/resources/compatibility/search.php
Before start backup the server, database and SSL certs (
Select SSO deployment option.
Select Single Node Type
Set SSO Administrator Password
To create a Database for SSO, go to the directory below in the installation media and run the SQL script provided after modifying the filename paths, named rsaIMSLiteSQLSetupTableSpaces (single Sign OnDbScriptsSSOServerSchemamssql) for SQL instances.
rsaIMSLiteSQLSetupTableSpaces: Change FileName as required:
Once the script runs, the following DB is created:
To create users, you need to run rsaIMSLiteSQLSetupUsers in the same directory. You need to change the passwords for youre requirements. This will create two users RSA_USER and RSA_DBA as follows:
JDBC Connection Options
FQDN of vCenter
Security Support Provider Interface service account information. If you plan to create a high availability Single Sign-On deployment, change this to an Active Directory user:
Not: IF you choose Network Service, verify that the NETWORK SERVICE account has read and execute on the folder where the RSA SSPI service is located. The default location is: C:Program FilesVMwareInfrastructureSSOServerutilsbinwindows-x86_64.
Set Installation location
vCenter Single Sign on port Settings:
Log file is located at C:UsersAdministrator.SHAppDataLocalTemp2vim-sso-msi.txt
Installation of Inventory Service
vCetner Inventory Service Upgrade warning
Database re-initialization options
Inventory Service Ports:
To register Inventory Service with SSO:
vCenter Server Upgrade
ODBC – DB credentials:
This warning is normal. The upgrade for Update manager will be done afterwards:
Options for DB, actually there is only one option as seen below. If you select the other one, Next button gets grayed out.
Agent Upgrade options:
vCenter Server Service Account:
JVM memory for vCenter
Provide SSO credentials:
Found user groups. The text file is at %temp%vc_admin_users_groups.txt
Provide Inventory Service Information:
And click Install. The upgrade might take up to 15 min 🙂
vSphere Web Client
Web Client Ports:
Upgrading Update Manager is pretty straightforward as well: