Posted by: B00M3R
C:\subscription.xml, Edge Synchronization, Exchange, Exchange Edge, InternalSMTPServers, Message Classifications, Microsoft Exchange Performing an Edge Synchronization, New-EdgeSubscription file, Performing an Edge Synchronization, Setting up Edge Synchronization, Setting up edge ynchronisation, TransportConfig Objects, XML Edge File
OK so lets say now we have installed Exchange 2007 in a way that will allow it to perform the edge transport server role. The problem is that right now, the server is completely isolated. It is not a member of an Active Directory domain, nor is it aware of the existence of your Exchange Server organization. We need to configure Exchange in a way that will allow communications between the edge transport server and the rest of the Exchange Server organization without actually making the edge transport server a part of the organization.
To do this, we must create an edge synchronization. An edge synchronization is essentially a one way trust relationship. The edge transport server trusts the Active Directory, but the Active Directory does not trust the edge transport server.
Creating an edge synchronization involves creating an XML file that contains pertinent information about the edge transport server. This information is then imported into the Active Directory, to make the Active Directory aware of the edge server s existence.
Before I show you how to perform the edge subscription, I need to warn you about a couple of things. First, creating an edge synchronization overwrites anything that you have manually configured on the edge transport server. Specifically, the following objects and types of information are overwritten:
- Accepted Domains
- Message Classifications
- Remote Domains
- Send Connectors
- The Server s InternalSMTPServers list of TransportConfig Objects
Once you implement the edge synchronization, Exchange will also configure itself so that you can t use the Exchange Management Shell to configure any of these types of objects on the edge transport server. This is a security precaution designed to prevent scripting attacks. You will still be able to manage the server through the Exchange Management Console though.
Ok let s create the edge subscription. To do so, we need to begin by creating an XML file that can be used for the subscription process. To do so, open the Exchange Management Shell, and enter the following command:
New-EdgeSubscription file C:\subscription.xml
When you enter this command, Exchange will display a warning….Press Y, and Exchange will create the edge subscription file (named subscription.xml) and place it in the server s root directory.
Now, copy the XML file that you just created to removable media, and delete the file from the edge server. Deleting the file is extremely important for security reasons. Finally, insert the removable media into your hub transport server, so that you can create the edge subscription.
You can complete the process by opening the Exchange Management Console and navigating through the console tree to Organization Configuration | Hub Transport. Now, click on the New Edge Subscription link, found in the Actions pane. When you do, Exchange will launch the New Edge Subscription Wizard. The wizard prompts you for the name and path of the subscription file that you created earlier. Once you supply this information, verify that the Automatically Create a Send Connector for this Edge Subscription check box is selected, and then click the New button and we are done.