One domain is not a problem. Domain controllers in the sites are not a
problem. You need to look at Sites and Services in Active Directory to see
how to optimise the WAN traffic.
There is lots of info on sites in help and at the microsoft website. If
you have a particular problem, try posting in the
microsoft.public.windows.server.active_directory newsgroup. That's where the
experts on this hang out.
"Exo" <(E-Mail Removed)> wrote in message
news:cc0601c48a2c$6cd4b550$(E-Mail Removed)...
> Hi All,
>
> I need more input on Network Design.
>
> We have 5 offices spread throughout...
>
> CURRENT ENVIRONMENT:
> Office 1 in Kansas City
> Office 2 in Boston
> Office 3 in SanDiego (Corporate Office)
> Office 4 in Philadelphia
> Office 5 in Netherland (Europe)new coming online soon
>
> SanDiego currently has Exchange Server 2003 and a Domain
> controller/Active Directory. All users from other offices
> login to their mails hosted here at office 3.
>
> All offices are connected to the Corporate Office via
> Tunnels (1.5mbps connection). Some workstations are
> members of the the DomainController.
>
> I have been assigned to redesign our network
> infrastructure.
>
> What i have in mind now is:
> 1)Keep the current DomainController
> 2)Any new system coming online will either be a member of
> or a child domain of the DomainController
>
> The reason i want only one domain controller is for
> centralized administration
>
>
> Would this design work efficiently?
>
> Another thought is:
> 1) Create a domaincontroller in each office
> 2) Create a trust relationship to the domain controller
>
> but I foresee that administration would be tougher as the
> company grow bigger and bigger.
>
> The Big question is:
> What would be the best design for my environment?
>
> Any help on this would be much appreciated.
>
> thanks in advance.
>
> -Exo
>
> All user
>
|
Similar Threads
Linear Mode
