Hub Transport Server Role: Overview
Applies to: Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1, Exchange Server 2007
Topic Last Modified: 2006-09-14
In Microsoft Exchange Server 2007, the Hub Transport server role is required.
|In pre-release versions of Exchange 2007, the Hub Transport server role was referred to as the Bridgehead server role.|
Deployed inside your Active Directory directory service forest, the Hub Transport server role handles all mail flow inside the organization, applies transport rules, applies journaling policies, and delivers messages to a recipient's mailbox. Messages that are sent to the Internet are relayed by the Hub Transport server to the Edge Transport server role that is deployed in the perimeter network. Messages that are received from the Internet are processed by the Edge Transport server before they are relayed to the Hub Transport server. If you do not have an Edge Transport server, you can configure the Hub Transport server to relay Internet messages directly. You can also install and configure the Edge Transport server agents on the Hub Transport server to provide anti-spam and antivirus protection inside the organization.
The Hub Transport server role stores all its configuration information in Active Directory. This information includes transport rules settings, journal rule settings, and connector configurations. Because this information is stored in Active Directory, you can configure settings one time, and then those settings are applied by every Hub Transport server in the organization.
You can install the Hub Transport server role on the same hardware with any other non-clustered internal server role or on a server that is dedicated to the Hub Transport server role. You must deploy a Hub Transport server role in each Active Directory site that contains a Mailbox server role. Deploying more than one Hub Transport server per site provides redundancy if a server fails. When you install more than one Hub Transport server in an Active Directory site, the connections are distributed.
The message-processing scenarios that you can manage on the Hub Transport server role are described in the following sections.
The Hub Transport server role processes all messages that are sent inside the Exchange 2007 organization before the messages are delivered to a recipient's Inbox or are routed to users outside the organization. There are no exceptions to this behavior; messages are always passed through a server that runs the Hub Transport server role.
Messages are submitted to the Hub Transport server in three ways: through Simple Mail Transfer Protocol (SMTP) submission, from the Pickup directory, or when a user inside the organization sends a message, and that message is picked up from the user's Outbox by the store driver, a software component of the Hub Transport server that delivers inbound messages to Exchange stores, the databases that contain public folder and mailbox stores.
When messages are submitted to the Hub Transport server, they are processed by the categorizer. The categorizer is a component of Exchange transport that processes all inbound messages and determines what to do with the messages based on information about the intended recipients. In Exchange 2007, the Hub Transport server uses the categorizer to expand distribution lists and to identify alternative recipients and forwarding addresses. After the categorizer retrieves full information about the recipients, it uses that information to apply policies, route the message, and perform content conversion. Messages are then delivered locally by the store driver to a recipient's mailbox, or they are delivered remotely by using SMTP to send messages to another transport server. Messages that are sent by users in your organization are picked up from the sender's Outbox by the store driver and are put in the Submission queue on a server that runs the Hub Transport server role. For more information, see Transport Architecture.
A collection of transport agents lets you configure rules and settings that are applied as messages enter and leave the mail flow components. You can create messaging policy and rule settings that are designed to meet different regulations and that can easily be changed to adapt to your organization's requirements. The transport-based messaging policy and compliance features include server-based rules that you configure to enforce your organization's compliance scenarios and the Journaling agent that acts to enforce message retention. For more information, see Planning for Hub Transport Features.
The Exchange 2007 Built-in Protection features provide anti-spam and antivirus protection for messages. Although these Built-in Protection features are designed for use in the perimeter network on the Edge Transport server role, the Edge Transport agents can also be configured on the Hub Transport server. By default, these agents are not enabled on the Hub Transport server role. To use the anti-spam features on the Hub Transport server, you must register the agents in a configuration file and enable the features that you want to use by running a provided Exchange Management Shell script. You install and enable the antivirus agent in a separate operation. For more information, see Planning for Anti-Spam and Antivirus Features.