Ever since vSphere 5.1 launched we’ve been getting a fair number of support calls about Single Sign On, or SSO for short. It is a requirement now, and many of you are getting caught on some aspect of the upgrade/implementation.
We don’t like our customers having to call into support. Not that we don’t love to hear from you, but we’d rather document how to deal with different issues and push the information out to you before you run into them. Then, you don’t have to waste time calling us!
Let’s start with two particularly important KB articles. These are classified as ‘Resolution Paths’. They walk you through an ordered set of steps in resolving a problem. You can read more about resolution path articles here.
- Troubleshooting Single Sign On (SSO) issues in vCenter Server 5.1 (2033137)
- Troubleshooting vCenter Single Sign On when it does not start (2034517)
If those two don’t address your problem, here are a few more resources to help you along your way on the upgrade path. Enjoy!
| Admin and Login |
|---|
| Troubleshooting SSL certificates updates and SSO (2033240) |
Troubleshooting vSphere Web Client login errors (2033253)
|
| Troubleshooting SSO on VCVA (2033338) |
| Updating SSL certificates for vCenter Single Sign On servers behind a load balancer (2034181) |
| Unable to log in to vCenter Server with the vSphere Client (2034798) |
Here are a few more links for good luck:
I’ve been reading the forums, blogs, and tweets about SSO, it seems there are quite a few things that can go wrong during the upgrade or install. This will probably cause us to delay the 5.1 upgrade until the issues are worked out, perhaps when Update 1 ships. I can understand the need for OpenLDAP support, but the implementation should not cause additional complexity and failures during an upgrade from a working 4.x or 5.x system…vCenter is too important to screw up. We are also not too excited about the requirement for yet another database to manage, in addition to vCenter and Update Manager.
Hi RobVM,
The majority of the tweets, blogs and forums that I have seen where people have had problems are due to either not understanding the role of SSO, or not reading the documentation thoroughly first. It’s true that you can get it very wrong and have all sorts of problems, but it’s also true that it can be deployed safely.
I have updated 3 VCenter Servers in a huge corporate environment without encountering issues – once I’d read the docs!
By all means wait for Update1 – it’s not perfect – but by the same token it’s quite possible that when Update 1 is release we can make the same mistakes upgrading!
Hope that helps,
Sam
Looks like we will be holding off on installing 5.1 here at work until 5.1.1.
?