Selected options are as follows:
vCenter and Embedded Platform Services Controller
Platform Services Controller
vCenter Server -- Needs a previously installed Platform Service Controller
If we have multiple vCenters -- close to 20+ or more
What are the maximums on how many 1 Service controller can handle all these links under one SSO domain or how many Vcenters / ESXi nodes / Virtual Machines / etc... I thought version 5.x had limitations for vcenters under one SSO domain.
And secondly can you create multiple Platform Service Controllers to prevent an outage if the one Platform Service Controller goes down - where they are in a cluster of sorts.... or balanced
Under SSO configuration if you choose the Embedded Deployment: "vCenter and Embedded Platform Services Controller"
Does the SSO Dmain name: vsphere.local make any difference?
Secondly what is the Site name used for: Default-First-Site
Is this like the default Active Directory Sites and Services... Does it link to AD Sites/Services?
If you choose Default-First-Site does it matter if an individual or standalone vCenter?
If you choose external deployment, does it list all the different sites, and should it be named accordingly - or is all vcenter deployments put under Default-First-Site
Under vCenter Service account
I see it can uyse the Windows Local System Account or specified account.
If you use an External Database - like MS SQL 2012 -- can you still use the Windows Local System account or do you always have to choose Specified service account
When adding OBDC connections for the external database, for vcenter, SRM, and update Manager, do they need to be listed under both x32 and x64 OBDC connection managers