I never followed that one, even on Windows 2000 where it applied. I had at most around 100 sites hanging from a single hub and was fine. The main thing was to make sure that the topology was properly defined and you had site link bridging disabled. If you defined things right, the KCC won't try to change the connections that much and everything will be fine. If your DSA Pending Queue was going out of control on your hub bridgehead you could either cut back the replication window or spread the connection load in the hub with ADLB. Make sure you get the officially released (latest versions) of ADLB. I found a mound of bugs in that and worked with MS to straighten them out when it first came out. Back then it could really dork up your connections good if you just ran it without verifying what it wanted to do first.
 
  joe
 
 
 
--
O'Reilly Active Directory Third Edition - http://www.joeware.net/win/ad3e.htm 
 
 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adeel Ansari
Sent: Wednesday, February 08, 2006 2:26 PM
To: [email protected]
Subject: [ActiveDir] Site Link Question

All,
 
I have about a few hub sites with 100+ site link. I found following from M$ website :
 
  • Make sure that no site is directly connected to more than 20 other sites
This condition can occur in large hub-and-spoke deployments where most sites are branch sites that communicate with a centralized hub site. If this condition exists and there are more than 20 site links from the hub site to branch sites, the hub site can be divided into multiple sites to provide additional bridgehead servers to handle the replication volume. In a site, a single bridgehead server is active per domain. If the site has more than 20 site links, the bridgehead servers can become overloaded.
 
 
 
Can someone please explain what steps do I need to take to divide the hub sites?
 
Regards,
Adeel
 

Reply via email to