P
paisher
Hello,
I'd like to have some people's opinion on AD design. What
to do, if active directory has to be implemented over 100
different locations with an average of 30 users per
location. One domain would be a dream, as approx. 30
percent of the locations are connected by slow sattelite
links. All other connections are able to connect AD sites
with the replication of AD and exchange. So i thought a
forest with a domain for each location devided in sites
and one exchange organization with routing groups could
help. The number of users per location isn't my worry,
but the fact that 130 domains have to be created, managed
and replicated individually is. Would that high number of
domains make a lot of replication traffic? I'm concerned
about the replication that global catalog servers will
make for forest-wide replication. Did anyone use SMTP to
replicate from sites with a bad connection? Any comment
is welcome.
..
I'd like to have some people's opinion on AD design. What
to do, if active directory has to be implemented over 100
different locations with an average of 30 users per
location. One domain would be a dream, as approx. 30
percent of the locations are connected by slow sattelite
links. All other connections are able to connect AD sites
with the replication of AD and exchange. So i thought a
forest with a domain for each location devided in sites
and one exchange organization with routing groups could
help. The number of users per location isn't my worry,
but the fact that 130 domains have to be created, managed
and replicated individually is. Would that high number of
domains make a lot of replication traffic? I'm concerned
about the replication that global catalog servers will
make for forest-wide replication. Did anyone use SMTP to
replicate from sites with a bad connection? Any comment
is welcome.
..