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: