Title: DC "replicating" with deleted DSA object

Nah – no need to.  They will go away by themselves as a normal part of the tombstoning process.  They are marked as deleted, which is just what the DS needs to let it know it’s no longer functioning and should be deleted from any references.

Rick


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ruston, Neil
Sent: Monday, August 08, 2005 9:50 AM
To: '[email protected]'
Subject: [ActiveDir] DC "replicating" with deleted DSA object

 

We have recently re-built and upgraded several DCs from w2k to w2k3. The upgrade is achieved as follows:
1. demote w2k DC
2. build and promote w2k3 DC

Sometimes the h/w in 1 and 2 are different but sometimes the same h/w is used.

Furthermore, sometimes the same name is used in 1 and 2 but not always.

If I now execute "repadmin /showreps" on an existing (bridgehead) w2k DC, I see the following issue:

<snip>
    yyyyy\xxxxxxxxxxxx
DEL:620c0fd7-f4f4-46ce-90ef-099659abcef6 (deleted DSA) via RPC
        objectGuid: a6cb3618-9a77-43a6-9ac3-d753b9b112eb
    zzzzz\aaaaaaaaaaaa (deleted DSA) via RPC
        objectGuid: ce82cc75-1c27-416f-808d-3ac461a17a63
    yyyyy\bbbbbbbbbbbb
DEL:a41088e1-0d66-43e8-8b83-a8986f7f6b2a (deleted DSA) via RPC
        objectGuid: 72c4c974-7dc3-43ae-85aa-b427755983fb
<snip>

Where:
xxxxxxxxxx is a DC which was built temporarily and then demoted several days ago
aaaaaaaaaa is a DC which was re-built (as per above) with the same name
bbbbbbbbbb is a DC which was re-built (as per above) with the same name (in the same site as xxxxxxxxxx)

I have been considering using "repadmin /delete" to remove these incorrect replication connections and wondered if anyone had used such a method before or could offer any alternatives?

Thanks,
neil

==============================================================================
Please access the attached hyperlink for an important electronic communications disclaimer:

http://www.csfb.com/legal_terms/disclaimer_external_email.shtml

==============================================================================

Reply via email to