• The Active Directory site to which the Edge Transport server is subscribed must contain at least one Hub Transport server.
  
  
• Verify that you have configured the settings on the Hub Transport server that are replicated to the Edge Transport server. For more information, see Understanding Edge Subscriptions.
  
  
• Read the following topics:
  
  
  • Create an Edge Subscription File on an Edge Transport Server
    
    
  • Understanding Edge Subscriptions
    
    
• Create the Edge Subscription file by running the New-EdgeSubscription cmdlet on the Edge Transport server. By running the New-EdgeSubscription cmdlet, you create an Edge Subscription file that you must copy to your Hub Transport server's hard disk.
  
  
• Copy the Edge Subscription file from the Edge Transport server to the Hub Transport server where you will perform this procedure.
  
  

  Note:
  It's a best practice to delete the Edge Subscription file from the Edge Transport server after you copy the file to the Hub Transport server where you will import the Edge Subscription file, and from the Hub Transport server after the subscription is imported.

• Use the EMC to import the Edge Subscription file
  
  
• Use the Shell to import the Edge Subscription file
  
  

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "EdgeSync" entry in the Transport Permissions topic.

1. In the console tree, navigate to Organization Configuration > Hub Transport.
   
   
2. In the result pane, click the Edge Subscriptions tab.
   
   
3. In the action pane, click New Edge Subscription. On the New Edge Subscription page, complete the following fields:
   
   
   • Active Directory site   Click Browse, and then select an Active Directory site in the drop-down list. This field identifies the Active Directory site where the Hub Transport server is connecting to the Edge Transport server for which the Edge Subscription exists.
     
     
   • Subscription file   Click Browse, and then select an Edge Subscription file.
     
     
   • Automatically create a Send connector for this Edge Subscription   Select this check box to automatically create a Send connector that routes messages from the Exchange organization to the Internet. The Edge Subscription is configured as the source server for the Send connector. The Send connector is configured to route messages to all domains by using Domain Name System (DNS) MX resource records.
     
     
4. Click New to create the new Edge Subscription.
   
   
5. On the Completion page, review the following, and then click Finish to close the wizard:
   
   
   • A status of Completed indicates that the wizard completed the task successfully.
     
     
   • A status of Failed indicates that the task wasn't completed. If the task fails, review the summary for an explanation, and then click Back to make any configuration changes.
     
     

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "EdgeSync" entry in the Transport Permissions topic.

This example subscribes an Edge Transport server to the specified site and creates the Internet Send connector and the Send connector from the Edge Transport server to the Hub Transport servers automatically.

	Copy Code
New-EdgeSubscription -FileData ([byte[]]$(Get-Content -Path "C:\EdgeSubscriptionInfo.xml" -Encoding Byte -ReadCount 0)) -CreateInternetSendConnector $true - CreateInboundSendConnector $true -Site "Default-First-Site-Name"

Note:
The default value of the CreateInternetSendConnector parameter and the CreateInboundSendConnector parameter is $true. It's shown here for demonstration only.

For detailed syntax and parameter information, see New-EdgeSubscription.