I’ve just managed to up upgrade the SSO component of vSphere 5.5 in my lab after an hour of trying.
The issue I kept getting was 1603 error when it got to the LookupService part of the install. The result of the error was a rollback.
“Windows Installer installed the product. Product Name: vCenter Single Sign-On. Product Version: 5.5.0.297. Product Language: 1033. Manufacturer: VMware, Inc.. Installation success or error status: 1603.”
In the end I changed the default site ‘Default-First-Site’ name to ‘Primary-Site’ and the rest of the install completed successfully.
Whether I had a bad SSO config to begin with will depend on if others get a similar issue. For the moment I’m posting this suggested workaround.
Tried this and it did not help in my case. v5.0 to v5.5 upgrade therefore SSO is not installed beforehand.
Thanks for the comment. I should have mentioned the fact it’s a 5.1 upgrade.
This ‘hack’ got me working again but with everything take backups etc. VMWare know about this issue and are working on the solution. It seems to be affecting lots of installations.
I believe they’ll be making the SSO function as an appliance in the future so there is light at the end of the tunnel for SSO.
That point about learning to say no to the wrong projects really hit home for me. In my second year of running my design studio, I took on every tiny request out of pure fear and nearly burned myself out. Setting firmer boundaries felt terrifying at first, but it completely transformed my business and my sanity.