Hi, > Ken are you talking about preventing AD from automatically creating site > links between all DC's in a network?
Site Links, and Connections are two different things. Site Links are not automatically created (except the Default First Site Link). You create these manually between sites. Once you've created your site links, the ISTG (Inter Site Topology Generator) generates the connection objects between DCs. Note the difference: Site Links are between sites. Connection objects are between DCs When Bridge All Sites Links is enabled, then site links are considered transitive. E.g. consider the following scenario (and each site has a single DC): Birmingham <- Site Link 1 -> London <- Site Link 2 -> New York In this case, if site links are transitive, then connection objects will be generated between BirminghamDC <-> LondonDC and LondonDC <-> NYDC and also between BirminghamDC <-> NYDC. If you don't want replication to flow BirminghamDC <-> NYDC then you need to disable "bridge all site links" Now, if you case, you have something pretty much the same as this: http://technet2.microsoft.com/windowsserver/en/library/d82e1b2f-d167-409b-a8c7-04364964e5e51033.mspx You'd want to disable "bridge all site links" and create the necessary site link bridges manually. Cheers Ken From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, 24 January 2008 3:34 PM To: NT System Admin Issues Subject: RE: AD Sites / Services gurus Ben/Ken, Sorry for the hijack, but my question may answer Ben's as well. Ken are you talking about preventing AD from automatically creating site links between all DC's in a network? I am building a AD proposal for about 6 sites and if my design is right I am going to have 3 sites US side with a main site link from the Miami location to the London location. From the London location it will goto the 2 offices on that side of the Atlantic. This way I only have replication going from Miami to London across that one Link, the remote offices on each side replicate with Miami and London respectively. If I need other connectors to other DC's for example; if Miami's DC fails I would need to manually create them from Site B and C to London. Is my thinking correct here? If so, then this may explain Ben's issue as well. One of his sites may have it turned off. I also see the only benefit in disabling all bridged site links is to control replication topology generation for the purpose of bandwidth control. Is that correct? I have also read that with SP1 and SP2, DFS site costing is no longer broken with the disabling of all Bridged site links, which means I have independent control of DFS Replication despite the Site Links...this I have to test in a lab since that is pretty much its sole purpose to provide reps in the area up to date documentation that they sync with their laptops and automated SW installation for the equipment through GP and scripting. This level of AD stuff is still a bit to new for me to be sure of anything yet. Greg From: Ken Schaefer [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 23, 2008 8:54 PM To: NT System Admin Issues Subject: RE: AD Sites / Services gurus You don't mention if you created site links between all your sites. Also, do you have "Bridge all site links" enabled or disabled? Cheers Ken From: Benjamin Zachary [mailto:[EMAIL PROTECTED] Sent: Thursday, 24 January 2008 10:40 AM To: NT System Admin Issues Subject: AD Sites / Services gurus I have one ad structure with 16 sites geographically dispersed. When I goto add a new site (and its been this way) the automatic generated connectors will connect some but not all other sites. For example, I add Site10 and it will create connectors for sites 1,2,3,6,7,8.Not a huge deal because I can add it manually but im trying to look at why it does this. Normally I have a handful of sites so have never seen this. There seems to be no specific case each tiem I add a site it will add some random number of ad connectors. ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
