Guido, This is an interesting suggestion - are you able to offer more detail?
Right now, we have manual bridgeheads in the main hub sites and manual connection objects too. [I plan to remove these in due course after reaching w2k3 FFL.] Are you suggesting that such a manual bridgehead should be removed/replaced in a specific, controlled manner as per the below? Or are you suggesting manual connection objects be created to another DC/GC in the same site before a dynamic bridgehead be removed? I'm not sure I quite follow your steps nor your reasoning :) What's the issue with FRS and vvJoins too? I thought only "partial" vvJoins were performed by DCs with newer SPs and/or w2k3?? Are you able to elaborate or point me to a paper/KB please? Thanks, neil MVP - dir services -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Grillenmeier, Guido Sent: 07 March 2005 19:02 To: [email protected] Subject: RE: [ActiveDir] KCC and Inter-site replication objects that reflects my findings from other DC replacements as well, which is why I tend to move the connection objects to another DC (i.e. in a hub-site with multiple DCs) during the replacement of the first DC. The reason to do so is simply due to FRS and it's requirements to do a full VV-join when the connection object changes to a new replication partner: this can cause quite a bit of file replication traffic, which I rather perform in a controlled manner if there are many connection objects to a single box that is to be replaced. /Guido -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gil Kirkpatrick Sent: Monday, March 07, 2005 6:18 PM To: [email protected] Subject: RE: [ActiveDir] KCC and Inter-site replication objects The dcpromo'd DC will recreate its view of the topology five minutes (by default) after it starts. AFAIK, the other DCs will still wait until the next scheduled time (up to 15 minutes) before re-evaluating the topology, but they will immdieately take into account the fact that the first DC was removed (assuming replication is functional to begin with). -gil -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Shawn Hayes Sent: Monday, March 07, 2005 9:46 AM To: [email protected] Subject: RE: [ActiveDir] KCC and Inter-site replication objects Thanks Gil One more question: We are planning on upgrading (actually dcpromo-ing to demote and then reloading) the DC with most of the inter-site connection objects. I understand demoting the server will remove it from the AD configuration. Will KCC at this point pick a new DC a create new connection objects in a more timely fashion? Thanks again, Shawn Hayes >>> "Gil Kirkpatrick" <[EMAIL PROTECTED]> 03/07/05 11:38AM >>> The KCC runs by default every 15 minutes, but there is another parameter that controls how long a DC has to be unavailable to be dropped from the topology. For intersite topology, the partner has to be non-responsive for 1 attempt and two hours. For intrasite topology, the partner has to be non-responsive for 0 attempts (DC attempts to contact another partner immediately upon failure) and two hours. For the additional ring-optimizing (non-critical) links, it is 1 attempt and two hours. These values are configurable through the registry, although I sure would want to make sure all DCs had the same settings. All the keys are under hklm\system\ccs\services\ntds\parameters IntersiteFailuresAllowed MaxFailureTimeForIntersiteLink (secs) NonCriticalLinkFailuresAllowed MaxFailureTimeForNonCriticalLink CriticalLinkFailuresAllowed MaxFailureTimeForCriticalLink See http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/te chref/en-us/Default.asp?url=/Resources/Documentation/windowsserv/2003/al l/techref/en-us/W2K3TR_repto_how.asp for details -gil Gil Kirkpatrick CTO, NetPro "To fly, flip away backhanded. Flat flip flies straight. Tilted flip curves. Experiment!" -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Shawn Hayes Sent: Monday, March 07, 2005 9:08 AM To: [email protected] Subject: [ActiveDir] KCC and Inter-site replication objects We have KCC and ISTG configured to automatically create site link connection objects. I am looking for information to explain the following situation: The server in our hub site that has most of the Inter-site replication objects defined to it goes down. At what point in time will the KCC / ISTG determine the server is down and create connection objects to one of the other DCs in the hub site. Our hub site has four DCs and we do not have any preferred bridgeheads defined. Thanks in advance, Shawn Hayes List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ ============================================================================== This message is for the sole use of the intended recipient. If you received this message in error please delete it and notify us. If this message was misdirected, CSFB does not waive any confidentiality or privilege. CSFB retains and monitors electronic communications sent through its network. Instructions transmitted over this system are not binding on CSFB until they are confirmed by us. Message transmission is not guaranteed to be secure. ============================================================================== List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
