To "throw" the DC into the alternative site, simply configure the site and site link (initially I would set it with a normal frequency) and then move the DC into that site with dssite.msc. Once it is in there and replicating fine, kick up the period to a week or less. If you have the extra hardware, throw a second DC into the same site. We ran into an occasion where some name mangling became more obvious on the second DC as it started throwing event log errors. I don't recall what they were now as that was close to a year or so ago that I saw it.
I haven't seen orgcheck but I would assume it looks for the key attributes or maybe for the common issues such as the name mangling issue I mentioned above. joe -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Graham Turner Sent: Friday, July 09, 2004 3:55 AM To: [EMAIL PROTECTED] Subject: Re: [ActiveDir] disable_outbound_repl Thanks all for the post replies on the reply highlighting issue of it disabling the inter-site replication but not the intra-site replication this begs the question of how it differentiates between the respective (inter vs intra) requests for replication ??? duly noted on throwing (is that literally ??!!) DC into a site with a long replication frequency; as i recall this process is not totally dynamic to the change of the DC IP address (and restart of the DC or just netlogon ?) and that the directory needs to be manually changed as well ?? the point at which it is then safe to re-establish more timely replication is based on satisfactory testing of the schema update - seems on exchange 2003 we have various tools such as orgcheck etc to test the update of the schema - not too sure what this actually checks ?? any comments on the likelihood of a rogue schema change then being propogated and causing interruption to the directory ?? GT ----- Original Message ----- From: "joe" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, July 09, 2004 3:21 AM Subject: RE: [ActiveDir] disable_outbound_repl > Throw the DC you are using to do the update into a site with a long > replication frequency but not over a week. Do your update, then when you are > ready, do a repadmin /sync on one or more of the connections. > > joe > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Graham Turner > Sent: Wednesday, July 07, 2004 2:00 PM > To: [EMAIL PROTECTED] > Subject: [ActiveDir] disable_outbound_repl > > just doing some planning work for schema update to applying exchange 2003 > forestprep > > have viewed the equivalent docs for adprep on win2k3 - > > i like very much the concept of disabling outbound repl from the schema > master server to which the update is applied using repadmin > /disable_outbound_repl command > > was seeking to understand a little better how this works - > > does it instruct rep partners not to create links to it or does it just > refuse somehow the request for updates > > TIA > > GT > > List info : http://www.activedir.org/mail_list.htm > List FAQ : http://www.activedir.org/list_faq.htm > List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ > > List info : http://www.activedir.org/mail_list.htm > List FAQ : http://www.activedir.org/list_faq.htm > List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ > List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
