Demote non-replicating domain controller

Holdit
Holdit used Ask the Experts™
on
Hello,

I have a domain controller in  brach office that has not replicated in > 60 days. I have corrected site link errors but replication still will not occur and it seems that the only solution is to demote and re-promote the DC.

The problem is that there may be user and computer accounts on this DC that we do not wnat to lose. My reading on this subject suggests that DCPROMO will seek to replicate any changes before demoting, but since replication is the problem to begin with, I have to assume that this won't be possible.

Is there a way to fix this issue without demoting the DC or at else demote the DC without losing the user and computer accounts?

Thanks.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Sounds like you the site DC computer password may have gone stale. Right click on the computer object in ADUC from the parent site and click Reset. Try this before demoting. Verify that your sites and services is still configured correctly. If that fails post your output for "repadmin /syncall".

Author

Commented:
The rest option gives an error because the target obejct is a domain controller.

Output for repadmin/syncall:
* * * * * * * * * *
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\<user>>repadmin /syncall
CALLBACK MESSAGE: Error contacting server 59a2bd22-94e4-4880-af31-a13b4a14594f._
msdcs.<domain> (network error): 1722 (0x6ba):
    The RPC server is unavailable.
CALLBACK MESSAGE: The following replication is in progress:
    From: 2aa0f11f-9736-4fc7-a394-7059edd60b57._msdcs.<domain>
    To  : 1b21f857-97e3-4bce-a4f9-449749cc12ee._msdcs.<domain>
CALLBACK MESSAGE: The following replication completed successfully:
    From: 2aa0f11f-9736-4fc7-a394-7059edd60b57._msdcs.<domain>
    To  : 1b21f857-97e3-4bce-a4f9-449749cc12ee._msdcs.<domain>
CALLBACK MESSAGE: SyncAll Finished.

SyncAll reported the following errors:
Error contacting server 59a2bd22-94e4-4880-af31-a13b4a14594f._msdcs.trinityusa.c
om (network error): 1722 (0x6ba):
    The RPC server is unavailable.
* * * * * * * * * *
Thanks
Top Expert 2014

Commented:
Check the time/date on the affected DC and make sure the firewall is not blocking anything.
Commented:
Problem solved. There were some references to a failed DC with I removed manually. I also reorganised the site connections to create a hub-and-spoke setup.

I was about to have a go at implementing this fix: http://searchwindowsserver.techtarget.com/tip/Quick-fix-for-a-non-replicating-DC , when I noticed that the problem had gone away.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial