Remote Office Email without a WAN

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Scumbag Adie (ScumbagAdie_at_discussions.microsoft.com)
Date: 09/10/04 

Date: Fri, 10 Sep 2004 13:37:07 -0700

Hi

I'm a bit of a novice with Exchange but here's a novel problem:

I designing a single domain w2003 system with a headquarters and multiple
remote sites. The problem is that many of the remote sites will have very
poor or non existant WAN links. Therefore I'm playing with some ideas to get
round this.

So far in the Active Directory newsgroup I've bounced the idea of using a
virtual machine DC being passed as a file on DVD between headquarters and the
remote sites. This virtual machine DC would be used to transfer AD
replication between DC's at headquarters and DC's at the remote sites and
back again. Might work, we'll have to see.

THe post here is to explore how Exchange at headquarters can exchange emails
and whatever else it needs to do between headquarters and the remote sites.
If Exchange was installed on the virtual machine DC could it act as a sort of
routing node between headquarters and the remote site, again by transferring
the virtual machine between the two?

Thanks in advance for you understanding of a crazy question (the SQL forum
will get the same sort of question for SQL server replication!).

Relevant Pages

  • Re: Requesting data messages
    ... Well actually in Exchange the GC's were not set to Automatically Discover ... So the two remote sites that are not in-site were manually added ... for remote3-dc2.xxxx.com as this DC is a VM and also a file server I ...
    (microsoft.public.exchange.connectivity)
  • Re: Requesting data messages
    ... FYI we also are using Outlook XP so we don't have cached exchange mode. ... So the two remote sites that are not in-site were manually added ... should be the ones local to the exchange server. ...
    (microsoft.public.exchange.connectivity)
  • Re: Outlook 2003 over ADSL to Centralised Exchange
    ... > There are ten remote sites and each one is one days travel away for the ... > not to locate Exchange servers locallly. ... > There is a requirement for the full Outlook 2003 client to support a plug ... > Outlook 2003 clients such a design. ...
    (microsoft.public.exchange.design)
  • Re: Migrating from 5.5 & Nt 4.0 to Win2k3 and Exch. 2k3
    ... You can move to Exchange 2003 without first going to Exchange ... >> I would install your first E2K3 server into the main site. ... >>> connected with a X400 connector to the main site. ... >>> wish to create a AD with OU's for the remote sites. ...
    (microsoft.public.exchange.setup)
  • Re: Exchange 5.5, 2000, and 2003 all on a 2000 domain
    ... Will this pose any problems? ... half of our headquarters' users on ... running all three of those versions in the same Exchange ...
    (microsoft.public.exchange.setup)