The EdgeSync Process

As the Edge Transport Server is not a member of Active Directory, connections between an Edge Transport Server and a Hub Transport Server must be manually performed.  This process is called the EdgeSync process. Essentially, this involves the creation of an EdgeSync XML file on the Edge Transport Server.  This file is then copied over to the Hub Transport Server and imported using either the Exchange Management Shell, or the Exchange Management Console by using a wizard.

The only way to create the EdgeSync XML file is through the Exchange Management Shell on the Edge Transport Server.  To create the file, open the Exchange Management Shell and type “New-EdgeSubscription –FileName” followed by a logical file name like “EdgeSubscriptionInfo.XML” or “EdgeSubInfo.XML”.  The exact file name and location is not important as long as it is copied over to the Hub Transport Server.  Note that there has to be FQDN connectivity between the Hub Transport Server and the Edge Transport Server, and not just physical network connectivity.

Over at the Hub Transport Server, one method of importing the EdgeSync XML file is performed using the Exchange Management Shell.  This is done using the New-EdgeSubscription command to specify the file location as well as the name of the site.  The second, easier method involves using the Exchange Management Console.  From within the Exchange Management Console, expand the Organization Configuration work center.  Click on “Hub Transport” and select the action “New Edge Subscription.”  Select the site from the list shown, browse to the correct EdgeSync XML file and click on “New” to create the subscription process.

Once completed, the Test-EdgeSynchronization Cmdlet can be used to determine if there is a problem between the Edge Transport Server and the Hub Transport Server and if the EdgeSync process can be created.