Two important "tasks" that sites have to deal with is optimizing
replication traffic on one hand and authentication traffic on the other. At the
moment you have a couple hundred physical sites in terms of individual
subnets.By default you start designing your site topology by doing a
: Wednesday, November 19, 2003
3:37 AM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Site
Replication Topology
Two important
tasks that sites have to deal with is optimizing replication
traffic on one hand and authentication traffic on the other. At the moment you
have a couple hundred physical
efficient queries. This is important from a DC load AND from a
network load point of view.
Cheers!
John
From: Creamer, Mark
[mailto:[EMAIL PROTECTED] Sent: woensdag 19 november 2003
15:14To: [EMAIL PROTECTED]Subject: RE:
[ActiveDir] Site Replication Topology
LOL
Good question
, November 19, 2003
9:59 AM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Site
Replication Topology
You're welcome
... replicationis (one of) my favourites :-). It's a good thing you're
trying to be ahead of the game! GC caching is a nice feature, but I
thinkit will not contribute to the discussion
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
