--- Begin Message ---We made every domain controller (80+) in our forest a GC. We did this because if a link went down, we wanted each DC to be able to hold its own. Maybe this wasn't such a good plan?________________________________ From: [EMAIL PROTECTED] on behalf of Laura A. Robinson Sent: Wed 8/30/2006 5:10 PM To: [email protected] Subject: RE: [ActiveDir] AD Site replication settings/costs No. GCs can replicate partitions that they don't own to other GCs. They can't replicate them to DCs for the domains in question, but they *can* replicate their read-only partitions to other GCs. Laura ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Cliffe Sent: Wednesday, August 30, 2006 5:40 PM To: [email protected] Subject: RE: [ActiveDir] AD Site replication settings/costs That should be "GCs cannot replicate partitions they don't own...." right? ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Laura A. Robinson Sent: Wednesday, August 30, 2006 5:05 PM To: [email protected] Subject: RE: [ActiveDir] AD Site replication settings/costs Is it a GC? If so, then yes, that's to be expected. You may have *thought* that you gave it only one replication partner, but if you're seeing additional connection objects, then it has more than one replication partner. When planning replication, you must be aware of every partition that the DCs in a site are hosting. If you don't want that remote DC to have connection objects from all of those other DCs, you're probably going to need to set up connection objects for preferred DCs for it to use for replication of partition data. If it's a GC, and if you have a GC that is a DC for the same domain in another site, that would be a good choice to set as a replication partner, because they would be able to replicate all of their partitions (GCs can replicate partitions they don't own to other GCs). Laura ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rimmerman, Russ Sent: Wednesday, August 30, 2006 2:52 PM To: [email protected] Subject: RE: [ActiveDir] AD Site replication settings/costs It's a Windows 2000 native domain, we're about 4 upgrades from having all Win2k3 DCs and from what I've read, that should help a lot with replication. Automatic site link bridging isnt enabled, and we have 0 site link bridges. We're a worldwide company with 3 main hubs, but it is a mesh network in design (MPLS). I guess i'm mainly confused because the DC at the slow bandwidth site in question only has one replication partner, yet we see connections to it from a large number of our DCs on a regular basis. Is this normal? ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Laura A. Robinson Sent: Wednesday, August 30, 2006 11:12 AM To: [email protected] Subject: RE: [ActiveDir] AD Site replication settings/costs Intervals vary by company, domain structure, network topology and latency tolerances. That said, there is nothing inherently wrong with the replication parameters you list below. Are they the best parameters for your environment? That depends. Is this a Windows 2000 environment? Is automatic site link bridging enabled? There's a lot to consider in determining how to set site link properties; what you've listed below won't really be enough for anybody to give you any kind of realistic advice. (sorry) Laura ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rimmerman, Russ Sent: Wednesday, August 30, 2006 11:59 AM To: [email protected] Subject: [ActiveDir] AD Site replication settings/costs We have about 80 AD sites with DCs. All sites are set for a cost of 100 on the site to site replication, and a replication interval of 15 minutes. I'm presuming this is probably not a good thing. One slow bandwidth site is complaining that their DC is talking to every DC in the domain. What is everyone else using as a replication interval for inter-site replication? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This e-mail is confidential, may contain proprietary information of Cameron and its operating Divisions and may be confidential or privileged. This e-mail should be read, copied, disseminated and/or used only by the addressee. If you have received this message in error please delete it, together with any attachments, from your system. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This e-mail is confidential, may contain proprietary information of Cameron and its operating Divisions and may be confidential or privileged. This e-mail should be read, copied, disseminated and/or used only by the addressee. If you have received this message in error please delete it, together with any attachments, from your system. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To find out more about Reuters visit www.about.reuters.com Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Reuters Ltd.<<winmail.dat>>
--- End Message ---
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This e-mail is confidential, may contain proprietary information of Cameron and its operating Divisions and may be confidential or privileged. This e-mail should be read, copied, disseminated and/or used only by the addressee. If you have received this message in error please delete it, together with any attachments, from your system. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
