Remove Lingering Objects In ad Posted on February 14, 2011 by dpejic Ok, command to execut is: 1. I use replmon to find out which server not replicate and have lingering object 2. In "servername" belowe replace with your problematic server 3. After that you need to use GUID (f943c62b-7d26-4504-81e0-2d68bff70d21) of healthy dc from which you wont to synchronize 4. /advisory_mode is only test to see if you do it all right, if everything ok delete /advisory_mode and execut command 5. "dc=DomainDnsZones,dc=yourdomain,dc=com" is partition where i have lingering object, for you maybe is diferent partition repadmin /removelingeringobjects servername f943c62b-7d26-4504-81e0-2d68bff70d21 dc=DomainDnsZones,dc=yourdomain,dc=com /advisory_mode EXAMPLE on Microsoft site: At a command prompt, type the following command, and then press ENTER: Important There must be connectivity between the server that has or might have lingering objects and the server that has an up-to-date, writable replica of the directory partition. repadmin /removelingeringobjects ServerName ServerGUID DirectoryPartition /advisory_mode Term Definition ServerName The DNS name or the distinguished name of the domain controller that has or might have lingering objects. ServerGUID The GUID of a domain controller that has an up-to-date writable replica of the directory partition DirectoryPartition The distinguished name of the domain directory partition that might have lingering objects. For example, DC=RegionalDomainName,DC=ForestRootDomainName,DC=com. Also run the command against the configuration directory partition (CN=configuration,DC=ForestRootDomainName,DC=com), the schema directory partition (CN=schema,CN=configuration,DC=ForestRootDomainName), and any application directory partitions that are hosted on the domain controller you are checking for lingering objects. /advisory_mode logs the lingering objects that will be removed so that you can review them, but it does not remove them. If lingering objects are found, repeat step 1 without /advisory_mode to delete the identified lingering objects from the directory partition. Repeat steps 1 and 2 for every domain controller that might have lingering objects. How to find GUID of server Using the DNS Management MMC Snap-In Open the DNS Management MMC Snap-in located in the Administrative Tools menu. If a shortcut is not present, this will require starting a new MMC console and adding the snap-in manually. Set the focus of the DNS Management snap-in to a DNS server used by the domain controllers. Expand the server to display the nodes Forward Lookup Zones and Reverse Lookup Zones. Expand Forward Lookup Zones to display the zone which contains the domain where the domain controller resides. Traverse the hierarchy of the zone to display the domain that the server is a member of. Expand this node and double-click _msdcs. Each domain controller registers a CNAME record (Alias record)(SCROLLE DOWN IN CONSOLE) in this location identifying its Server GUID. In the right hand pane of the MMC console, locate the name of the server in the Data column and the Server GUID will be identified in the Name column.