Synchronize BDC with a new PDC 2

[JavaDude]

I have an NT domain called DMN1 with a PDC and a BDC. Recently I got a new PDC named NEWPDC, configured with the same domain name DMN1. When I replaced the old PDC with NEWPDC, the BDC is having problem synchronize with NEWPDC. The error stated: Replication of the BUILTIN Local Group "Rid:0x220" from primary domain controler NEWPDC failed with the following error: Cannot perform this operation on built-in account.

In retrospect, I should have got a new BDC and promote it. But now I am looking for any solutions that may help me avoid installing a new PDC or BDC. Any help will be appreciated.

 

[ShackDaddy]

In retrospect, you should have installed your new server as a BDC and promoted it. 'Should have' may be too mild a phrase. There is nearly no sane way you will be able to make your two servers be on the same domain, any more than you can grab some stranger that shares your last name off the street and make him your brother. It's an issue of DNA, and its an issue of SID. Reinstall your PDC as a BDC of your existing server and hope that you haven't done too much damage by trying to force it.

If you want to hightail it down a different rocky road, rename the domain that the new PDC is on and set up a 2-way trust relationship between your two separate domains that allows users to cross domains freely. Still, it would be far better to reinstall your new server. Dave Shackelford - MCT, MCSE, CCNA, MA
Network Engineer
IRSC, Inc. - A ChoicePoint Company
"One of the advantages of being disorderly is that one is constantly making exciting discoveries." (A. A. Milne)

 

[Jpoandl]

Your right, you should have built a BDC.

I don't know of any other way to resolve you problem except this....

You should rebuild the new server. Build it as a BDC of your existing domain. Once it is part of your existing domain, highlight the new BDC in Server Manager -> go to file and choose "synch with primary controller".

Shut down the PDC.

Then select the NEW backup domain controller you want to promote, and under the View menu, select Promote to Primary Domain Controller.


Here's and MS link:

http://support.microsoft.com/support/kb/articles/Q167/2/48.ASP

 

[ShackDaddy]

Wait a sec! Why are you shutting down the old PDC? Why not let it be naturally demoted as part of the promotion process? If you just shut it down and don't allow its demotion, if it comes back on later as a second PDC, the two PDC's will play chicken and it may not be the new one that wins. Just go with the natural flow and install the new guy as a BDC and then _simply_ promote it. All the rest will nicely fall into place. Dave Shackelford - MCT, MCSE, CCNA, MA
Network Engineer
IRSC, Inc. - A ChoicePoint Company
"One of the advantages of being disorderly is that one is constantly making exciting discoveries." (A. A. Milne)