Interesting question, this
In the first scenario, I configure both sites with Basic SSO:
- If so, how would remote performance compare to say managing a 4.1 remotely in linked mode as we do now?
1. Correct
2. I don't find a comparision chart or an actual performance statistics on this but I also have not come across an issue related with degraded console performance. The closest I could find was the below link, but then again, it does not actually give a counter to state whether console access in vSphere client or Web Client was faster
3. Correct
In the second scenario, I configure Multi-Site with Dallas as Primary SSO:
- In Multi-Site, if the Dallas SSO goes down Dallas is still inaccessible until it is back up correct? (unless you temporarily add that vCenter to another SSO)
The only reason I see to do multi-site is if you are planning to use Linked-Mode and ONLY because it seems to be a prerequisite requirement. The current manual import/export multi-site SSO requirements and other overhead will cause my team to now rethink the benefits Linked Mode. Unless I'm misunderstanding, the SSO topology implementations are very sketchy and I may opt for Basic Mode at all sites until this is more fully cooked?
I do think there are multiple ways in which the second scenerio can play up.
1. Multisite - the "local" access bit above
2. Multisite HA - answers point 3
3. As to point 2, the above two answers might help clear the confusion :-)
So essentially I think what the confusion above is that there are actually three modes as opposed to two you have mentioned.
Let me know if this has helped
a