Improve company productivity with a Business Account.Sign Up


Exchange 2003 with multiple Front End servers

Posted on 2006-06-21
Medium Priority
Last Modified: 2010-03-06
One of my customer is having one Head Office and a Branch. Each location will have one Exchange 2003 Back-End and one Front-End. I want to keep exchange servers in 2 different Routing Groups as physically there are connected through WAN links. OWA site will be published on the ISA 2004 server which will be acting as internal firewall.
To make both sites as failover site for each other I would like do the following things:
#Create MX record (10) of Front-End01 pointing to in Head Office. (Primary)
#Create MX record (20) of Front-End02 pointing to in Branch Office. (Secondary)
If the mails cannot be delivered to via Front-End01, then the mails automatically delivered to Front-End02.

Q1) I would like to know, under what circumstances and conditions the mails are sent to Front-End02 (secondary) instead of Front-End01 (primary)?

Q2) Do I need to setup the OWA on both the locations and publish on the ISA 2004 on both the locations?

Q3) What settings should I do on the Back-End servers to deliver the mails internally between routing groups?

Q4) Any other suggestion based on the above scenario to make complete redundancy?

I am badly in need of your suggestions.

Question by:exp_ee
  • 2
  • 2
LVL 104

Expert Comment

ID: 16959220
The scenario that you have outlined above will only give you redundancy for inbound email traffic - not for the mailboxes themselves.

The MX record behaviour has nothing to do with Exchange. Therefore if you read up on how MX records work, you will get your answer.
Basically if the lowest value MX record is not available or cannot be reached, then the higher value record is used. The exact reasons for when the higher value is used differs between servers.
The exception to that is when spammers come along. They will usually use the higher value record in the (often correct) belief that the second MX doesn't have the same level of spam protection as the primary.

OWA will be on both frontend machines whether you want it to be or not. What is your choice though is whether OWA can be seen from the internet. That is where your firewall or ISA servers come in. (Yes I did say servers, because if you want the redundancy then you need to have two of those as well - one at each office).

You will need a routing group connector to get email delivered between the routing groups. Also make sure that you have not put a smart host on to the SMTP VS of any Exchange server, as that will disrupt the message flow.
If you want emails to go out through the Frontend servers, then create an SMTP Connector and set the default SMTP VS on the server you want to use for outbound email as the bridgehead.


Author Comment

ID: 16974958
Thanks Simon for your detail answer.
Shall I consider that if I shutdown the Front-End01 which is pointing to MX 10, then the mails will be diverted to Front-End02 which is pointing to MX 20?

If I publish OWA of Front-End01 to ISA01 and Front-End02 to ISA02, the url address should be the same i.e or I have to select a different name for the secondary something like ?

LVL 104

Accepted Solution

Sembee earned 2000 total points
ID: 16975090
If one server is completely unavailable then internet servers should start using the second MX record for email delivery. That is the point of multiple MX records.

For your two URLs, that is up to you. If you have both servers reacting to the same DNS name then you will need to configure both in DNS and have round robin DNS in place. That will not give you redundancy, because the DNS system doesn't know when one server is down. You would have to look at some kind of load balancing technology to sort out which server is live or not.

Otherwise two URLs will make it easy for your users to know which server they are connecting to.

When you come to purchase SSL certificates, do not be tempted by wild card certificates, as those are not compatible with Windows Mobile devices.


Author Comment

ID: 16975125
Convinced. Thanks for your answers.

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

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

The article is for all the Exchange users seeking smooth and effective EDB to PST conversion. Exchange Server is the most widely used platform for messaging with collaborative sharing, Exchange online, secure working environment, etc.
How to import Outlook calendar to MS Exchange Server. A Calendar stores user appointments, meetings details to manage work. Moving Outlook Calendar to a new or already existing Exchange Server become complex process if Admin needs to import Calendar…
Watch the video to know how one can repair corrupt Exchange OST file effortlessly and convert OST emails to MS Outlook PST file format by using Kernel for OST to PST converter tool. It can convert OST to MSG, MBOX, EML to access them. It can migrate…
Watch the video to know the process of migration of Exchange or Office 365 mailboxes in absence of MS Outlook. It is an eminent tool which can easily migrate Public, Archive user mailboxes from one another Exchange server and Office 365. Kernel Migr…

589 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