During the installation of vCenter Single Sign On (SSO), the installer will attempt to detect the Active Directory (AD) domain for the logged in user and add it as an Identity Source. For the most part, this works fine; however, I’ve run into a couple of instances so far deploying vSphere 5.1 to customers where they either want to add a second AD Identity Source or for one reason or another (running the installer as the local administrator is a typical case), the installer didn’t properly add a non-System-Domain Identity Source. To add a new AD Identity Source: 1. Log in to ...read more