An Edge Subscription subscribes an Exchange Server 2013 Edge Transport server to an Active Directory site. This automatically creates the required connectors for internet mail flow to occur inbound and outbound via the Edge Transport server and the Mailbox servers in that Active Directory site.
On the Edge Transport server create an Edge Subscription file.
[PS] C:\>New-EdgeSubscription -FileName C:\Admin\Edge.xml Confirm If you create an Edge Subscription, this Edge Transport server will be managed via EdgeSync replication. As a result, any of the following objects that were created manually will be deleted: accepted domains, message classifications, remote domains, and Send connectors. After creating the Edge Subscription, you must manage these objects from inside the organization and allow EdgeSync to update the Edge Transport server. Also, the InternalSMTPServers list of the TransportConfig object will be overwritten during the synchronization process. EdgeSync requires that this Edge Transport server is able to resolve the FQDN of the Mailbox servers in the Active Directory site to which the Edge Transport server is being subscribed, and those Mailbox servers be able to resolve the FQDN of this Edge Transport server. You should complete the Edge Subscription inside the organization in the next "1440" minutes before the bootstrap account expires. [Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "Y"): y
Copy the Edge Subscription file to a Mailbox server in the organization Import the Edge Subscription file by running the following command.
[PS] C:\>New-EdgeSubscription -FileData ([byte[]]$(Get-Content -Path "C:\Admin\Edge.xml" -Encoding Byte -ReadCount 0)) -Site "DataCenter1"
In my example “DataCenter1″ is the name of the Active Directory site that hosts the Mailbox servers that I want to participate in EdgeSync with the Edge Transport server. If you have multiple Edge Transport servers (for high availability) you simply repeat the process of creating the Edge Subscription file on each Edge Transport server and then subscribing it to the Active Directory site.
Note: If you add a new Mailbox server to the site it will not participate in EdgeSync until you resubscribe the Edge Transport server to the site.
Removing Other Send Connectors
If you’ve previously configured send connectors for outbound email you may need to take additional steps to remove them after you’ve deployed your Edge Transport server.
For example, here you can see the two EdgeSync connectors that were automatically created, and the existing “Internet Email” send connector as well. At the moment outbound email will still go out via the “Internet Email” connector.
[PS] C:\>Get-SendConnector
Identity AddressSpaces Enabled
-------- ------------- -------
Internet Email {SMTP:*;1} True
EdgeSync - DataCenter1 to Internet {smtp:*;100} True
EdgeSync - Inbound to DataCenter1 {smtp:--;100} True
Remove any unnecessary send connectors so that mail will flow via the Edge Transport server.
[PS] C:\>Remove-SendConnector "Internet Email" Confirm Are you sure you want to perform this action? Removing Send connector "Internet Email". [Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"): y
Verify Outbound Email
You can verify that outbound email is flowing via the Edge Transport server by sending an outbound message, then copying the message headers from the received message into a header analyzer such as MXToolbox or ExRCA.
Verify Inbound Email
For inbound email you will need to ensure that your MX records point to the public IP address for your Edge Transport server (which may be a NATed IP address behind a firewall or other network device). To verify inbound mail flow send an email from an external address or use the inbound SMTP test on ExRCA.
This article Configuring an Edge Subscription for Exchange Server 2013 is © 2014 ExchangeServerPro.com
Get more Exchange Server tips at ExchangeServerPro.com
