RE: Ad 2000 to 2003 but replication question !

Hello Laurent,

Thanks for your reply.

According to your description, here are some options which may be helpful
to remove this 2 objects.

Option 1.

Please try enabling the following registry both on parent and child domain
controller to force replicate again.

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Parameters
Value Name: "Allow Replication With Divergent and Corrupt Partner"
Internal Name: DRA_OVERRIDE_TOMBSTONE_LIMIT
Value Type: REG_DWORD
Value Data: 0x1 (enabled)

Option 2.

Use the "repadmin /removelingeringobjects" tool to remove inconsistent
deleted objects and then resume replication again.

Note: the support tools is need to be installed on the domain controller
firstly. The support tools is in the Windows installation Disc.

Option 3.

If the options above doesn't work, please just use "ADSIEDIT.MSC" utility
on both parent and child domain controller to manually remove the 2 objects.

Please locate the 2 objects with LDAP path you provided and then remove
them.

Hope the issue will be resolved soon. I'm looking forward to your reply.

Thanks a lot.

David Shen
Microsoft Online Partner Support

.

Relevant Pages

  • Re: Ad 2000 to 2003 but replication question !
    ... "Allow Replication With Divergent and Corrupt Partner" ... The support tools is in the Windows installation Disc. ... on both parent and child domain controller to manually remove the 2 objects. ...
    (microsoft.public.windows.server.migration)
  • Re: Ad 2000 to 2003 but replication question !
    ... To give you more information in each domain we have only one DC, so i can't demote the dc in the child domain. ... i have read all the link you give me, but not sur to unterstand at all: I'm OK with the concept of lingering object but all the technotes talk about such trouble in intra domain replication. ... If a domain controller was offline or not replicated with the replication ... this will cause a lot of potential problems in Active Directory ...
    (microsoft.public.windows.server.migration)
  • RE: Ad 2000 to 2003 but replication question !
    ... whether there will be a risk if the inter-domain replication is re-enabled. ... If a domain controller was offline or not replicated with the replication ... this will cause a lot of potential problems in Active Directory ... Demote the domain controller to be member server in child domain ...
    (microsoft.public.windows.server.migration)
  • Re: Ad 2000 to 2003 but replication question !
    ... the parent Domain Controller and child Domain ... because the time since the last replication with this parent domain has ...
    (microsoft.public.windows.server.migration)
  • Replication problems
    ... I have two DC's my secondary has a ton of replication errors. ... The local domain controller has not recently received replication ... To identify the domain controllers by name, install the support tools ... from the following source domain controller. ...
    (microsoft.public.windows.server.active_directory)