Force EdgeSync Synchronization
To force EdgeSync synchronization, run the following command from the Exchange Management Shell on the Hub Transport server:
Configuring Target DNS Server for Mail Forwarding
After you have completed setting up the target Exchange 2007/2010 organization for Internet mail flow between target and source Exchange organizations, you should also add the Mail Exchanger (MX) record for the target domain to the DNS server. This is necessary to forward the mail (redirected to the additional SMTP addresses added by the Directory Synchronization Agent) to the target Exchange 2007/2010 server.
We will use the following additional address space given as example on the steps above:
- @target.local—to redirect mail from source to target mailboxes. A secondary SMTP address will be added to each target mailbox by the Directory Synchronization Agent according to this template.
To set MX record for the target domain
- In the DNS snap-in, connect to the target DNS server and browse to the Forward Lookup Zones container.
- Right-click the Forward Lookup Zones and select New Zone.
- In the New Zone wizard, select the Primary zone to be created.
- Type local for the Zone name and complete the wizard.
- Right-click the zone object local again, and click New Mail Exchanger on the shortcut menu.
- In the New Resource Record dialog box, type target for the Host or child domain.
- Click Browse and select the Exchange server in the target domain to which mail sent to the @target.local domain will be redirected.
- Click OK.
Testing the SMTP Connectors (Optional)
After both source and target Exchange organizations have been set up for Internet mail flow as well as both source and target DNS servers have been configured for mail forwarding, it is recommended to test the connection between the source and the target organizations.
Caution: This step should be performed in coordination with the administrator of the Exchange organization.
To test the SMTP connectors:
- Create test mailboxes on the source and target Exchange servers. In this example, both mailboxes will be called mbx1.
- Set the same primary SMTP address for both mailboxes.
- In this example the primary address for both mailboxes will be mbx1@Westland.Exchange.com.
- Set additional addresses for both mailboxes.
- In this example additional address for the source mailbox will be firstname.lastname@example.org, and email@example.com for the target mailbox.
- Create a contact on the source Exchange server and point it to the additional SMTP address of the target Exchange mailbox (firstname.lastname@example.org).
- Create a contact on the target Exchange server and point it to the additional SMTP address of the source mailbox (email@example.com).
- Open the test source mailbox and send a message to the source contact.
- Open the test target mailbox and make sure that the message has arrived.
- From the test target mailbox, send a message to the target contact, and make sure the e-mail has reached the source test mailbox.
Appendix A: Exchange 2003 to Exchange 2007 Migration Restrictions
Public folder stores are no longer mandatory for Exchange 2007 organizations. However, if Exchange 2007 organization does not have a public folder store and MSA or CSA is installed directly on the source Exchange 2003 server, then the Exchange 2003 to Exchange 2007 migration scenario is not supported.
To work around that issue, you need to use separate agent hosts for MSA or CSA instead of installing them directly on the source Exchange 2003 server.
NOTE: For detailed information about system requirements for agent hosts, see the Exchange Migration Agents section of the System Requirements and Access Rights document.