Steve, Thanks for your explanation, it is clearer now for me :) Regards, Yann
________________________________ De: [EMAIL PROTECTED] de la part de Steve Linehan Date: lun. 08/08/2005 19:49 À: ActiveDir@mail.activedir.org Objet : RE: [ActiveDir] DC "replicating" with deleted DSA object Replication Metadata is handled somewhat different than a typical deleted object. The following reference gives more details: http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/TechRef/1465d773-b763-45ec-b971-c23cdc27400e.mspx See the section titled "How Replication Metadata is Preserved in Windows Server 2003" for more information on how/why this occurs. The original idea was to help in situations where we removed a connection and then re-added it back so that less overhead was required. Thanks, -Steve ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of TIROA YANN Sent: Monday, August 08, 2005 11:00 AM To: ActiveDir@mail.activedir.org Subject: RE : [ActiveDir] DC "replicating" with deleted DSA object Hi, Ah..so for my comprehension, these Deleted Objects do not follow the Tombstone process for a deleted objects as users,computers.. (60 days if i remind...) as stated Rick. Does the Stay of Execution state=15days ONLY apply to DCs state (demoted, renamed with same name,etc..?) or any other objects ? Yann ________________________________ De: [EMAIL PROTECTED] de la part de Steve Linehan Date: lun. 08/08/2005 17:16 À: ActiveDir@mail.activedir.org Objet : RE: [ActiveDir] DC "replicating" with deleted DSA object Those connections are in a Stay of Execution state. With SP1 we changed so that we would not attempt to replicate with them but prior to that we will. If your forest has a normal config these will be removed after 15 days. They cause no harm and you can remove them with the /delete option or wait until the stay of execution period, normally 15 days. Thanks, -Steve ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ruston, Neil Sent: Monday, August 08, 2005 9:50 AM To: 'ActiveDir@mail.activedir.org' 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 ==============================================================================
<<winmail.dat>>
