Skip to main content
AD Academy
Back to all events
1988Directory Service (DC)Replication & DCsCRITLast updated:

Lingering object — replication halted

What it means

A DC tried to replicate an object already deleted elsewhere. AD stops replication with that partner. Usual cause: the DC was offline longer than the tombstone lifetime (180 days).

When it is normal and when it is suspicious

Never normal — a deleted object came back from a DC that was offline too long.

First steps

  1. 1repadmin /showrepl * /csv — find the lagging partner.
  2. 2repadmin /removelingeringobjects <DC> <SourceDC-GUID> <DN> /advisory_mode — dry run first.
  3. 3A DC offline for over 180 days is rebuilt, never reconnected.

Fields worth checking

FieldWhat to look at
Source DCThe offending DC. Stop replicating from it until cleaned.

Related events

This reference is a starting point for investigation, not a replacement for your organisation's security policy.