Solved

Exchange 2003 with multiple Front End servers

Posted on 2006-06-21
4
214 Views
Last Modified: 2010-03-06
Hi,
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 mail.domain.com in Head Office. (Primary)
#Create MX record (20) of Front-End02 pointing to mail.domain.com 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.

Sal
0
Comment
Question by:exp_ee
[X]
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
  • 2
  • 2
4 Comments
 
LVL 104

Expert Comment

by:Sembee
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.

Simon.
0
 

Author Comment

by:exp_ee
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 https://mail.domain.com or I have to select a different name for the secondary something like https://mail1.domain.com ?

0
 
LVL 104

Accepted Solution

by:
Sembee earned 500 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.

Simon.
0
 

Author Comment

by:exp_ee
ID: 16975125
Convinced. Thanks for your answers.
0

Featured Post

Backup Solution for AWS

Read about how CloudBerry Backup fully integrates your backups with Amazon S3 and Amazon Glacier to provide military-grade encryption and dramatically cut storage costs on any platform.

Question has a verified solution.

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

Suggested Solutions

Title # Comments Views Activity
exchange 2016 suddenly stopped working 15 50
Skype for Business server 6 44
query all mailbox rules 5 29
exchange 13 22
Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
In-place Upgrading Dirsync to Azure AD Connect
In this video we show how to create an Accepted Domain 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 Mail Flow >> Ac…
This video discusses moving either the default database or any database to a new volume.

749 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