Q
Problem solve Get help with specific problems with your technologies, process and projects.

Using one-way connection agreements from Exchange 5.5 to AD

Expert Peter terSteeg discussed the issues involved with using one-way connection agreements from Exchange 5.5 to Active Directory.

We are in the process of planning our migration from Exchange 5.5 to Exchange 2003. Our Exchange architecture is decentralized, consisting of 35 sites worldwide with a total of 10,000 mailboxes. We plan to be in a coexistence phase for approximately six months.

One of our architects had planned a design based on the Active Directory Connector (ADC) using one-way connection agreements (from Exchange 5.5 to Active Directory). Although this is simple in terms of the number of connection agreements we need, I have concerns, since the recommended approach is to configure two-way connection agreements.

What are the critical issues, if any, with one-way connection agreements regarding a migration that is as involved as ours?

VIEW MEMBER FEEDBACK TO THIS ASK THE EXPERT Q&A.

I think there might me a lot of additional detail that isn't being included in the question posted to the forum. One-way connection agreements will definitely protect your production source environment in the event something happens to the target. So, it could be that one-way connection agreements were decided on because the ability to control and manage the new target environment was unknown. Also, one-way connection agreements most likely simplified the overall structure of the migration prep and planning work to configure the ADC for use in the environment.

Is there some downside? Sure. Changes from Active Directory will not be reflected in objects that still primarily exist in Exchange 5.5.


MEMBER FEEDBACK TO THIS ASK THE EXPERT Q&A:

We performed a similar migration last summer. You may want a two-way or two one-way agreements per site (the former is not recommended by Microsoft, but we did it that way for more control) to update your Exchange 5.5 side to reflect the new homeserver/mailbox information of the migrated user and modifications -- additions made to the Exchange 2003 side. Otherwise, the Exchange 5.5 user gets "account does not exist in the organization" when sending to an Exchange 2003 user. You can also check off the "do not delete" button on the connector to prevent accidental deletions on the Exchange 5.5 side.
—Keith G.


Do you have comments on this Ask the Expert Q&A? Let us know.
Related information from SearchExchange.com:

  • 11 tips in 11 minutes: Migrating from Exchange 5.5 to Exchange Server 2003
  • Tip: From Exchange 5.5 to 2003 in a single bound
  • Expert Advice: Setting up Connection Agreements
  • Resource Center: More migration advice

  • Dig Deeper on Exchange Server setup and troubleshooting

    Have a question for an expert?

    Please add a title for your question

    Get answers from a TechTarget expert on whatever's puzzling you.

    You will be able to add details on the next page.

    Start the conversation

    Send me notifications when other members comment.

    Please create a username to comment.

    -ADS BY GOOGLE

    SearchServerVirtualization

    SearchCloudComputing

    SearchSQLServer

    SearchEnterpriseDesktop

    SearchVirtualDesktop

    Close