New Transport Features in Exchange 2007 SP1
Applies to: Exchange Server 2007 SP1
Topic Last Modified: 2007-08-22
Microsoft Exchange Server 2007 Service Pack 1 (SP1) includes several enhancements to transport functionality. Some of these enhancements affect the Hub Transport server role, some affect the Edge Transport server role, and some affect the core transport functionality that is common to the Hub Transport server role and the Edge Transport server role.
Exchange 2007 SP1 includes the following enhancements to core transport functionality:
- Back pressure Back pressure is a system resource monitoring feature for the Hub Transport server role and the Edge Transport server role. This feature enables the Hub Transport servers and Edge Transport servers to respond to high resource use. In Exchange 2007 SP1, the free disk space requirement has changed from 4 GB to 500 MB. For more information, see Understanding Back Pressure.
- Additional configuration options in the Exchange Management Console In Exchange 2007 SP1, you can configure more transport feature settings in the Exchange Management Console. For more information, see Configuring Transport Server Properties.
Exchange 2007 SP1 includes the following enhancements to message processing and routing functionality on the Hub Transport server role:
- Priority queuing The message priority that is assigned to a message by an Outlook user is now considered by the categorizer. This helps ensure that messages sent with high importance receive priority handling and are delivered more quickly than messages with a low importance setting. For more information, see Understanding Priority Queuing in Exchange 2007 SP1 and SP2.
- Active Directory site links The Set-AdSiteLink cmdlet is used to configure Exchange-specific settings on an Active Directory site link. In Exchange 2007 SP1, the Set-AdSiteLink cmdlet includes the MaxMessageSize parameter. This parameter lets the administrator restrict the maximum message size for messages that are relayed between Active Directory directory service sites.
- Routing group connectors When Exchange 2007 coexists with Microsoft Exchange Server 2003 or Exchange 2000 Server, routing group connectors are used to relay messages between the Exchange 2007 routing group and legacy routing groups. In Exchange 2007 SP1, the New-RoutingGroupConnector cmdlet and the Set-RoutingGroupConnector cmdlet include the MaxMessageSize parameter. This parameter lets the administrator restrict the maximum message size for messages that are relayed between Exchange 2007 Hub Transport servers and Exchange 2003 or Exchange 2007 bridgehead servers.
- Send connector configuration In Exchange 2007 SP1, the scoping of a Send connector to a single Active Directory site is simplified by the addition of the IsScopedConnector parameter in Exchange Management Shell cmdlets and the Scoped send connector check box in the Exchange Management Console. When a Send connector is scoped, only the Hub Transport servers in the same Active Directory site as the Send connector's source servers consider that Send connector in routing decisions.
- AD RMS Prelicensing agent Exchange 2007 SP1 includes the AD RMS Prelicensing agent. You can enable this Windows Rights Management Services (RMS) agent on the Hub Transport server to provide better functionality for letting Outlook users access protected messages. For more information, see Managing the AD RMS Prelicensing Agent.
- X.400 authoritative domains Exchange 2007 SP1 provides support for configuring an X.400 address space as an authoritative domain and also provides support for X.400 long addresses. For more information, see Exchange 2007 SP1 and SP2 Support for X.400 Authoritative Domains.
- Transport rules Exchange 2007 SP1 enables transport rules to act on Unified Messaging messages, such as voice mail, fax messages, and missed call notifications. For more information about transport rules, see Overview of Transport Rules.
Exchange 2007 SP1 includes the following enhancements to the Edge Transport server role:
Exchange 2007 SP1 includes the following enhancements to the EdgeSync cmdlets that improve usability for the administrator:
- Start-EdgeSynchronization The Start-EdgeSynchronization cmdlet is used to immediately begin synchronization of data from Active Directory to the Active Directory Application Mode (ADAM) directory service. In Exchange 2007 SP1, support for the Server parameter has been added to this cmdlet to let the administrator run the cmdlet from a remote computer.
- Test-EdgeSynchronization The Test-EdgeSynchronization cmdlet is a diagnostic cmdlet that provides a report of the synchronization status of subscribed Edge Transport servers. In Exchange 2007 SP1, an additional parameter set enables the administrator to verify synchronization results for individual users.
For more information, see Understanding the EdgeSync Synchronization Process.
The cloned configuration scripts enable administrators to apply a consistent configuration when more than one Edge Transport server is deployed. In Exchange 2007 SP1, the information that is cloned now includes the TransportConfig object. The TransportConfig object controls server-wide settings for the Edge Transport server role. By including this object in the cloned configuration information, server deployment, backup, and restore procedures are streamlined. For more information, see Using Edge Transport Server Cloned Configuration.