So I completed the upgrade of my vCenter server to 5.1 today. All went well with some minor issues which Google helped with.
Thank you to everyone to provided assistance to me while preparing for this upgrade!
My biggest concern with the installation of SSO and it's DB. Our vCenter DB current exists on a separate 64bit SQL 2008 R2 server so the ODBC connection that was there worked flawlessly. The scripts provided worked as described after the customisation for our environment.
The following links helped me prepare for the SSO installation:
- Successfully Installing vCenter SSO Part 1 - SQL Database via @ChrisWahl | Wahl Network
- vSphere 5.1 - Part 2 - vCenter Single Sign On (SSO) Install
The real issue that stomped me was this:
The wizard was interuppted before VMware vCenter Server could be completed installed.
vCenter Server has been successfully installed, but one or more of the vCenter Server components was not installed.
Once I checked the logs they made mention of an exist code of 1603 which led me VMware KB: Installing Profile-Driven Storage via vCenter Server fails with an error code 1603 which did not help.
After some Googling, I found a forum where some mentioned that some of the VMware services were using a domain account instead of the system account. When I checked my VMware services, the following services were found to be using a domain account instead of the service account:
- VMware VirtualCenter Management Webservices
- VMware VirtualCenter Server
- VMwareVCMSDS
Once I changed the services to the use the service account, I re-ran in the vCenter installation and the install was successfully completed without any errors.
Hope this helps anyone who may have a similar issue.
Regards,
Vishard