Re: 2-3 site setup - Single Forest , multiple domain?

From: Steve Foster [SBS MVP] (steve.foster_at_picamar.co.uk)
Date: 04/21/04


Date: Wed, 21 Apr 2004 15:43:32 -0700

Edwick wrote:

>
>
>
> Hello folks,
>
> I have a customer with 3 SBS2000/4.5 locations. They (we) would like
> to move to Server2003 and Active Directory.
> Is there any good documentation on doing a (relatively) small scale
> setup like this? There are no dedicted links between each of the
> sites and as such we would be using VPNs to connect them (ISA or
> hardware-based) via DSL or Fractional T1 service. This seems like a
> "branch-office" situation but the MS "branch-office" documentation is
> pretty complex and suggested as appropriate for 100+ nodes (never
> happen here).

Are you sure? From the numbers you outline, it seems like you're
probably close to the 100+ nodes.

You're certainly beyond SBS!

>
> Ideally, we would have ONE W2k3 Forest root server and ONE or more
> application servers (Exchange/ISA/file-print) at each location
> connected via VPN. Read: each site would have 2-3 servers located on
> it. The two sites have approx 50 users per location.
> There are about 10-15 small locations with 2-5 PCs used to POP mail
> from their main Exchange server.

As long as you have reliable links between LAN sites, a single forest
with a single domain should work fine.

>
> We would like to employ ease of Administration, Group Policies, and
> better Exchange store distribution. To that end, are there any good
> articles that cover Exchange 2003 in this multi-site setup?

Running multiple Exchange servers within an organisation is relatively
trivial in a single forest/single domain scenario. It gets more
complicated if the AD structure is more complex.

>
> This company may bring in another server to another growing location
> within the next year so this needs to be appendable to include this.

Extending AD to additional locations is again fairly trivial in a
single forest & domain environment - you just get basic tcp/ip working
at the WAN level and add servers.

>
> I feel like i'm asking what should be obvious-answerable questions
> but I don't have the answers. Typically I deal in SBS2000/SBS2k3
> installations.

Fundamentally, you *must* get the core TCP/IP services working nicely
across your WAN. Get that wrong, and any AD implementation will be a
nightmare. Get it right, and AD will be as easy as a single LAN.

-- 
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.


Relevant Pages

  • Re: Forestprep
    ... Setup failed while installing sub-component Microsoft Exchange ... The Exchange Server Setup Progress.log file shows the following: ... >>> or the other operations master role holders. ...
    (microsoft.public.exchange.setup)
  • Re: DR stand by server for 2003
    ... Join the new Exchange server you setup into the domain ... Restore your mailboxes from backup ...
    (microsoft.public.exchange.setup)
  • Re: 1 Exchange server with child or trusted domains?
    ... You can setup the site link replication to run infrequently to ... Windows Server MVP ... > We've got two 2003 DCs, one 2003 Exchange server, native mode on both. ... > Setting up a remote office for about 10 users, connected via VPN. ...
    (microsoft.public.exchange.design)
  • Re: Changing Exchange Server name in outlook 2000
    ... > configured.Its a single forest and single domain. ... > My question is how to change the exchange server name on ... > way to change server name on a global basis instead of ...
    (microsoft.public.exchange.design)
  • Changing Exchange Server name in outlook 2000
    ... configured.Its a single forest and single domain. ... My question is how to change the exchange server name on ...
    (microsoft.public.exchange.design)