Message-
From: [EMAIL PROTECTED]
To: ActiveDir@mail.activedir.org
Sent: 5/22/2005 4:51 AM
Subject: RE: [ActiveDir] Replication failures - lingering objects
When running repadmin /showreps on one of the good DCs I get the
following message only under cn=configuration
Last attempt @ 2005-05-21
, I think it is good you are shooting it.
joe
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Alex
FontanaSent: Saturday, May 21, 2005 10:52 PMTo:
ActiveDir@mail.activedir.orgSubject: RE: [ActiveDir] Replication
failures - lingering objects
When running repadmin
/showreps
@mail.activedir.org
Cc: 'Eric Fleischman'
Subject: RE: [ActiveDir]
Replication failures - lingering objects
Ouch. Hasn't replicated since 1952... That
is certainly interesting. I would say that is a bug somewhere though I guess it
could represent a corrupted LDAP attribute value holding the replication
@mail.activedir.org
Subject: RE: [ActiveDir]
Replication failures - lingering objects
I am confused, the config is the only
partition not replicating? If the DC is not replicating due to being to far out
because of TLS issues then it shouldn't be replicating anything.
Anytime you get into a position like
I am confused, the config is the only partition not
replicating? If the DC is not replicating due to being to far out because of TLS
issues then it shouldn't be replicating anything.
Anytime you get into a position like that, I agree with
Rick, mow the DC down and start over.
joe
From:
Woops,
60day tombstone lifetime, not garbage
collection.
From: Alex Fontana
Sent: Tuesday, May 17, 2005 1:53
PM
To: 'ActiveDir@mail.activedir.org'
Subject: Replication failures -
lingering objects
I have a DC that appears to have had some time synch
problems before I
If youre concerned that there might
be a problem I dont see any real value in taking a chance.
I tend to treat DCs much like tin soldiers. Their purpose
in life is primarily object repository and authN. If the object
repository cant be trusted (possibly out of date) then the authN
Try with repadmin /removelingering object
Or disable the strict replication key on
all domain controllers and re-enable once the objects has been replicated (you
can delete later on if you want to)
Mod the below /d value for enable/disable
of strictrepl key
FOR /F skip=1 usebackq
