SSO Domain ID do not match when joining linked mode

[AllBlack]

Hi

SSO sure is a pain in the @$S. I have created two fresh instances of vCenter. All services have been installed individually (thus no simple install).

Both instances are configured for multisite

Before installing second instance I exported SSO data as explained in the KB articles.
I created second instance in the same manner. Pointed SSO to my primary SSO server using multimode.
Once 2nd vCenter was up and running I exported SSO data and imported it on the primary SSO, again as per KB instructions.

Then I tried to join the second instance in linked mode to first instance which fails.
The status.txt and join tool.log file say there is a mismatch in domain ID. Apparently this happens when not using multisite SSO but I have configured that during both installs.

What could be causing this then? I found an article that talks about veryfying ID but for some reason I do not have access

http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&externalId=2050493&sliceId=1&doc...

[raog]

1) Is the firewall configured properly to allow communications between the two ADAM instances on VCs?

2) Was the first SSO installed as primary node and not using "Basic" mode?

3) On the first VC, run the linked mode configuration wizard and see if its showing up as joined already... if yes, isolate that VC and then try the joining operation again.

Regards

Girish

[AllBlack · Accepted solution]

I checked the first VC and that did indeed appear as being part of a joined config. I was not able to isolate it via the configuration editor as that generated an error. I managed to get it joined after I deleted the 2nd VC instance through the ADSI configurator on first instance.
So it seems that when there is an error with joining during setup that it leaves some settings behind that prevents from joining them afterwards.