?
Solved

Setting up a new Front-End Exchange Server

Posted on 2007-12-06
2
Medium Priority
?
855 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
[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 Comments
 
LVL 104

Accepted Solution

by:
Sembee earned 1600 total points
ID: 20422092
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 400 total points
ID: 20422332
0

Featured Post

Office 365 Training for Admins - 7 Day Trial

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

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

In-place Upgrading Dirsync to Azure AD Connect
I don't pretend to be an expert at this, but I have found a few things that are useful. I hope that sharing them here will help others, so they will not have to face some rather hard choices. Since I felt this to be a topic of enough importance and…
To show how to generate a certificate request 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 >> Certificates…
This video discusses moving either the default database or any database to a new volume.

719 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