Re: Site design

From: Laura E. Hunter \(MVP\) (hunter(nospamplease)_at_sfs.upenn.edu)
Date: 07/01/04 

Date: Thu, 1 Jul 2004 13:30:52 -0400

The beauty of sites is that they allow you to separate your physical design
from your logical data requirements.

Generally speaking, you only need to create separate domains if you have
segments of your userbase that have different security requirements, since
certain security settings (account policies are the most obvious, but there
are others) can only be set at the domain level. Since Active Directory is
site-aware, your clients will attempt to authenticate through a DC at the
local site before making an attempt across a WAN link. It's helpful to have
a DC at each site, and the secondary DNS server at each site is also quite
good, design-wise.

Be sure that you set up your replication topology correctly, and monitor it
to make sure that it is behaving the way you expected it to. There are
tools (built-in and Resource Kit) like replmon.exe that you can use to
monitor replication traffic between your sites.

http://www.microsoft.com/windows2000/techinfo/reskit/samplechapters/dsbh/dsbh_rep_yphn.asp 

-- 
******************************
Laura E. Hunter - MCSE, MCT, MVP
Replies to newsgroup only
"taylor" <anonymous@discussions.microsoft.com> wrote in message 
news:2421201c45f5f$277705a0$a301280a@phx.gbl...
>I need some help in designing Windows 2003 implementations
> in three geographically separated sites. I need to let
> one Administrator to adminster group policies, accounts,
> etc. from the main site.
>
> Site 1(main) : W2k3 DC, DNS, DHCP, Database and
> Application server, Exchange,ISA, File and Print Server.
>
> Site 2: 1km away connected through single mode fibre
> DC, Secondary DNS, File and Print Server.
>
> Site 3: 2km away connected through single mode fibre
> DC, Secondary DNS.
>
> Is it better to configure sites with all DCs in the same
> domain or shall I create child domains for each site.
>
> And any comments on this design?
>
> If I am posting in the wrong newsgroup please guide me
> to the right one.
>
> Thanx

Relevant Pages

  • Re: Design for historical data
    ... > types of visits are really that, 3 separate types of visits, which store ... billion rows of page delivery history in a system I helped build (I know ... Good design is important, decent, well balanced hardware (disk, ... Pro SQL Server 2000 Database Design - ...
    (microsoft.public.sqlserver.programming)
  • Re: Philosophical placement of counter
    ... Depends on what you mean by 'fsm architecture'. ... readability and maintainability of the design. ... I would likely break it up into separate clocked processes just to try ...   process ...
    (comp.lang.vhdl)
  • Re: Optimizing the Speed / Design tradeoff in numeric applications
    ... >> calculations to arrive at three values, named d2, t0 and theta. ... > I agree with Pete that whenever possible, design should trump ... My attitude would be to first separate the external world ... typedef struct gazouta { ...
    (comp.programming)
  • RE: "Module" option does not show up when setting permissions.
    ... It's by design. ... Access 2000 introduced the separate VBA ... Project for handling the code (notice the separate code window (VB Editor) ... an MDE database file out of it if you want to hide the source code from ...
    (microsoft.public.access.security)
  • Re: Forest, Domain, OU design question
    ... It seemed that the exam was more focused on GPO, NT 4 DNS situations and RIS then any real situations regarding AD design. ... >> they wanted separate schemas or keep administration separate. ... > Domains are REQUIRED for "diffferent security> ACCOUNT policies" > although sloppiness is possible on any particular> question. ... > Domains may be required/desired if you need "complete> control" of resources, mirroring NT domain structures>, and for either/both "massive> number of objects" and to "control replication" in WANS. ...
    (microsoft.public.win2000.active_directory)
Loading