Hi,

We are looking at replacing our non-Windows based mail server with
Windows 2003 Enterprise and Exchange 2003 Enterprise. I would appreciate
advice on whether my thoughts are on the right track.

Site A is a datacentre.
Site B is HQ, less than 50 users.
Site C is a smaller office.

There are a small number (<10) users who roam on their laptops.

Connectivity:
Site A: 100mbit no probs.
Site B: ADSL. Each line 2mbit down, 256k up. We can get 4x bonded.
Site C: Shared building connectivity (presume 2mbit).

Currently, Site B has the fileserver and mailserver. It locally has the
most users. Roaming (mobile) and remote (Site C and other minors) have
severe connectivity problems accessing their email from Site B.

This is obviously not scalable and liable to collapse.

I am thinking:
1. Site A gets 1x server with Windows/Exchange and is the root domain
(.root).
2. Site B gets 1x server with Windows/Exchange and is a sub-domain
(office-a.countrycode.root).
3. Servers at both A and B replicate all configuration (AD/etc), files
and email between each other.
4. Users connected locally at Site B send and receive email/files from
Site B's server.
5. All other users (mobile and other sites) send and receive their
email/files from Site A.

I hope this is clear? Think largely electronic based company who's HQ
has a stretched connection to the world.

Am I on the right track for design? I assume that replicating mail/files
from Site B to Site A will be one major pain in the rear over this
connectivity. But can it be done, and are there any ideas on
improvements out there?

Links to documentation particular to our situation would be useful too,
have been reading a wealth but most is pertinent to orgs with lots of
servers.

Thanks!

James