Добрый день .
The event id 1988 will be logged on DC which is not having lingering object.The description of the Event ID 1988 is quite descriptive. It gives the following Information
1. The GUID of the source domain controller from where the lingering objects are coming.
Source DC (Transport-specific network address): c3f32f0e-7eb8-4d5e-a9da-f18ae3931bd7._msdcs.domain.com
2. The DN of the Lingering Object (This piece of information is helpful in determining the location of the lingering object with respect to the naming context – domain partition, configuration partition , global catalog)
Object:
CN=50\0ADEL:80d39a4e-2502-425b-ab85-ccbea79eb100,CN=Deleted Objects,DC=DomainDnsZones,DC=domain,DC=com
3. The event also gives the command that needs to be run to remove lingering objects
Repadmin /RemoveLingeringObjects <Name of the Source DC> <GUID of the DC which do not have the Lingering Objects>
Name of the Source DC: The Event ID 1988 mentions the GUID of the source DC. From this GUID, we need to get the name of that DC
GUID of the DC which do not have the Lingering Objects: DC on which we are getting Event ID 1988is the one on which we do not have the Lingering Objects.Ping the GUID which is mentioned in the Event 1988. This is the GUID of the domain controller which has
Lingering Objects. By pinging the GUID, we will get the name of the domain controller having lingering objects
http://blogs.technet.com/b/glennl/archive/2007/07/26/clean-that-active-directory-forest-of-lingering-objects.aspx
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.If faulty DC is FSMO role holder you need to seize the FSMO on other DC.
А так же
http://technet.microsoft.com/ru-ru/library/cc949134(v=ws.10).aspx#BKMK_1988
Печенкин Николай
