Getting a Windows 2000 Domain Controller to replicate after being offline for 60 days...

  • Thread starter Thread starter cfrank
  • Start date Start date
C

cfrank

Ok, here is the deal. The domain controller(s) were actually not
offline for 60 days. But the date acutally got changed on the PDC
emulator, several times. And then all of the sudden all of the domain
controllers were not replicating anymore. I was able to get the
Windows 2003 domain controllers to function again using the registry
key "Allow Replication With Divergent and Corrupt Partner" set to 1.
This worked great for the windows 2003 servers. But, not for the
Windows 2000 servers. My guess is that it just doesn't work for
Windows 2000. So, now I have 11 Windows 2000 domain controllers that
won't replicate anymore. Is there anyway to get these to replicate
again without demoting and repromoting them? I tried increasing the
tombstone life to 180 days but that didn't work. As far as I can tell
the date was changed to May 11th when it was actually Aug 11th. So, I
thought that 180 days would be enough. No luck.
 
Ok, here is the deal. The domain controller(s) were actually
not
offline for 60 days. But the date acutally got changed on the
PDC
emulator, several times. And then all of the sudden all of
the domain
controllers were not replicating anymore. I was able to get
the
Windows 2003 domain controllers to function again using the
registry
key "Allow Replication With Divergent and Corrupt Partner" set
to 1.
This worked great for the windows 2003 servers. But, not for
the
Windows 2000 servers. My guess is that it just doesn't work
for
Windows 2000. So, now I have 11 Windows 2000 domain
controllers that
won't replicate anymore. Is there anyway to get these to
replicate
again without demoting and repromoting them? I tried
increasing the
tombstone life to 180 days but that didn't work. As far as I
can tell
the date was changed to May 11th when it was actually Aug
11th. So, I
thought that 180 days would be enough. No luck.
Click to expand...

you have to be VERY carefull with what you are doing because it may
look like everything is OK, but you could have problems afterwards
with lingering objects....

See
http://www.microsoft.com/technet/pr...ons/4a1f420d-25d6-417c-9d8b-6e22f472ef3c.mspx

The registry "Allow Replication With Divergent and Corrupt Partner" is
used when a DC has exceeded the tombstone lifetime and wants to
replicate. The other DCs simply say "NO WAY!" when it is set to 0.
Before setting it to 1 you should make sure you do not have lingering
objects. (REPADMIN - and see the article above)

The registry "strict replication consistency" is for when a certain DC
detects the existence of lingering object in a replication partner in
a certain partition. If it is set to 0 the DC that does not contain
the lingering will still replicate it in. If it is set to 1 to will
halt the replication with the DC for that partition.

Before doing ANYTHING look at the article mentioned above, take a look
at the event logs. Although it is possible to check for lingering
objects on the DCs that do not repicate and remove them it is SAFER to
demote them and promote them afterwards!

Good luck!
 
Back
Top