The next step is to verify that the Edge Transport server has received the necessary information from the Hub Transport server. Since a full directory comparison would be unfeasible, there are a couple of specific things you can spot check to verify that the Edge Transport server is working correctly:
- First, go to the Edge Transport server and open the Exchange Management Console to verify that the send connector was created successfully. The only primary containers you should see in the console tree should be the Edge Transport container and the Toolbox container.
- To make sure that the send connector was created successfully, select the Edge Transport container. The lower half of the details pane will display a series of tabs. Select the Send Connectors tab and verify that a send connector is present and enabled.
If your organization only contains a single Active Directory site, the send connector should look like this:
edgesync – default-first-site-name to Internet Enabled
edgesync – Inbound to Default-First-Site-Name Enabled
As you can see, the send connector actually consists of two different components: an inbound connector and an outbound connector. Both of these connectors should be created automatically.
If for some reason the send connector doesn't exist, you can use the New Send Connector option found on the Actions pane to manually create one (there is also an option to enable the send connector if it is disabled for some reason).
Before you create a send connector though, make sure that the Accepted Domains list has been replicated to the Edge Transport server. If the Accepted Domains list has been synchronized, but there is no send connector, you may have simply forgotten to select the checkbox to automatically create it when you set up the Edge Subscription.
If the send connector is missing and the Accepted Domains list has not been synchronized though, there is clearly some sort of problem occurring.
To check the Accepted Domains list, go to the Hub Transport server, open the Exchange Management Shell, and enter this command:
Get-AcceptedDomain
Exchange Server should return a list of the accepted domains, as shown in Figure C.
Figure C: Get-AcceptedDomain will retrieve a list of the accepted domains.
Now that you have a list of the accepted domains in hand, go to your Edge Transport server, open the Exchange Management Shell and issue the Get-AcceptedDomain command.
The Edge Transport server should produce a list of accepted domains. All you have to do now is to verify that the two lists match each other. If the Edge Transport server contains a partial list of accepted domains, then synchronization is most likely working, but probably has not completed yet.
If you have given synchronization time to complete, but the Accepted Domains list is empty, then there is probably some sort of communications problem between the Edge Transport server and the Hub Transport server.
HOW TO INSTALL AND CONFIGURE AN EDGE TRANSPORT SERVER
Home: Introduction
Step 1: How an Edge Transport server works
Step 2: Install the Edge Transport server
Step 3: Create an Edge Subscription
Step 4: Replicate Active Directory data to the Edge Transport server
Step 5: Verify communication with the Hub Transport server
Step 6: Configure Edge Transport server email filtering agents
Step 7: Set up Edge Transport server advanced content-filtering features
| ABOUT THE AUTHOR: |
|
Brien M. Posey, MCSE
Brien M. Posey, MCSE, is a Microsoft Most Valuable Professional for his work with Exchange Server, and has previously received Microsoft's MVP award for Windows Server and Internet Information Server (IIS). Brien has served as CIO for a nationwide chain of hospitals and was once responsible for the Department of Information Management at Fort Knox. As a freelance technical writer, Brien has written for Microsoft, TechTarget, CNET, ZDNet, MSD2D, Relevant Technologies and other technology companies. You can visit Brien's personal Web site at http://www.brienposey.com. |
|
