Preparing to Run the Microsoft Exchange EdgeSync Service
Microsoft Exchange Server 2007 will reach end of support on April 11, 2017. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.
Applies to: Exchange Server 2007, Exchange Server 2007 SP1, Exchange Server 2007 SP2, Exchange Server 2007 SP3
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 Application Mode (ADAM) directory service instance on a computer that has the Edge Transport server role 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.
When the New-EdgeSubscription command is run on the Edge Transport server to export the Edge Subscription file, any objects that will be replicated from Active Directory to ADAM by the Microsoft Exchange EdgeSync service are removed from the Edge Transport server. After you import the Edge Subscription file on the Hub Transport server, recipient and configuration data is replicated from Active Directory to ADAM. Therefore, you must configure settings on the Hub Transport server to populate the settings on the Edge Transport server.
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.
Before You Begin
Verify that the perimeter network firewall that separates the Edge Transport server from the Exchange organization is configured to enable communications through the correct ports. The Edge Transport server uses non-standard Lightweight Directory Access Protocol (LDAP) ports. By default, these ports are configured when the Edge Transport server role is installed. You can modify the ports that are used by ADAM by using the ConfigureAdam.ps1 script that is provided with Exchange 2007. However, do not modify the ports after you create the Edge subscription. If you modify the ports after you create the Edge subscription, you must remove the Edge Subscription and then create a new subscription. By default, the following LDAP ports are used to access ADAM:
LDAP Port 50389/TCP is used locally to bind to the ADAM instance. This port does not have to be open on the perimeter network firewall.
Secure LDAP Port 50636/TCP is used for directory synchronization from Hub Transport servers to ADAM. This port must be open for successful EdgeSync synchronization.
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 Configuring DNS Settings for Exchange 2007 Servers.
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 resubscribe the Edge Transport server.
Important
To resubscribe an Edge Transport server, export a new XML file on the Edge Transport server and then import the XML file on a Hub Transport server. You must resubscribe the Edge Transport server to the same Active Directory site to which it was originally subscribed. You do not have to first remove the original Edge Subscription. The resubscription process will overwrite the existing subscription.
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 following:
- Exchange Organization Administrator role
For more information about permissions, delegating roles, and the rights that are required to administer Microsoft Exchange Server 2007, see Permission Considerations.
Configuring Settings for Propagation to Edge Transport Servers
You configure the following settings for propagation to the Edge Transport server role:
Internal SMTP servers Use the Set-TransportConfig cmdlet to configure the InternalSMTPServers parameter. This parameter specifies a 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.
After the Edge Transport server is subscribed to the Exchange organization, 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 periodically synchronize new, modified, and deleted recipient and configuration data to ADAM. You can also use the Start-EdgeSynchronization cmdlet in the Exchange Management Shell to immediately begin synchronization.
For More Information
For more information, see the following topics: