Upgrading vCenter from 5.0 to 5.1 U2

image

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:

Before start backup the server, database and SSL certs (%ALLUSERSPROFILE%VMWareVMware VirtualCenter).

 

Installing SSO:

 

Click install

SSO Install

Select SSO deployment option.

 SSO deployment options

Select Single Node Type

Single Node Type

Set SSO Administrator Password

SSO Administrator Password

Database Type

Database Type

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.

single Sign OnDbScriptsSSOServerSchema

rsaIMSLiteSQLSetupTableSpaces: Change FileName as required:

rsaIMSLiteSQLSetupTableSpaces

Once the script runs, the following DB is created:

RSA DB

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:

rsaIMSLiteSQLSetupUsers

RSA_DBA

RSA_DBA

RSA_USER

RSA_USER

JDBC Connection Options

JDBC Connection Options

FQDN of vCenter

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:

Security Support Provider Interface service account

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

Installation location

vCenter Single Sign on port Settings:

vCenter Single Sign on port Settings:

Install

SSO installation

Log file is located at C:UsersAdministrator.SHAppDataLocalTemp2vim-sso-msi.txt

 

Installation of Inventory Service

 

Setup Screen

vCetner Inventory Service Upgrade warning

Inventory Service Upgrade

Database re-initialization options

Database re-initialization options

FQDN

Inventory Service Ports:

Inventory Service Ports:

JVM Memory:

JVM Memory

To register Inventory Service with SSO:

To register Inventory Service with SSO

Certificate

Certificate

Click Install:

Install

 

vCenter Server Upgrade

 

Setup Screen

vCenter Server

Upgrade warning:

vCenter Server Upgrade

ODBC – DB credentials:

ODBC – DB credentials:

This warning is normal. The upgrade for Update manager will be done afterwards:

upgrade for Update manager

Options for DB, actually there is only one option as seen below. If you select the other one, Next button gets grayed out.

Options for DB

Agent Upgrade options:

Agent Upgrade options:

vCenter Server Service Account:

vCenter Server Service Account

vCenter Ports:

vCenter Ports:

JVM memory for vCenter

JVM memory for vCenter

Provide SSO credentials:

SSO

Found user groups. The text file is at %temp%vc_admin_users_groups.txt

vc_admin_users_groups.txt

Provide Inventory Service Information:

Inventory Service

Installation location:

Installation location

And click Install. The upgrade might take up to 15 min 🙂

The upgrade might take up to 15 min

Installation completes:

Installation completes

 

vSphere Web Client

 

vSphere Web Client Upgrade

Installation location:

Installation location

Web Client Ports:

Web Client Ports

SSO

Web Client SSO

Install…

 

Update Manager

 

Upgrading Update Manager is pretty straightforward as well:

image

Upgrading Update Manager

Upgrading Update Manager

Upgrading Update Manager

Upgrading Update Manager

Upgrading Update Manager

Upgrading Update Manager

Upgrading Update Manager

Good luck

Bulent Tolu

Bulent Tolu

Sr. Systems Engineer at VMware
Bulent is an IT professional with Master's in MIS and 10-years of experience in broad range of Information Technologies. He is exposed to engineering/architecting, implementation/integration, and administration of various high-available IT systems and infrastructure. He has a passion to continually research, test and evaluate new technologies and follow industry best practices to secure and optimize IT systems. Currently, he lives in Istanbul and works as a Sr. Systems Engineer at VMware.
Bulent Tolu

One Thought on “Upgrading vCenter from 5.0 to 5.1 U2

  1. prathi on 17 November 2014 at 22:08 said:

    Thanks bulent..this really helps.. I have a question, did you faced any issues during upgradation, if so plz share..

Leave a Reply

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

Post Navigation

Share
Translate »