Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

Setting up a local Exchange server

Posted on 2009-04-07
6
229 Views
Last Modified: 2012-05-06
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
Comment
Question by:mhbland
  • 2
  • 2
  • 2
6 Comments
 
LVL 58

Expert Comment

by:tigermatt
ID: 24087993

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
 
LVL 15

Expert Comment

by:abhaigh
ID: 24091919
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
 

Author Comment

by:mhbland
ID: 24094611
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
Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.

 
LVL 15

Expert Comment

by:abhaigh
ID: 24094898
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
 
LVL 58

Accepted Solution

by:
tigermatt earned 250 total points
ID: 24094969

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
 

Author Closing Comment

by:mhbland
ID: 31567521
Thank you very much for pointing me in the right direction.  I will start testing all this on our test network.
0

Featured Post

Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Utilizing an array to gracefully append to a list of EmailAddresses
In-place Upgrading Dirsync to Azure AD Connect
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…

840 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question