Category:Exchange 200x
Last Updated:2011-08-10
This solution requires UnitySync v1.0 or greater:
It is highly recommended you initially set up the necessary connections and run a few test syncs on only a few contacts. In doing so, you can test mail delivery and reply-ability to confirm successful results before resuming syncs of all contacts to the new ex200x domain.
If an Ex55 source or destination directory is migrated to Ex2000, you will need to modify your connections to compensate for this change.
The quick and easy solution is to create a new connection to sync to/from this EX2000 destination. Then, run a first time sync to populate each directory from scratch.
Syncing from scratch may may not be desirable if you wish to transfer Ex55 synced objects to Ex2000 during your migration procedure. In this case, you need to set up a special type of SimpleSync connection that will allow you to link to existing Ex2000 objects if they exist.
It is always recommended you simulate this type of change in a test environment to make sure you get the configuration changes right. Pay particular attention to reply-ability. It may be necessary to customize x500 or legacyexchangedn mappings.
In this example, we'll assume you are using two connections to do a bi-directional sync between two Ex55 directories (connection A writes to the retiring ex55 domain and connection B reads from the retiring Ex55 domain).
I. To replace connection A, you need to create a connection that uses Ex2000 as the destination directory type.
1. Using Connection > Add, design a connection with a destination Map Template of ActiveDir-Contact (mail enabled).
2. This type of connection will link to both Custom Recipients/Contacts and Mailboxes/Users… however if a match is not found, it will create a new Custom Recipient/Contact.
3. If you were using a custom map file for connection A, you will need to create a new custom map file for this new connection, then reapply the customizations. You can NOT use the original custom map file. The original custom map file is designed to create Ex55 objects.
4. If you were using Advanced/Placement to define the destination location to sync to, you will need to adjust the syntax to identify the new Ex2000 directoy. Click Help on the Advanced tab for complete syntax information.
5. Go through each of the other configuration tabs and set the connection up appropriately.
(Attribute Filters, Display Name Format, Source tab, etc).
6. On the Destination tab, you must specify parameters for both "Object Creation" and "Joining with Existing Objects". The use of both of these functions at the same time is referred to as Search Mode. These parameters allow SimpleSync to link to existing objects and create new objects when necessary. Commonly used Join Source/Dest indexes are mail/mail.
II. To replace connection B, you need to create a connection that uses Ex2000 as the source directory type.
1. Using Connection > Add, design a connection with a source Map Template of Active Directory.
2. This type of connection will link to both Custom Recipients/Contacts and Mailboxes/Users… however if a match is not found, it will create a new custom recipient/contact.
3. If you were using a custom map file for connection B, you will need to create a new custom map file for this new connection, then reapply the customizations. You can NOT use the original custom map file. The original custom map file is designed to sync from an EX55 source.
4. If you were using Advanced/Placement to define the location of the synced destination objects, you will need to adjust the syntax. Click Help on the Advanced tab for complete syntax information.
5. Go through each of the other configuration tabs and set the connection up appropriately. (Attribute Filters, Display Name Format, Soruce tab, etc).
6. On the Destination tab, you must specify parameters for both "Object Creation" and "Joining with Existing Objects". The use of both of these functions at the same time is referred to as Search Mode. These parameters allow SimpleSync to link to existing objects and create new objects when necessary. Commonly used Join Source/Dest indexes are mail/mail.
III. Run a Simulation for both connections:
Each Simulation should show ‘MODS’ for any existing destination objects found on the new Ex200x destination directory. If your SIM shows all ADDS, or more ADDS than expected. Consult with Support before running a real sync.
IV. Run both connections:
The first sync will do MODS of all existing destination objects found using the Source/Dest indexes. It will also do ADDS of new entries if necessary. Run the sync again, the sync will run with little or no changes made.
V. Update automated Scripts
You must change your batch script to call the two new Ex2000 connections instead of the original Ex55 connections.
VI. Important note about legacyexchangedn/x500
After syncing, you may notice that while the new contacts work fine when selected from the GAL, replies to old emails may fail, undelivered. Please review the LegacyExchangeDN KB article for the fix.