• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 258
  • Last Modified:

Setting up a local Exchange server

We have one Exchange 2003 Enterprise Server SP2 in the main office.  Users in other locations will access their mailbox via a VPN connection.  The response times is quite slow for the VPN users.  I would like to be able to store their mailboxes locally in a local Exchange server.  Additionally, if the local server fails I would like for them to be able to use the main Exchange server as a backup.  Is this possible?
0
mhbland
Asked:
mhbland
  • 2
  • 2
  • 2
1 Solution
 
tigermattCommented:

The first part is possible. You'd get a second Exchange Server and install it into the second office. You then move the mailboxes of users in the second office to their local Exchange Server. Their connection in Outlook would then be direct to their local server, and the Exchange server communicates back to the head office over the VPN connection.

Configuring resilience in that users in each office are 'backed up' on the other Exchange Server becomes much more difficult and would require some form of cluster. For smaller deployments, you'd be looking at a DoubleTake license to do such clustering. Alternatively, if you upgraded to Exchange 2007, you could gain some clustering using SCR (Standby Continuous Replication), although you don't get the automated failover with this approach.

For the majority of deployments, high up-time can still be achieved without spending out on an Exchange cluster. If Exchange is installed on suitable hardware with redundancy features (redundancy power supplies, correct RAID arrays and so on), you can achieve VERY high uptime without the added cost of installing and maintaining a cluster.

-Matt
0
 
abhaighCommented:
you would need to use a third-party clustering solution in order to do what you want

I would look at WANSyncHA for Exchange, - yes, it's unfortunatly been bought by CA, but it does what it says on the tin and would provide you with the functionality you are after (no, I don't work for CA :)
0
 
mhblandAuthor Commented:
Thanks for your advice.  I think you are right in that it is best to go for a second Exchange server with high fault tolerance rather than having to go for some sort of clustering.  Can you point me at some good documentation on setting up a second Exchange server for specific mailboxes.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
abhaighCommented:
It's easy

1.set up new exchange box as a member server of the existing org

2. use ADUC to move the mailboxes of the people you want hosted on that sever across to it

3.?????

4. PROFIT!

The only question is how long the mailbox move would take across your wan, but if you aren't moving that many mailboxes, and they aren't gigantically huge, it's not going to take all that long.
0
 
tigermattCommented:

As the previous poster stated, the process is very easy. You'd need to install Server 2003 to a machine and join it to the domain, then install Exchange onto that machine.

Assuming you downgrade a new Exchange 2007 license to enable you to install Exchange 2003, you would then create a new routing group, drop the server into it, and create a Routing Group connector between the two groups.

You will need a second A record outside (something like mail2.company.com) and map it to the static IP in the second site. Users with mailboxes on the second server must connect directly to their Exchange Server to access OWA or RPC/HTTP; these requests will not be proxied through the current server. I'd suggest at the same time, you open port 25 at the second site and add mail2.company.com as an additional MX record - again, to give fault tolerance for inbound email.

There isn't much more configuration before you launch the Move Mailbox wizard and move the appropriate mailboxes to the new server. Users' Outlook configuration will update itself automatically the next time Outlook is launched.

It couldn't be simpler.

-Matt
0
 
mhblandAuthor Commented:
Thank you very much for pointing me in the right direction.  I will start testing all this on our test network.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 2
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now