I’ve been working on a Sharepoint Portal Project for quite a while.
Recently when we enabled Single Sign On, we had an error on the Job Server stating that it cannot locate the domain controller.
After numerous searches on Microsoft KB and Partner KB, i never seem to be able to locate why the heck the problem exists in the first place.
So how, if you’re enabling Single Sign On for your portal farm, and you encounter a problem, check your DNS.
Yes, DNS. You may ask why, simple. The SSO Service looks for your DNS and asks your DNS where your PDC Emulator is.
If the SRV Record for the PDC emulator isn’t pointing to the PDC Emulator, then the setup will fail resulting in that error.
To check if you’re pointing to the right PDC Emulator
Go to your DNS Forward Zone.
Expand a _MCDCS record -> PDC. You should then see a record there. This record needs to be pointing to the correct PDC Emulator. If not, update it. Yes, this is the one that breaks the thing. No idea why.
Then on the infrastruture, we always have multiple DCs for redundancy. Question is, why does it look for the PDC Emulator only, can’t the other DC suffice? This is really against the idea of having Multi-Masters. Anyway, frustrations aside. That costs me a Microsoft ticket which i think isn’t quite fair coz i can’t find this anywhere.
Alright, i’m not a sharepoint expert, so i guess there must be legitimate reason why SSO service is looking for the PDC Emulator.