Solved

Setting up a new Front-End Exchange Server

Posted on 2007-12-06
2
849 Views
Last Modified: 2011-10-03
We have a few companies that all use the same Exchange setup.  Right now I am in the process of setting up a second Front-End Exchange server that will be used for the larger of the companies.  I wasn't able to find a good solid best practice scenario for some of my questions, so I wanted to see what the expert's opinions were:

1) Is there any potential problem with having 2 Front-End Exchange servers pointing to the same back-end?

2) Does the computer name on our domain have to be the same as the public A record?  If I have it as FEMailServer on the domain & exchange.domain.com on the public internet.  Also, I want to get an SSL certificate registered in that name too.

3) I want to put it behind my firewall completely, so I need to know what ports I need open to the world.  I plan on doing the following:
- SMTP
- POP3
- IMAP
- Exchange ActiveSync
- OWA
- OMA
- RPC over HTTPS
- What other options are there? =)

4) Are there any articles on other best-practices to consider when implementing a new one?

5) I want to create an SMTP connector in our Exchange Manager to take all email that is coming from a list of domains & send it through the bridgehead of my new FE Exchange Server & then out to our managed security service.  I know how to build the generic portion of the SMTP Connector, but how would I specify only to allow for the certain domains going out it.  

Thanks for your help
0
Comment
Question by:rustyrpage
2 Comments
 
LVL 104

Accepted Solution

by:
Sembee earned 400 total points
Comment Utility
You can have as many frontend servers as you like. There is no issue with numbers.
Do ensure that they are patched to the same level as the backends. If the backends went through Exchange 2003 SP1 and then SP2, then repeat that and any additional updates.

Ports wise, most things run through 443 - you will need to open 25 for SMTP, 110 for POP3 and 143 (IIRC) for IMAP.

The name of the computer doesn't matter - the only thing that matters is that the DNS resolves.

On your final question - that isn't possible. Exchange doesn't route based on sender, only on destination.

Microsoft have a white paper on Exchange 2003 frontend/backend scenarios. You can download it from their Technet site.

Simon.
0
 
LVL 13

Assisted Solution

by:cshepfam
cshepfam earned 100 total points
Comment Utility
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
Local Continuous Replication is a cost effective and quick way of backing up Exchange server data. The following article describes the steps required to configure Local Continuous Replication. Also, the article tells you how to restore from a backup…
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…
This video discusses moving either the default database or any database to a new volume.

743 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

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now