Announcement

Collapse
No announcement yet.

Lingering Objects

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Lingering Objects

    Hi,

    How can I confirm if I have lingering objects in Active Directory? Is there a utility for this?

    Had an admin take DC's off line with out doing the DCPROMO first. I believed he removed them manually (metadata cleanup) but I want to confirm they are gone.

    After checking "replmon" I noticed changes are being seen by servers not known to me. They're 17 of these servers and not sure what to make of it. The list looks something like this.

    DELETED SERVER #1
    DELETED SERVER #2
    DELETED SERVER #3...and so on and so on the 17 of them.

    TIA guys!

  • #2
    Re: Lingering Objects

    Improper DC demotion does not create lingering objects.

    Lingering objects come from restoring old backups or turning on DCs that have been offline longer than the tombstone lifetime.

    If you had lingering objects you would see the warnings in the event logs because AD Strict Replication (Win2000 SP3+ only) disables replication with a DC that contains lingering objects.

    Comment


    • #3
      Re: Lingering Objects

      Originally posted by Garen View Post
      Improper DC demotion does not create lingering objects.

      Lingering objects come from restoring old backups or turning on DCs that have been offline longer than the tombstone lifetime.

      If you had lingering objects you would see the warnings in the event logs because AD Strict Replication (Win2000 SP3+ only) disables replication with a DC that contains lingering objects.
      Ok, so I can check the logs for lingering objects?

      Comment


      • #4
        Re: Lingering Objects

        Something like this:
        Code:
        Event Type:    Error
        Event Source:    NTDS Replication
        Event Category:    Replication 
        Event ID:    1988
        Date:        07/04/2009
        Time:        12:56:56
        User:        NT AUTHORITY\ANONYMOUS LOGON
        Computer:    DC99
        Description:
        Active Directory Replication encountered the existence of objects in the following partition that have been deleted from the local domain controllers (DCs) Active Directory database.  Not all direct or transitive replication partners replicated in the deletion before the tombstone lifetime number of days passed.  Objects that have been deleted and garbage collected from an Active Directory partition but still exist in the writable partitions of other DCs in the same domain, or read-only partitions of global catalog servers in other domains in the forest are known as "lingering objects". 
         
         This event is being logged because the source DC contains a lingering object which does not exist on the local DCs Active Directory database.  This replication attempt has been blocked.
         
         The best solution to this problem is to identify and remove all lingering objects in the forest.
         
         
        Source DC (Transport-specific network address):
        11159e43-14df-477f-822d-d1fcwad37aww._msdcs.microsoft.com 
        Object:
        CN=2342342131f34f23\0ACD3:333222940-6e48-4ee4-719-6157cfd2437c,CN=12121212,OU=1212121,OU=121212,OU=12121,DC=1212,DC=microsoft,DC=com 
        Object GUID:
        111111111-6e48-111-b719-6157cfd2437c 
         
        User Action:
         
        Remove Lingering Objects:
         
         The action plan to recover from this error can be found at http://support.microsoft.com/?id=314282.
         
         If both the source and destination DCs are Windows Server 2003 DCs, then install the support tools included on the installation CD.  To see which objects would be deleted without actually performing the deletion run "repadmin /removelingeringobjects <Source DC> <Destination DC DSA GUID> <NC> /ADVISORY_MODE". The eventlogs on the source DC will enumerate all lingering objects.  To remove lingering objects from a source domain controller run "repadmin /removelingeringobjects <Source DC> <Destination DC DSA GUID> <NC>".
         
         If either source or destination DC is a Windows 2000 Server DC, then more information on how to remove lingering objects on the source DC can be found at http://support.microsoft.com/?id=314282 or from your Microsoft support personnel.
         
         If you need Active Directory replication to function immediately at all costs and don't have time to remove lingering objects, enable loose replication consistency by unsetting the following registry key:
         
        Registry Key:
        HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Strict Replication Consistency
         
         Replication errors between DCs sharing a common partition can prevent user and compter acounts, trust relationships, their passwords, security groups, security group memberships and other Active Directory configuration data to vary between DCs, affecting the ability to log on, find objects of interest and perform other critical operations. These inconsistencies are resolved once replication errors are resolved.  DCs that fail to inbound replicate deleted objects within tombstone lifetime number of days will remain inconsistent until lingering objects are manually removed by an administrator from each local DC.
         
         Lingering objects may be prevented by ensuring that all domain controllers in the forest are running Active Directory, are connected by a spanning tree connection topology and perform inbound replication before Tombstone Live number of days pass.
        cheers
        Andy

        Please read this before you post:


        Quis custodiet ipsos custodes?

        Comment

        Working...
        X