Introduction to the Exchange 2007 Edge Transport server role

by Scott Lowe MCSE | Dec 01, 2006 8:00:00 AM

Tags: Servers, Scott Lowe MCSE, Microsoft Exchange Server 2007, Edge Transport, server, E-mail Administration Tips Newsletter

Takeaway: The Edge Transport service takes a little getting used to, but provides services that are important for an organization of any size. Here's some information you need to know.

In my previous tips, I've given brief excerpts describing the roles provided by the now role-ified Exchange Server 2007. With the exception of the Unified Messaging role, the Edge Transport server role is the most exceptional in that it endows Exchange 2007 with a number of features not available in previous versions of the server. In this tip, I'll explain the role (pun intended) of the Edge Transport server role.

First, this role is not required. While the Edge Transport server role is responsible for Internet mail handling, if you decide you don’t want the services (described later) offered by this role, you can configure the Hub Transport role to assume the duties of Internet mail gateway. Just understand that you will lose the benefits provided by Edge Transport.

Second, I’ll talk about the things that make this role unique. First, the server on which you install this role can have no other Exchange Server roles installed. The Edge Transport role must live by itself. Furthering its isolation, this role must be installed onto a server at the edge of your network that is not a part of your Active Directory domain. Now, at this point, you may be wondering just how this server can communicate with your other Exchange servers since the new server isn’t a part of your AD infrastructure. As an edge server designed to handle mail coming into (and out of) the organization, it would make sense that this server needs pretty tight communication with the rest of your network.

The necessary integration with your Exchange and AD environment is accomplished by using ADAM--Active Directory Application Mod--services along with a component called EdgeSync that runs on a separate server that has the Hub Transport role installed. EdgeSync performs regular one-way synchronization of recipient and configuration information from AD to the ADAM instance running on the Edge Transport server.

The Edge Transport server sees every message that comes into and goes out of your organization. This server is the one to which your domain’s MX record should point and Exchange will automatically route outgoing mail through this service as well.

Edge Transport is designed to limit possibility of virus outbreak and to reduce spam. The antivirus/antispam services provided or made possible by the Edge Transport role are pretty impressive and include:

• Content filtering
• White listing (Safe Sender List Aggregation)
• Connection and recipient filtering
• Edge transport rules

Microsoft also makes available Forefront Security for Exchange Server, a product that tightly integrates with Exchange 2007. I imagine that other antivirus vendors will release similar products, if they haven’t already by the time you read this.

Due to its nature, the Edge Transport service takes a little getting used to, but provides services that are important for an organization of any size.

Print/View all Posts Comments on this article

Exchange 2007 roles jbaker@... | 12/04/06