Preparing to run the Microsoft Exchange EdgeSync service

Updated: February 1, 2011

Applies To: Forefront Threat Management Gateway (TMG)

This topic provides information about the configuration that you must perform on the Hub Transport server role, before you subscribe the Edge Transport server to the Microsoft Exchange Server organization. After the Edge Transport server has been subscribed to the Exchange organization, the Microsoft Exchange EdgeSync service periodically replicates recipient and configuration data, from the Active Directory directory service to the Active Directory Lightweight Directory Services instance, on a computer on which the Edge Transport server role is installed. The Microsoft Exchange EdgeSync service that is running on the Hub Transport servers in the Active Directory site to which the Edge Transport server is subscribed, will perform the initial one-way replication and periodic synchronization of new, deleted, and modified data.

Note

After an Edge Transport server is subscribed to the Exchange organization, the tasks that are used to configure the objects that are replicated to the Edge Transport server by the Microsoft Exchange EdgeSync service, are disabled on the Edge Transport server.

Preparing to run the EdgeSync service

  1. Verify that Domain Name System (DNS) host name resolution is successful from the Edge Transport server to the Hub Transport servers, and from the Hub Transport servers to the Edge Transport server. For more information, see:

    Exchange 2007 Exchange 2010

    Configuring DNS Settings for Exchange 2007 Servers

    Configuring DNS Settings for Exchange 2010 Servers

  2. License the Edge Transport server. The licensing information for the Edge Transport server is captured when the Edge Subscription is created, and is shown in the Exchange Management Console for the Exchange organization. For subscribed Edge Transport servers to appear as licensed, they must be subscribed to the Exchange organization after the license key is applied on the Edge Transport server. If the license key is applied on the Edge Transport server after you perform the Edge Subscription process, the licensing information is not updated in the Exchange organization, and you must re-subscribe the Edge Transport server.

  3. On the Hub transport server, configure settings for propagation to the Edge Transport servers:

    Note

    To configure the settings on the Hub Transport server role that are propagated to the Edge Transport server role, the account you use must be delegated the Exchange Organization Administrator role.

    You can configure the following settings for propagation to the Edge Transport server role:

    • Internal SMTP servers—Configure the list of internal SMTP server IP addresses or IP address ranges that should be ignored by Sender ID and connection filtering.

    • Accepted domains—Configure all authoritative domains, internal relay domains, and external relay domains.

    • Remote domains—Configure remote domain settings.

Next Steps

Enabling connectivity for EdgeSync traffic

Tasks

Subscribing the Edge Transport Server to the Exchange Organization