|
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
delims==" %i IN (`netdom query dc`) DO reg add \\%i\HKLM\System\CurrentControlSet\Services\NTDS\Parameters
/v "Strict Replication Consistency" /t REG_DWORD /d 1 /f Thank you and have a splendid day! Kind Regards, Freddy Hartono Windows Administrator (ADSM/NT Security) Spherion Technology Group, For Agilent Technologies E-mail: [EMAIL PROTECTED] From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Fontana I have a DC that appears to have had some time synch
problems before I got here… Subsequently, all other DCs have
discontinued replication for the cn=configuration (per repadmin) with this
DC. My question is; the first event I can see showing replication
problems with this DC is on April 8th, which should mean that
I’m not past the 60 day garbage collection period. It seems to me
that I could modify the reg setting to allow the other DCs to resume
replication and no lingering objects would be reintroduced because the deleted
object info is still present. The offending DC is running Windows 2000
SP3. Any thoughts? TIA -Alex |
- RE: [ActiveDir] Replication failures - lingering ob... freddy_hartono
- RE: [ActiveDir] Replication failures - lingeri... Jorge de Almeida Pinto
- RE: [ActiveDir] Replication failures - lingeri... joe
- RE: [ActiveDir] Replication failures - lingeri... Alex Fontana
- RE: [ActiveDir] Replication failures - lingeri... Jorge de Almeida Pinto
- RE: [ActiveDir] Replication failures - lingeri... Alex Fontana
