Install SSO and upgrade from 5.0 to 5.1 vCenter,Inventory,vSphere,vSphere Update Manager
Step 1 : What is SSO and Installing SSO
SSO is shortly enables authorized vCenter Server users to access multiple vCenter Server-related systems with a single login.
I created a new VM for install SSO.
Need a database, if you don’t have central one or standalone database server then SSO installation package come with mssql express one and you can use it
No need to do something from GUI just change the path of mdf/ndf/ldf and execute such sql commands, no need to create a sql user, i will use windows auth 😉
CREATE DATABASE RSA ON PRIMARY(
FILENAME=’C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\RSA_DATA.mdf’,
FILENAME=’C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\RSA_INDEX.ndf’,
FILENAME=’C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\translog.ldf’,
To whom interest jdbc out “jdbc:sqlserver://;serverName=10.110.1.61;port=1433;databaseName=RSA;integratedSecurity=true”
Now, mount the vCenter 5.1 cd iso to sso server and start installation, without sso installed you can not upgrade inventory service and vCenter 5.1 also check .Net 3.5 SP1 installed or not !
I do not have AD environment for SSO will join because of that you can get warning message, click OK and continue
Now, you have a option to install SSO high available but i will not do this, SSO virtual machine run on cluster and i’m backing it with veeam also without sso just only loose management 🙂 but all cluster functionality and vm activity will continue to work
For high availability pls fallow http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&externalId=2033588&sliceId=2&docTypeID=DT_KB_1_1&dialogID=433530793&stateId=1%200%20433554690
I selected basic one
Password for admin@System-Domain and –> Next
Did you decide to which MSSQL will you use , i will choose existing one –> Next
Set related db informations like below and –> Next
Give the sso server ip address or FQDN –> Next
No need to change installation folder –> Next
SSO service port described, its 7444, no need to change until you used this port for other service –> Next
Click Install and wait installation finish, perfect first round over.
Step 2 : Upgrade Inventory Service
On vCenter 5.0 there is no option at the installation time but service was there after installation over, you have to read related pdf on links section end of the article to understand why such service created but shortly its helping vCenter to reducing direct access clients to vCenter, working like a cache or something like that.
Start installation, it will inform you replace SSL Certificate (i did not use special one before) , agree the term , Choose Do not overwrite existing database, vCenter hostname should be come automatically, leave the ports default, if you also need to increase number of VM and host what vCenter will handle change the “Inventory Size” .
Now time to enter SSO user and test it , enter SSO user/pass and SSO server hostname, if you see the Certificate Installation window then its okay SSO is working
Click Install certificates and Install !
Step 3 : Upgrade vCenter 5 to 5.1
Start installation, my vCenter db is on central database server , its asking database user name and password, pls set correct one.
Installation will detect if you have old components like Update Manager, you have to upgrade it after vCenter upgrade.
Be sure you backed up vCenter database and related SSL folder and go !
Leave automatic vCenter Agent Upgrade option and click next
I was running vCenter Server with SYSTEM Account and keep continue with it
leave the ports default, if you also need to increase number of VM and host what vCenter will handle change the “Inventory Size”
Enter SSO user/pass and SSO server hostname , installation will pop up a warning like below, i want to keep users and clicked “Yes”
deleted_vc_users.txt which is under %temp%
Resgiter vCenter Server administrator with SSO
Register vCenter and Inventory, for me leave how installer prepared the values and next
Set intallation folder next and click install .
After instalaltion of course next step will be upgrade vCenter client but you will get a permisson error and you have to give permission to SSO admin user to connect,manage and maintain on vCenter Server 🙂
Step 4 : Upgrade vCenter Client
Run vSphere Client installation and go !
Step 5 : Upgrade the vCenter Upgrade Manager
Start installation, old version will be detected , continue
I tried without use sso user and still its working
Next, database user pass will be requested , set it and click next
Select upgrade database option next and verify update manager ip address and ports and next
Click install ,installation will stop the running process of update manager and start to update system
Back to the vCenter Server and from Plug-ins tab select Manage Plugins and from Available Plug-ins click Download and Install and fallow the instraction accept new certificate and its there ….
Control your baseline and configurations and if you will upgrade ESXi5.0 to 5.1 then upload the image from ESXi Images tab of update manager, create a new base line for it
Let me show you the upgrade ESXi from Update Manager
Choose the host and go to Update Manager tab, you can see that one incompatible/Upgrades are waiting. I guess you can not see that because you have to attach a new baseline to host which you created before upload the image
Click “Remediate” and choose UpgradeBaseline and related option from right site and next and accept the agreement ,Remove 3th party incompatible softwares ,enter description and related settings on next screens and go !
Reset SSO Password – http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2034608
Inventory Service – http://www.vmware.com/files/pdf/techpaper/Whats-New-VMware-vCenter-Server-51-Technical-Whitepaper.pdf
Posted on 26/09/2012, in vCenter and tagged install vmware sso, SSO, Upgrade ESXi5 to ESXi 5.1, Upgrade vCenter 5 to vCenter 5.1, Upgrade vCenter5, Upgrade vSphere 5, VMware. Bookmark the permalink. 1 Comment.