ÇÔ¸Õ¡ÒûÃѺ¡ÒõÑ駤èÒ¡ÒèÓÅͧẺä´àá·ÍÃÕ·Õèãªé§Ò¹ÍÂÙèã¹à¤Ã×Í¢èÒ·ÕèÁÕ¢¹Ò´ãË­è

º·¤ÇÒÁ¹Õé͸ԺÒÂÇÔ¸Õ¡ÒûÃѺ¡ÒõÑ駤èÒ¡ÒèÓÅͧẺ Active Directory 㹡ÒáÓ˹´¤èÒà¤Ã×Í¢èÒ·ÕèÁÕ¢¹Ò´ãË­è

ÊÔè§ÊӤѭ¹ÕéÊèǹ ÇÔ¸Õ ËÃ×ͧҹ»ÃСͺ´éÇ¢Ñ鹵͹·ÕèºÍ¡ÇÔ¸Õ¡ÒÃá¡éä¢ÃÕ¨ÔÊ·ÃÕ ÍÂèÒ§äáçµÒÁ »Ñ­ËÒÃéÒÂáçÍÒ¨à¡Ô´¢Öé¹ËÒ¡¤Ø³»ÃѺà»ÅÕè¹ÃÕ¨ÔÊ·ÃÕäÁè¶Ù¡µéͧ ´Ñ§¹Ñé¹ â»Ã´µÃǨÊͺãËéá¹èã¨ÇèҤسä´é·ÓµÒÁ¢Ñ鹵͹àËÅèÒ¹ÕéÍÂèÒ§ÃÐÁÑ´ÃÐÇѧ ÊÓËÃѺ¡Òûéͧ¡Ñ¹à¾ÔèÁàµÔÁ ãËéÊÓÃͧÃÕ¨ÔÊ·ÃÕ¡è͹·Ó¡ÒûÃѺà»ÅÕè¹ à¾×èÍ·Õè¤Ø³¨ÐÊÒÁÒö¤×¹¤èÒÃÕ¨ÔÊ·ÃÕä´éËÒ¡ÁջѭËÒà¡Ô´¢Öé¹ ÊÓËÃѺ¢éÍÁÙÅà¾ÔèÁàµÔÁà¡ÕèÂǡѺÇÔ¸Õ¡ÒÃÊÓÃͧ¢éÍÁÙÅáÅФ׹¤èÒÃÕ¨ÔÊ·ÃÕ â»Ã´¤ÅÔ¡·ÕèËÁÒÂàÅ¢º·¤ÇÒÁµèÍ仹Õé à¾×èÍ´Ùº·¤ÇÒÁã¹°Ò¹¤ÇÒÁÃÙé¢Í§ Microsoft::¤ÇÒÁÃÙé¤ÇÒÁÊÍ´¤ÅéͧµÑǵÃǨÊͺ (KCC) »ÃѺẺ䴹ÒÁÔ¡â·â¾âÅÂÕ¨ÓÅͧẺ¢Í§¢éÍÁÙÅà¤Ã×Í¢èÒ¢ͧ¤Ø³ àÁ×èÍÁÕà¾ÔèÁ ËÃ×ÍàÍÒÍÍ¡¨Ò¡à¤Ã×Í¢èÒ àÁ×è͵ÑǤǺ¤ØÁâ´àÁ¹äÁè¾ÃéÍÁãªé§Ò¹µÑǤǺ¤ØÁâ´àÁ¹ ËÃ×Í àÁ×èÍÁÕ¡ÒÃà»ÅÕè¹á»Å§¡ÒáÓ˹´àÇÅÒ¡ÒèÓÅͧẺ¢Í§¢éÍÁÙÅ

§Ò¹¢Í§¡Òà KCC ä´éá¡è:

• KCC ·Õè¢Öé¹ÍÂÙè¡Ñºâ·â¾âÅÂբͧà¤Ã×Í¢èÒÂÃкØäÇé â´ÂÇѵ¶Ø Active Directory ÊÃéÒ§Çѵ¶Ø¡ÒÃàª×èÍÁµèÍ·Õèãªé㹡ÒáÓ˹´¡ÒáÒèÓÅͧẺ¢Òà¢éÒ áÅТÒÍÍ¡·ÕèµÑǤǺ¤ØÁâ´àÁ¹:
  
  
  • ÊÓËÃѺáËÅè§ÀÒÂã¹ä«µìà´ÕÂǡѹ ¢Òà¢éҡѺµÑǤǺ¤ØÁâ´àÁ¹ KCC ¡ÓÅѧàÃÕ¡ãªé
  • ¢ÒÊÓËÃѺáËÅ觷ÕèÁÒã¹ä«µì·ÕèᵡµèÒ§¡Ñ¹ à¢éÒä»Âѧ䫵ì·Õè KCC ¡ÓÅѧ·Ó§Ò¹ ¶éÒµÑǤǺ¤ØÁâ´àÁ¹ KCC ¡ÓÅѧàÃÕ¡ãªé interSiteTopologyGenerator elected ÊÓËÃѺ䫵ì¹Ñé¹
• á»Å§Çѵ¶Ø Microsoft Windows NT ä´àá·ÍÃÕºÃÔ¡Òà Connection (ntdsConnection) ·Õè ¡Ó˹´ KCC áÅÐ ¡Ó˹´¼Ùé´ÙáÅ㹡ÒõÑ駤èҤ͹¿Ô¡à¢éÒ㨠â´Ââ»Ãá¡ÃÁ¡ÒèÓÅͧẺ¢Í§ºÃÔ¡ÒÃä´àá·ÍÃÕ (DS)

â´Â¤èÒàÃÔèÁµé¹ áµèÅЧҹàËÅèÒ¹Õé¨Ð´Óà¹Ô¹¡Ò÷ء 15 ¹Ò·Õ ÊÓËÃѺ¢éÍÁÙÅà¾ÔèÁàµÔÁà¡ÕèÂǡѺ¡Òà KCC â»Ã´´Ùº··Õè¨ÓÅͧẺä´àá·ÍÃÕ·Õèãªé§Ò¹ã¹·ÃѾÂÒ¡Ã Kit ¡Òà Windows 2000

µÑÇÍÂèÒ§:

㹡ÒáÓ˹´ºÒ§ä«µì·ÕèÁÕ¢¹Ò´ãË­è¤èÒ»ÃСͺ´éÇÂ䫵ì¨Ó¹Ç¹ÁÒ¡ â´àÁ¹¨Ó¹Ç¹ÁÒ¡ ËÃ×Í䫵ì betweens ¡Ãкǹ¡ÒüÅÔµËÅÒ KCC ·Õè inter-site ´Óà¹Ô¹ªéÒ ·ÕèãªéÁÒ¡à¡Ô¹¡ÇèÒ»ÃÔÁÒ³µèÍ˹èÇ»ÃÐÁÇżšÅÒ§ (CPU) àÇÅÒáÅÐ˹èǤÇÒÁ¨Ó·ÃѾÂÒ¡Ã

¶éÒ D ¤×Í ËÁÒÂàÅ¢¢Í§â´àÁ¹ã¹à¤Ã×Í¢èÒ¢ͧ¤Ø³ S ¤×Í ¨Ó¹Ç¹¢Í§ä«µìã¹à¤Ã×Í¢èÒ¢ͧ¤Ø³ áÅШҡ¹Ñé¹ ¤Ø³ÊÒÁÒöÅÐàÇé¹Êèǹ·ÕèàËÅ×ͧ͢º·¤ÇÒÁ¹Õé

µÒÃÒ§µèÍ仹ÕéáÊ´§àÇÅÒ¡ÒôÓà¹Ô¹¡ÒÃáÅеÑÇàÅ¢¢Í§»ÃÔÁÒ³¡ÒÃãªé˹èǤÇÒÁ¨ÓÊÓËÃѺ KCC inter-site ¡ÒÃàÃÕ¡ãªé㹡ÒáÓ˹´¤èÒÎѺ áÅÐ spoke ËÅÒ¡ËÅÒ»ÃѺäÁèÁÕ»ÃÐÊÔ·¸ÔÀÒ¾¡Ò÷ӧҹ¤èÒãªé áµèÅÐ䫵ì»ÃСͺ´éǵÑǤǺ¤ØÁâ´àÁ¹ÊÓËÃѺâ´àÁ¹à´ÕÂÇáÅÐá¤çµµÒÅçÍ¡Êèǹ¡ÅÒ§ â´àÁ¹¤×Í dispersed à·èÒ¢éÒÁä«µì ¡ÒÃàª×èÍÁ⧡ÒÃàª×èÍÁâ§䫵ì·ÕèÍѵâ¹ÁѵԶ١à»Ô´ãªé§Ò¹ ¡ÒûÃÐàÁÔ¹à¡Ô´¢Öé¹ã¹¡Òà Xeon III Pentium Intel ·Õè 500 MHz ´éÇ 1 ¡Ô¡Ð亵ì (GB) ¢Í§ÊØèÁ¡ÒÃà¢éҶ֧˹èǤÇÒÁ¨Ó (RAM) ãªé˹èǤÇÒÁ¨ÓÃÇÁ¶Ö§¡ÒÃᤰҹ¢éÍÁÙÅ »ÃÔÁÒ³¡ÒÃãªé˹èǤÇÒÁ¨Ó¨ÐµèÓŧº¹¤ÍÁ¾ÔÇàµÍÃì·ÕèÁÕ˹èǤÇÒÁ¨Ó¡ÒÂÀÒ¾·Õè¹éÍ¡ÇèÒ

The formula for the execution time is:You can determine how long the KCC runs in your existing configuration using the Active Directory Sites and Services snap-in:

1. Determine which domain controller in the site is the current inter-site topology generator by viewing the properties of the NTDS Site Settings object.
2. Time the execution of the KCC on that domain controller:
   
   
   1. ¤ÅÔ¡¢ÇÒ¡ÒõÑ駤èÒ ntds.
   2. ¤ÅÔ¡Check Replication Topology.

Also, you can monitor the execution time of the KCC on an on-going basis by using Registry Editor to view the following registry key:Change the "1 Knowledge Consistency Checker" value to a value of 3 or greater.

With this value set to 3 or greater, the KCC will log events 1009 and 1013 to signify the beginning and end of the check.

Recommendations

If your configuration does not satisfy the above criteria, then use the appropriate method:

Reduce Use of Site-Link Bridges in Your Site Configuration

This option works well in typical hub and spoke configurations by reducing the number of potential routes between sites.

Automatic site-link bridging indicates the entire network is fully Internet Protocol (IP) routed. In this situation, any computer in a given site can communicate over IP with any computer in any other site. Automatic site-link bridging is enabled for both the IP and Simple Mail Transport Protocol (SMTP) inter-site transports by default. Disabling this feature requires that you add explicit site-link bridge objects where needed. Site-link bridges are necessary only if a particular site contains a domain controller of a domain that is not present in any adjacent site, but another domain controller of that domain does occur in other sites in the forest. An adjacent site is defined to be any site included in any site link containing the site in question. Most configurations do not require the use of site-link bridges, because any site holding a domain controller of a given domain that occurs in more than one site is almost always adjacent to at least one other site containing a domain controller of the same domain.

If KCC is unable to directly or transitively connect all the sites containing domain controllers of a particular domain after you disable automatic site-link bridging, the KCC will log event 1311.

µÑÇÍÂèÒ§:

The Directory Service consistency checker has determined that either:

1. There is not enough physical connectivity published by using the Active Directory Sites and Services Manager to create a spanning tree connecting all the sites in the forest.
2. Replication cannot be performed with one or more critical servers for changes to propagate across all sites. This is most often due to the servers being unreachable.

To resolve issue A, use the Active Directory Sites and Services Manager to do one of the following:

• Publish sufficient site connectivity information such that the computer can infer a route by which this partition can reach this site. This option is preferred.
• Add an ntdsConnection object to a domain controller that contains the partition domain controller=europe,domain controller=mycorp,domain controller=com in this site from a domain controller that contains the same partition in another site.

To resolve issue B, examine the current event log to determine which server or servers could not be contacted by the KCC.

To disable automatic site-link bridging:

1. Double-click the Active Directory Sites and Services snap-in.
2. Right-click the IP transport object, and then click¤Ø³ÊÁºÑµÔ.
3. In the Inter-Site Transports container, click the appropriate check box to clear it, and then clickµ¡Å§.

ÁÕÂѧ¤§¢Õ´¨Ó¡Ñ´¡ÒõÑ駤èҤ͹¿Ô¡·Õè KCC ÊÒÁÒö¤Ó¹Ç³â´ÂÍѵâ¹ÁѵÔâ·â¾âÅ¢éÍ inter-site ÂÕ áÁéÇèÒ¨Ðàª×èÍÁâ§䫵ìäÁèàª×èÍÁ⧡ÓÅѧ¶Ù¡ãªé µÒÃÒ§µèÍ仹ÕéáÊ´§àÇÅÒ¡ÒôÓà¹Ô¹¡ÒÃáÅеÑÇàÅ¢¢Í§»ÃÔÁÒ³¡ÒÃãªé˹èǤÇÒÁ¨ÓÊÓËÃѺ KCC inter-site ·Õè¡ÓÅѧàÃÕ¡ãªé㹡ÒáÓ˹´¤èÒÎѺ áÅÐ spoke ËÅÒ¡ËÅÒ áµèÅÐ䫵ì»ÃСͺ´éǵÑǤǺ¤ØÁâ´àÁ¹¢Í§â´àÁ¹à´ÕÂÇáÅÐá¤çµµÒÅçÍ¡Êèǹ¡ÅÒ§ (GC) â´àÁ¹¤×Í dispersed à·èÒ¢éÒÁä«µì ¡ÒÃàª×èÍÁ⧡ÒÃàª×èÍÁâ§䫵ì·ÕèÍѵâ¹ÁѵԶ١»Ô´ãªé§Ò¹ áÅкÃÔ´¨ìàª×èÍÁâ§䫵ìäÁèä´é¡Ó˹´äÇé ¡ÒûÃÐàÁÔ¹à¡Ô´¢Öé¹ã¹¡Òà Xeon III Pentium Intel ·Õè MHz 500 ÁÕ ram ¢¹Ò´ 1 GB ¡ÒôÓà¹Ô¹¡ÒäÃÑ駺¹µÑÇ»ÃÐÁÇżšÒà II Intel Pentium 200 MHz à»ç¹à¡ÕèÂǡѺ¤ÙèàËÅèÒ¹Ñé¹áÊ´§ ãªé˹èǤÇÒÁ¨ÓÃÇÁ¶Ö§¡ÒÃᤰҹ¢éÍÁÙÅ »ÃÔÁÒ³¡ÒÃãªé˹èǤÇÒÁ¨Ó¨ÐµèÓŧº¹¤ÍÁ¾ÔÇàµÍÃì·ÕèÁÕ˹èǤÇÒÁ¨Ó¡ÒÂÀÒ¾·Õè¹éÍ¡ÇèÒ

ÊÙµÃÊÓËÃѺàÇÅÒ¡ÒôÓà¹Ô¹¡ÒÃÊÓËÃѺ䫵ì´ÒÇà·ÕÂÁ¤×Íâ´Â:ËÁÒÂàÅ¢¢Í§â´àÁ¹ÁÕËÁÒÂàÅ¢¢Í§â´àÁ¹ áÅШӹǹ¢Í§ä«µì¨Ó¹Ç¹¢Í§ä«µìä´é

ÊÙµÃÊÓËÃѺ䫵ìÎѺ¤×Í:

àÃÕ¡ãªé KCC Inter-site à·èÒ¹Ñé¹ã¹ÃÐËÇèÒ§»Ô´ªÑèÇâÁ§ÊÙ§ÊØ´

µÑÇàÅ×Í¡¹Õé·Ó§Ò¹àÁ×èͤÍÁ¾ÔÇàµÍÃìÁÕªèͧàÊÕºẺàÇÅÒàÁ×èͧҹà¾Õ§àÅ硹éÍ¡ÓÅѧàÊÃç¨àÃÕºÃéÍ áÅÐ KCC inter-site ¡ÒÃàÃÕ¡ãªé·ÓãËé¾Í´ÕÀÒÂ㹪èͧàÊÕº¤ÃÑ駹Õé´éÇ ෤¹Ô¤¹Õé¨Ðâ´Â»¡µÔ¨Ðãªé੾ÒÐàÁ×èÍãªé¡ÒÃàª×èÍÁ⧡ÒÃàª×èÍÁâ§䫵ìÁÕÍÂÙè¶Ù¡Å´ áÅÐàÇÅҢͧ¡ÒôÓà¹Ô¹¡ÒÃËÃ×Í¡ÒÃãªé˹èǤÇÒÁ¨Ó¢Í§ KCC Âѧ¤§ ÁջѭËÒã¹ÃÐËÇèÒ§àÇÅÒ·Ó§Ò¹ÊӤѭ

KCCs ã¹ä«µì·Õè¡Ó˹´ãËéÊÒÁÒö¡Ó˹´¤èÒ¡ÒûԴãªé§Ò¹à©¾ÒÐâ·â¾âÅÂÕ inter-site ¤Ó¹Ç³ ¡ÒÃÃÑ¡ÉÒ¤ÇÒÁÊÒÁÒö㹡ÒõͺʹͧµèÍ¡ÒÃà»ÅÕè¹á»Å§¤ÇÒÁµéͧ¡ÒèÓÅͧẺÀÒÂã¹ä«µì¢Í§µ¹àͧ ¡Òäӹdz¡ÒÃâ·â¾âÅÂÕ inter-site áÅéÇÍÒ¨ re-enabled ³àÇÅÒÃкØÇѹ·Õèà¾Ô觹ҹ¾Í KCC ã¹ä«µìà¾×èÍÃѹ¡ÒõÃǨÊͺ inter-site áÅÐÊÒÁÒöáÅéǶ١»Ô´ãªé§Ò¹ÍÕ¡¤ÃÑé§

àÁ×èÍ¡ÒõÃǨÊͺâ·â¾âÅÂÕ inter-site ¶Ù¡»Ô´ãªé§Ò¹ÊÓËÃѺ䫵ìºÒ§ä«µì 䫵ì¹Ñ鹨ÐäÁèµÍºÊ¹Í§µèÍ¡ÒÃà»ÅÕè¹á»Å§ã¹â·â¾âÅÂÕ·Õè inter-site ¶éÒ˹Öè§ ËÃ×Í·Ñ駤Ùè¨ÓÅͧẺÊÓËÃѺ¡ÒÃàª×èÍÁµèÍ inter-site ·Ñé§ËÁ´·Õè·Ó«éÓã¹â´àÁ¹·ÕèÃкØäÁèÁÕ äÁèÁÕ adaptation KCC Íѵâ¹ÁѵÔä»ÂѧáËÅ觢éÍÁÙÅãËÁèËÃ×Í»ÅÒ·ҧ¨Ðà»ç¹àÊÃç¨ÊÁºÙó쨹¡ÇèÒµÑǤǺ¤ØÁâ´àÁ¹·ÕèÁÒ¡ÅѺÍ͹äŹì ËÃ×ÍÊèǹ inter-site ¢Í§ KCC àÃÕ¡ãªéÍÕ¡¤ÃÑé§

ËÁÒÂà˵Ø:: ¼Ùé´ÙáÅÃкºÊÒÁÒöà¾ÔèÁ¡ÒÃàª×èÍÁµèÍã¹¢³Ð·Õè inter-site KCC ¶Ù¡»Ô´ãªé§Ò¹´éǵ¹àͧ

¡ÒûÃÐàÁÔ¹ÇèÒµÑÇàÅ×Í¡¹Õéà»ç¹ÊÁ¨Ãԧ㹡ÒáÓ˹´¤èҢͧ¤Ø³ ¡è͹¡Ó˹´¤ÇÒÁÂÒÇ KCC ãªé㹡Ò÷ӧҹã¹ÊÀÒ¾áÇ´ÅéÍÁ¡Ò÷ӧҹ¢Í§¤Ø³ËÃ×ÍäÁè áÅéÇ ´ÙÇèÒ ÁÕºÅçÍ¡àÇÅÒº¹µÑǤǺ¤ØÁâ´àÁ¹Ë¹Öè§ã¹áµèÅÐ䫵ìà¾×èÍ¡ÒÃãËéàËÁÒÐÊÁ¡Ñº¤ÇÒÁµéͧ¡ÒÃ˹èǤÇÒÁ¨ÓáÅÐàÇÅÒ ¤Ø³äÁè¨Óà»ç¹ÊÓËÃѺÊèǹ inter-site ¢Í§ KCC ·Óã¹ä«µì·Ñé§ËÁ´ã¹àÇÅÒà´ÕÂǡѹ

àÁ×è͵éͧ¡ÒáÓ˹´µÒÃÒ§àÇÅÒ¡Òà KCC inter-site ãªé¤ÍÁâ¾à¹¹µì¢Í§µÑÇ¡Ó˹´àÇÅÒ§Ò¹¡ÒèѴ¡Ó˹´¡Òà executions ¢Í§ "wscript /b runkcc.vbs" (ʤÃÔ»µìã¹ÃٻẺ¢éͤÇÒÁÍÂÙè㹺·¤ÇÒÁ¹Õé) ÊÓËÃѺ¢éÍÁÙÅà¾ÔèÁàµÔÁà¡ÕèÂǡѺ¡ÒáÓ˹´àÇÅÒ§Ò¹ ÍéÒ§ÍÔ§¶Ö§ËÑÇ¢é͵ÑÇ¡Ó˹´àÇÅÒ§Ò¹ã¹ÇÔ¸Õãªé¢Í§ Windows 2000 Runkcc.vbs ¨Óà»ç¹µéͧãªéà¤Ã×èͧÁ×ÍʹѺʹعã¹â¿Åà´ÍÃì Support\Tools 㹫մÕÃÍÁ Windows 2000 ãËéµÔ´µÑ駺¹¤ÍÁ¾ÔÇàµÍÃì¹Õé¶Ù¡àÃÕ¡ãªé

»Ô´¡ÒÃãªé§Ò¹ KCC Inter-Site ·Ñé§ËÁ´ ¡ÒáÓ˹´¤èÒ¡ÒÃàª×èÍÁµèÍ´éǵ¹àͧ

µÑÇàÅ×Í¡¹Õé·Ó§Ò¹´Õ㹡ÒõÑ駤èҤ͹¿Ô¡ spoke ÎѺ·Ó§Ò¹»¡µÔ «Öè§â´Â·ÑèÇ件١ãªé੾ÒÐàÁ×èÍÊͧÇÔ¸Õ¡è͹˹éÒ¹ÕéäÁèä´éà»ç¹µÑÇàÅ×Í¡·ÕèÊÒÁÒö â´Â੾ÒÐÍÂèÒ§ÂÔè§ã¹¡ÒáÓ˹´¤èÒ´éǾѹ¢Í§ä«µì

àÁ×èÍâ·â¾âÅÂÕ inter-site Íѵâ¹ÁѵԶ١»Ô´ãªé§Ò¹·Ñé§ËÁ´ ¨Ð¡ÅÒ·ÕèÃѺ¼Ô´ªÍº¢Í§¼Ùé´ÙáÅàÁ×è͵éͧ¡ÒÃÊÃéÒ§Çѵ¶Ø¡ÒÃàª×èÍÁµèÍà¾×èÍãËéá¹èã¨ÇèÒ ¢éÍÁÙÅ·Õè¨ÓÅͧẺÂѧ¤§äËżèÒ¹¿ÍàÃʵì·ÓẺ¨ÓÅͧ inter-site ·Õè¨Óà»ç¹ â´Â·ÑèÇä» ÅÙ¡¤éÒ·Õè ÁÕ䫵ìà¾Õ§¾Í¡Ñº surpass ¨Ó¡Ñ´ KCC employ topologies à¤Ã×Í¢èÒÂÎѺ áÅÐ spoke àª×èÍÁµèÍ headquarters ·ÕèºÃÔÉÑ· ÁÕ䫵ìÊӹѡ§Ò¹ÊÒ¢Ò homogeneous ¨Ó¹Ç¹ÁÒ¡ symmetry ¹Õé simplifies ¡Ãкǹ¡ÒÃä´éÍÂèÒ§ÁÒ¡

¡è͹·Õè¨ÐÊÃéÒ§Çѵ¶Ø¡ÒÃàª×èÍÁµèͧ͢¤Ø³â´ÂäÁèµéͧ¡ÒäÇÒÁªèÇÂàËÅ×ͧ͢ KCC ÁÕËÅÒ¨ش¾Ô¨ÒóÒ:

• ¤ÇÒÁÅéÁàËÅǢͧà«ÔÃì¿àÇÍÃì ãËé¾Ô¨ÒóҡÒÃà¡Ô´¢Öé¹ã¹¡Ã³Õ·ÕèµÑǤǺ¤ØÁâ´àÁ¹ BR1 ã¹ä«µìÊӹѡ§Ò¹ÊÒ¢Òàª×èÍÁµè͡ѺµÑǤǺ¤ØÁâ´àÁ¹ HQ1 ã¹ä«µì¢Í§ºÃÔÉÑ·ÎѺ áÅÐ HQ1 undergoes ¢éͼԴ¾ÅÒ´¢Í§ÎÒÃì´áÇÃì »Ñ­ËÒ´éÒ¹¾Åѧ§Ò¹ ËÃ×ͺҧÍ×è¹ æ à˵ءÒóìÃعáç àÁ×èÍÁÕ¡ÒÃãªéâ·â¾âÅÂÕ inter-site Íѵâ¹ÁÑµÔ KCC ·ÕèãªéàÇÅÒÀÒÂãµé´ÙáÅ¡ÒÃà¾ÔèÁ¡ÒÃàª×èÍÁµèÍÍÔ¹à¾ÔèÁàµÔÁà¾×èÍ·Óà»ç¹¡ÒêÑèǤÃÒÇ«éÓ¨Ò¡µÑǤǺ¤ØÁâ´àÁ¹Í×è¹ã¹ä«µì¢Í§ºÃÔÉÑ·ÎѺ¨¹¡ÇèÒ HQ1 Ê觡ÅѺ¤èÒẺÍ͹äŹì äÁè ÁÕ¡ÒÃÊÃéÒ§â·â¾âÅÂÕ inter-site Íѵâ¹ÁÑµÔ à¾×èÍãËéá¹èã¨ÇèÒ ¡ÒèÓÅͧẺ¹Ñé¹Âѧ¤§à¡Ô´¢Öé¹ã¹¡Ã³Õ¢Í§¤ÇÒÁÅéÁàËÅǢͧà«ÔÃì¿àÇÍÃì «éÓ«é͹¡ÒÃàª×èÍÁµè͵éͧÁÕ¡Ó˹´ ¡Ó˹´Êͧ¡ÒÃàª×èÍÁµèÍ¢Òà¢éÒà¾×èÍ BR1 ¨Ò¡ HQ1 áÅШҡ HQ2 If there are two domain controllers in the branch office, BR1 and BR2, then the second connection should be from HQ2 to BR2. This allows updates to be replicated from the corporate hub site in the event that one of the two branch office domain controllers fails.
  
  Redundant connections defined in this manner may force the same Active Directory updates to be replicated more than once unless the IP transport is being used and all connections inbound to the site have the same destination domain controller within the site. When using the SMTP transport or multiple destination domain controllers, the replication schedule should be interleaved such that the updates from one source are received, applied, and replicated within the destination site before the request to the second source is made. Extending the example above, the first connection might replicate on odd hours and the second connection replicate on even hours.
• Global Catalog placement. If a site contains GCs, one or more of the GCs must be used for replication to and from the site. If this is not done, then GCs will not remain synchronized.
• Domain placement. If domain controllers of a particular domain are spread out over multiple sites, one or more domain controllers of that domain must be used for replication with other domain controllers of that same domain. This ensures that domain data is replicated across all domain controllers of that domain. It is not sufficient for a domain A domain controller in site 1 to replicate solely with a domain B GC in site 2 if site 2 contains a domain controller for domain A. Because the domain B GC has only a subset of the attributes for objects in domain A, it cannot act as a conduit to replicate attributes not in this set between the domain A domain controllers.
• Load balancing. Distribute the inbound and outbound replication load. For example, if you have 100 domain controllers in your corporate hub site and 1000 branch offices with 1 domain controller each, you do not want to configure all 1000 branch office domain controllers to replicate from the same domain controller in your hub site. Instead, load balance such that each domain controller in the corporate hub communicates with 10 branch office sites. Since only one inbound replication can occur at a time and communication with branch office sites is often over slow wide area network (WAN) links, failing to load balance will not only increase the CPU and memory load on the hub site domain controller, but this may also result in very large backlogs of data to replicate.

¡ÒÃàÃÕ¡ãªé¤ÃÑé§à´ÕÂǢͧ KCC ÂѧÊÒÁÒöãªéà¾×èÍÊÃéÒ§¡ÒÃàª×èÍÁµèÍ·ÕèÊÒÁÒö¶Ù¡ adapted ¼Ùé´ÙáÅáÅéÇàÃÔèÁµé¹ ¶éÒ KCC ·Õè inter-site äÁèµéͧ¡ÒÃÃѹà»ç¹ÃÐÂÐ æ ËÅѧ¨Ò¡¹Ñé¹ ¨Ò¡¹Ñé¹¼Ùé´ÙáÅÃкºµéͧ¡Ó˹´¡ÒèÓÅͧẺà¾ÔèÁàµÔÁ㹡ÒÃàª×èÍÁµèÍà¾×èÍãËé¨ÓÅͧẺ¨Ð·Ó§Ò¹ã¹¡Ã³Õ¢Í§¤ÇÒÁÅéÁàËÅǢͧµÑǤǺ¤ØÁâ´àÁ¹µé¹·Ò§·ÕèÃÐºØ â´Â¡ÒÃàª×èÍÁµèÍáá ¶éÒÁÕ¡ÒÃàª×èÍÁµèÍ·ÕèÁÕÍÂÙè·Ñé§ËÁ´ÅéÁàËÅÇ áÅÐäÁèÁÕ re-run KCC ·Õè inter-site ¼Ùé´ÙáÅÃкºµéͧàª×èÍÁµèÍâ´ÂµÃ§¡ÑºµÑǤǺ¤ØÁâ´àÁ¹»ÅÒ·ҧ áÅÐÊÃéÒ§¡ÒÃàª×èÍÁµè͡ѺµÑǤǺ¤ØÁâ´àÁ¹·ÕèäÁèÊÒÁÒöà¢éÒ¶Ö§ 㹡ÒáÓ˹´¤èÒ´éÇ volatility ÊÙ§ (àÁ×è͵ÑǤǺ¤ØÁâ´àÁ¹µé¹·Ò§·Õè´Õ·ÕèÊØ´·Õè¨ÐäÁè¾ÃéÍÁãªé§Ò¹ã¹ºÒ§¤ÃÑé§ÊÓËÃѺÃͺÃÐÂÐàÇÅÒ¤ÇÒÁÂÒǢͧàÇÅÒà¹×èͧ¨Ò¡¤ÇÒÁÅéÁàËÅǢͧà¤Ã×Í¢èÒÂ) ¨Ðá¹Ð¹Óä´éÁÒ¡¡ÇèÒ˹Ö觡ÒÃàª×èÍÁµè;ÔàÈÉ

Runkcc.vbs (VBScript to Trigger the One-time Run of the KCC)

Microsoft áÊ´§µÑÇÍÂèÒ§¡ÒÃà¢Õ¹â»Ãá¡ÃÁà¾×èÍ»ÃСͺ¡ÒÃ͸ԺÒÂà·èÒ¹Ñé¹ áÅÐäÁèÁÕ¡ÒÃÃѺ»ÃСѹ äÁèÇèÒâ´ÂªÑ´á¨é§ËÃ×Íâ´Â¹Ñ ·Ñ駹ÕéÃÇÁ¶Ö§ áµèäÁè¨Ó¡Ñ´à¾Õ§¡ÒÃÃѺ»ÃСѹâ´Â¹ÑÂã¹àÃ×èͧ¡Òë×éÍ¢ÒÂËÃ×ͤÇÒÁàËÁÒÐÊÁÊÓËÃѺÇѵ¶Ø»ÃÐʧ¤ì੾ÒÐ º·¤ÇÒÁ¹Õé͹ØÁÒ¹ÇèҤسÁÕ¤ÇÒÁ¤Øé¹à¤Â¡ÑºÀÒÉÒ¡ÒÃà¢Õ¹â»Ãá¡ÃÁ·ÕèáÊ´§ÍÂÙè ÃÇÁ·Ñé§à¤Ã×èͧÁ×͵èÒ§æ ·Õèãªé㹡ÒÃÊÃéÒ§áÅÐá¡é¨Ø´º¡¾Ãèͧ¡Ãкǹ¡Òà ÇÔÈǡýèÒÂʹѺʹع¢Í§ Microsoft ÊÒÁÒöªèÇÂ͸ԺÒÂà¡ÕèÂǡѺ˹éÒ·Õè¡ÒÃãªé§Ò¹¢Í§¡Ãкǹ¡ÒÃ੾ÒÐä´é áµè¨ÐäÁè»ÃѺà»ÅÕè¹µÑÇÍÂèÒ§àËÅèÒ¹Õéà¾×èÍãËéÁÕ˹éÒ·Õè¡ÒÃãªé§Ò¹·Õèà¾ÔèÁ¢Öé¹ ËÃ×ÍÊÃéÒ§¡Ãкǹ¡ÒÃã´æ à¾×è͵ͺʹͧ¤ÇÒÁµéͧ¡ÒÃÍÂèÒ§ã´ÍÂèҧ˹Ö觢ͧ¤Ø³â´Â੾ÒÐ'*/ runkcc.vbs
'*/
'*/ Parameters:<none></none>
'*/ Purpose: When run on a domain controller, this script makes the local domain controller the Inter-Site
'*/ Topology Generator for its site, enables inter-Site topology generation temporarily if it is disabled,
'*/ runs the KCC topology generation process, and disables inter-site topology generation if it was
'*/ configured so to begin with.
'*/
'*/

ON ERROR RESUME NEXT

Call ExecuteKCC()

Public Sub ReportError ()

'tell the user the error
wscript.Echo "The following error occurred: (" + cstr(hex(err.number)) +") " + cstr(err.description)

End Sub

Public Sub ExecuteKCC ()

ON ERROR RESUME NEXT

wscript.echo "Loading functions for use by this script..."
set dll=createobject("iadstools.DCFunctions")
if err.number <> 0 then ReportError:WScript.Quit
dll.enabledebuglogging 1

'get the local box name
wscript.echo "1> Connecting to local machine..."
set localMachine=GetObject("LDAP://localhost/rootdse")
if err.number <> 0 then ReportError:Wscript.Quit
ServerName=localmachine.get("dnsHostName")
if err.number <> 0 then ReportError:WScript.Quit
wscript.echo "2> Found local machine " + ucase(ServerName)

'get the config NC
configNC=localMachine.get("configurationNamingContext")
if err.number <> 0 then ReportError:Wscript.Quit
wscript.echo "3> Configuration Naming Context is: " + configNC

'get the SiteName of this box
domaincontrollerSiteName=dll.dsgetsitename

if err.number <> 0 then ReportError:Wscript.Quit
wscript.echo "4> The site for this server is: " + domaincontrollersitename

'get the DSA DN for this box
DSAObj = localMachine.get("dsServiceName")
if err.number <> 0 then ReportError:Wscript.Quit
wscript.echo "5> The DN for this machine's DSA is: " + DSAObj

'bind to the Site Settings object in the Directory
SiteSettingsPath="LDAP://localhost/CN=NTDS Site Settings,CN="+domaincontrollerSiteName+",CN=Sites,"+configNC
set SiteSettings=GetObject(SiteSettingsPath)
if err.number <> 0 then ReportError:WScript.Quit

'make the current box the ISTG
wscript.echo "6> Making " + ucase(ServerName) + " the Inter Site Topology Generator for the " + ucase(domaincontrollerSiteName) + " site."
SiteSettings.Put "interSiteTopologyGenerator",DSAObj
SiteSettings.SetInfo
if err.number <> 0 then ReportError:Wscript.Quit

'get the current options
origOptions=SiteSettings.Get("options")
if hex(err.number) = "8000500D" then
origOptions=0
elseif err.number=0 then
'do nothing
else
ReportError:Wscript.Quit
end if
modOptions=origOptions
wscript.echo "7> Currently, the options specified for KCC operations for the ISTG in this site is set to: " + cstr(origOptions)

'enable the KCC if currently disabled, otherwise, leave it alone
if modOPtions And 16 then
mod2Options=modOptions XOr 16
wscript.echo "8> The KCC is currently disabled for inter-site topology generation. Temporarily re-enabling it. Setting options to: "+ cstr(mod2Options)
SiteSettings.Put "options", mod2Options
SiteSettings.SetInfo
if err.number <> 0 then
ReportError
wscript.echo "An error occurred during the process of modifying the options attribute. Check to make sure that it has the correct original value. This script is terminating."
Wscript.Quit
end if
else
wscript.echo "8> The KCC is currently enabled to handle inter-site topology generation. No change is necessary before triggering the KCC."
end if

'run the KCC
Result=dll.TriggerKCC(cstr(ServerName))
if err.number > 0 then ReportError
If result=0 then
wscript.echo "9> The KCC was successfully triggered on " + ucase(ServerName)
else
wscript.echo "9> The following error occurred trigerring the KCC on " + ucase(ServerName) + ": " + dll.lasterrortext
end if

'disable the KCC
wscript.echo "10> Re-writing the original options (" + cstr(origOptions) + ") to the ISTG."
SiteSettings.Put "options", origOptions
SiteSettings.SetInfo
if err.number <> 0 then ReportError:WScript.Quit

End Sub

'end script

For more information about the Windows 2000 KCC, click the following article numbers to view the articles in the Microsoft Knowledge Base: