B
bruce
We have a multi-site win2k network that was sort of grown out of control.
we have 10 sites with either DSL or T1 connectivity. Every site is linked
by VPNs.
We would like to consilidate with our 3 multi-server sites as sort of a
core link. Then link each of the remaining single server sites into this
core, but not to each other. This way changes that originate from one of
the core sites (almost all changes do) would replicate out, changes that
originate from one of the single server sites would replicate to the core &
then back out to the other single server sites.
My question is, knowing that when I create a link with more than 2 sites AD
treats is as a NxN star config, how should I link the other sites?
Should I create one link for each single server site that includes the site
+ the core sites? Will this create a big mesh mess?
-or-
Should I create 3 links for each single server site, one to each core site?
Any advice appreciated. TIA
we have 10 sites with either DSL or T1 connectivity. Every site is linked
by VPNs.
We would like to consilidate with our 3 multi-server sites as sort of a
core link. Then link each of the remaining single server sites into this
core, but not to each other. This way changes that originate from one of
the core sites (almost all changes do) would replicate out, changes that
originate from one of the single server sites would replicate to the core &
then back out to the other single server sites.
My question is, knowing that when I create a link with more than 2 sites AD
treats is as a NxN star config, how should I link the other sites?
Should I create one link for each single server site that includes the site
+ the core sites? Will this create a big mesh mess?
-or-
Should I create 3 links for each single server site, one to each core site?
Any advice appreciated. TIA