|
As a start, you want to use sites to define router
topology. In other words, you want to be able to define to the clients,
the shortest/fastest path to the domain controller vs. the old NT3/4 days where
it would just broadcast for the closest dc.
Al
From: Creamer, Mark [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18, 2003 2:37 PM To: [EMAIL PROTECTED] Subject: [ActiveDir] Site Replication Topology I'd like to revisit our site design, and am looking for some advice if possible. Right now we have a couple hundred physical sites in terms of individual IP subnets, but only a few sites defined in AD. The ones defined are the sites that actually have a domain controller located there. The greatest volume of traffic over our WAN is AS/400 emulation, so we have mostly slow links, 56-256K.
Reviewing Robbie's book #1, I see he suggests a one-to-one site topology between sites defined in AD and physical sites where a subnet is located. Can I get an explanation why I would or might not want to set things up this way? My limited understanding of the sites was to associate the various subnets with a specific site, but I suspect there's a lot more to it than that. Thanks!
Mark Creamer
|
- [ActiveDir] Site Replication Topology Creamer, Mark
- RE: [ActiveDir] Site Replication Topology Mulnick, Al
- RE: [ActiveDir] Site Replication Topology John Reijnders
- RE: [ActiveDir] Site Replication Topology Creamer, Mark
- RE: [ActiveDir] Site Replication Topology John Reijnders
- RE: [ActiveDir] Site Replication Topology Creamer, Mark
