5 replies
by benwagg
I have had this happen. Check your BDC to see if the Event Log indicates that it has had trouble syncing w/ the PDC. For whatever reason, either the PDC is not recognizing requests from the BDC or the BDC is not recognizing the authority of the PDC's changes to overwrite its copy of the database.
What resolved it for me:
(SysA is original PDC and SysB is original BDC)
1. Synchronize servers
2. Promote SysB (BDC) to PDC (requires reboot)
3. Reboot SysA (PDC) after SysB & demote SysA to BDC when it recognizes there is already a PDC for domain online.
4. Reboot as needed, stir, let simmer...
5. Reverse the process, to promote SysA back to PDC and put SysB back in its place.
One time I had to do this w/ multiple BDCs. This action forces all copies of the domain database to be updated and the BDC to re-recognize the PDC. I don't know yet why the BDC chose to forget who the PDC in charge was, but as I recall, this resolved a couple other flukey problems, too. (continuous master browser elections...)
by nschloss
by itnetman
by nschloss
by nschloss
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending