Object lingering


I have multiples Domain controllers, sometime one DC stop communicate  with other DCs. Now I have a lot objects lingering spread at five DC. I want help to found the correct partition from object lingered.

Thank very much
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Skyler KincaidNetwork/Systems EngineerCommented:
You can set the burflags to force replication or you can try to just force replication from your Master DC.
aspenbrAuthor Commented:
I have tried force replication from Master DC to other DC, but haven´t worked. The event viewer show me the message there are objects that need be remove after start the process sync .
aspenbrAuthor Commented:
Source domain controller:
CN=SCS-102470,OU=Computadores SC,DC=inter,DC=corp
Object GUID:
3d5faa05-b702-45f9-8968-06cab0c37921  This event is being logged because the source DC contains a lingering object which does not exist on the local DCs Active Directory Domain Services database.  This replication attempt has been blocked.
 The best solution to this problem is to identify and remove all lingering objects in the forest.
Powerful Yet Easy-to-Use Network Monitoring

Identify excessive bandwidth utilization or unexpected application traffic with SolarWinds Bandwidth Analyzer Pack.

SandeshdubeySenior Server EngineerCommented:
How to Troubleshoot Lingering Objects

Alternately you can also demote & promote the server containg the lingering as sometimes its difficult to remove lingering object either using repadmin /removelingeringobjects or other tool. If lingering objects spreads then its more difficult to tackle them.

You need to forcefully demote the server having lingering object by runnning dcpromo/forceremoval followed by metadata cleanup and promote the server back as DC.If faulty DC is FSMO role holder you need to seize the FSMO on other DC.

Reference link
Forcefull removal of DC:http://support.microsoft.com/kb/332199
Metadata cleanup:http://www.petri.co.il/delete_failed_dcs_from_ad.htm
Seize FSMO role:http://www.petri.co.il/seizing_fsmo_roles.htm

Hope this helps

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
You may also want to check out the ReplDiag tool as it can help with cleaning lingering objects from multiple DCs.  The following blog illustrates its use.
aspenbrAuthor Commented:
Thanks a lot guy .
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.