white paper VMware vCenter Server 6.0 Deployment Guide (Atttached)

[middleoftheroad]

I was wondering if the post deployment steps for configuring identity sources that start on page 79 of VMware vCenter Server 6.0 Deployment Guide (Attached) are absolutely necessary?

Background :We are planing to do a brand new  appliance (linux) install with an embedded platform services controller.

These post deployment steps seem redundant to step 10 on page 18 in the "vCenter Server Appliance Deployment" Guide" which read . "Select Create a new SSO Domain and enter an administrator vCenter SSO Password; enter an SSO

Domain name such as vsphere.local and an SSO Site name such as a city or physical location name."

[vHaridas]

Hi,

'Configure Identity Sources' step (page 79) is necessary to add Active Directory as Authentication source for vCenter Users.

First Add vCenter Appliance in Active Directory, restart vCenter and then follow steps mentioned in document to add your Active Directory as identity source for user authentication.

Then provide vCenter permission/access to your domain users/groups.

without this, Windows AD users cannot login to vCenter.

Thanks,

Haridas

[unsichtbare]

Joining VCSA to AD domain is NOT the only way of accomplishing the goals here.

It is also possible to add Active Directory as an LDAP source, thereby not creating a dependency on the domain and/or any potential trust issues.