Configure the Edge Servers

  • Article
Cc526574.chm_head_left(en-us,TechNet.10).gif Cc526574.chm_head_middle(en-us,TechNet.10).gif Cc526574.chm_head_right(en-us,TechNet.10).gif

Configure the Edge Servers

The Edge Transport server role differs from other Microsoft Exchange Server 2007 server roles in several important ways that you must consider when you plan your deployment. The Exchange Server 2007 Edge Transport server does not have access to Active Directory for storage of configuration and recipient information as do the other Exchange Server 2007 server roles. The Edge Transport server uses the Active Directory Application Mode (ADAM) to store configuration and recipient information. The Edge Transport server is deployed outside the Exchange organization in the perimeter network and can provide Simple Mail Transfer Protocol (SMTP) relay and smart host functionality. The Edge Transport server also has an important role in providing anti-spam and antivirus functionality for the Exchange organization.

Tasks

  1. Replicate Organization Data to the first Edge Server using EdgeSync

Prerequisites

Verify that the network firewall that separates the Edge Transport server from the Exchange Server 2007 Hub Transport server(s) is configured to enable communications through the correct ports. The Edge Transport server uses custom LDAP ports. The following ports are needed for the directory synchronization:

  • LDAP: Port 50389/TCP
  • Secure LDAP: Port 50636/UDP
  • SMTP: Port 25/TCP
  • Optional: enable RDP: Port 3389/TCP

Replicate Organization Data to the First Edge Server Using EdgeSync

EdgeSync is a collection of processes that run on the Exchange Server 2007 Hub Transport server role. EdgeSync establishes one-way replication of recipient and configuration information from the Active Directory directory service to the Active Directory Application Mode (ADAM) instance, on a computer that has the Edge Transport server role installed. An Edge Transport server subscribes to an Active Directory site, and is associated with the Hub Transport servers in that site in order to configure the connectors that are replicated to ADAM during this process. The Hub Transport servers in the organization will then route messages that are being delivered to the Internet to the site with which the Edge Transport server is associated, for relay to the Edge Transport server and then to the Internet.

Procedure DWHE.91: To export the EdgeSync subscription file

  1. Log on to EXEDGE01 as a member of the local Admins group.

  2. Open the Exchange Management Shell.

  3. Run the following command: `

    New-EdgeSubscription -FileName "C:\EdgeSubscriptionInfo.xml"
`

  1. Copy the Edge Subscription file from the Edge Transport server to the Hub Transport server (EXHUB01).

    Note

    It is a best practice to delete the Edge Subscription file from the Edge Transport server after you copy it to the Hub Transport server.

In the following procedure you configure the Edge Transport server ExEDGE01 to use DNS01 for External DNS Name resolution.

Procedure DWHE.92: To configure External Name Resolution on the Edge Transport server

  1. Open the Exchange Management Shell on EXEDGE01.
  2. Run the following command: <pre IsFakePre="true" xmlns="https://www.w3.org/1999/xhtml">Set-TransportServer -Identity ExEdge01 –ExternalDNSAdapterEnabled $false –ExternalDNSServers &lt;IPAddress of DNS01&gt;</pre>

Procedure DWHE.93: To verify name resolution between the Hub Transport server and Edge Transport server

  1. Log on to EXHUB01 as a member of the Domain Administrators group.

  2. Open a command prompt.

    Note

    The Hub Transport server must be able to resolve the fully qualified domain name (FQDN) of the Edge Server or the Edge Subscription will not work correctly.

  3. Ping the fully qualified domain name (FQDN) of the first Edge server (EXEDGE01) server. Do not proceed until you are certain that the Hub server can resolve the FQDN of the Edge server.

Procedure DWHE.94: To create the EdgeSync Subscription on the Hub Transport Server

  1. Open the Exchange Management Shell on EXHUB01.

  2. Navigate to the Edge Subscription file.

  3. Run the following command: <pre IsFakePre="true" xmlns="https://www.w3.org/1999/xhtml">New-EdgeSubscription -filename "C:\EdgeSubscriptionInfo.xml" -CreateInternetSendConnector $true -site "Default-First-Site-Name"</pre>

  4. Review the response to make sure the Edge Subscription was created.

    Note

    It is a best practice to delete the Edge Subscription file from the Hub Transport server after you have successfully imported it.

Procedure DWHE.95: To add an accepted SMTP domain

Accepted Domains are added on the Hub Transport server, and are automatically replicated to the Edge server via the Edge subscription.

  1. Open the Exchange Management Shell on EXHUB01.
  2. Run the following command: <pre IsFakePre="true" xmlns="https://www.w3.org/1999/xhtml">New-AcceptedDomain -Name "ConsolidatedMessenger" -DomainName consolidatedmessenger.com -DomainType Authoritative </pre>

Procedure DWHE.96: To manually trigger Edge Synchronization

EdgeSync synchonizes the list of accepted SMTP domains once per hour. The synchronization of recipient data occurs at four-hour intervals. Use the Start-EdgeSynchronization cmdlet to immediately start synchronization of configuration data from the Active Directory directory service to the subscribed computers that have the Edge Transport server role installed.

  1. Open the Exchange Management Shell on EXHUB01.
  2. Run the following command: <pre IsFakePre="true" xmlns="https://www.w3.org/1999/xhtml">Start-EdgeSynchronization</pre>