Chat now with support
Chat with Support

Reference Materials for Migration 8.15 - Tips and Tricks

Introduction Environment Assessment, Planning, and Testing Basic Migration Steps Considerations for Active Directory Migration and Resource Update Considerations for Exchange Migration Preferred Settings for the Directory Synchronization Agent Directory Synchronization Agent Placement Indexing Service Attributes Full Directory Resynchronization Conclusion Environment Preparation Checklist Exchange Migration without Trusts Active Directory Migration without Trusts

Step 2. Start Public Folder and Calendar Synchronization

Synchronize both public folder and calendar data to the target organization before the first user logs on to the target mailbox. This will make the transition transparent.

Perform initial public folder synchronization before starting mailbox migration (Step 3). It may take a few days to complete if there is a large amount of public folder data. By starting this before mailbox migration, you can ensure that all public folder data is available before the first user logs on to the target mailbox.

CAUTION:  In Exchange 2003, the size limit for public folder items is set by default to 10 MB. It is recommended that you increase or remove the size limits before you start the synchronization. Otherwise, if you set a two-way synchronization, you may lose the attachments larger than 10 MB on the source side.

It is best to configure mailbox synchronization but not start it, and then use mailbox synchronization collection members to populate a calendar synchronization collection in a calendar synchronization job. Then start calendar synchronization. Calendar data synchronizes much faster than mailbox data, so if calendar synchronization starts before or at the same time as the first mailbox synchronization, it normally completes for all mailboxes before the first mailbox is switched. That way you can ensure that calendar information is available for any user in any organization, regardless of whether the user’s mailbox is switched.

NOTE: If a mailbox is synchronized in a Remote Users Collection, the whole mailbox content, including the Calendar folder, is transferred to the target server at once by the Mail Source Agent. The mailbox is automatically switched as soon as its content is transferred.

The Calendar Synchronization Agent logs on to all mailboxes in the calendar synchronization job and does not log off until it finishes processing. The Mail Source Agent skips the logged on mailboxes during processing of a Remote Users Collection. Thus, the calendars of the mailboxes migrated in the Remote Users Collections should not be synchronized until these mailboxes are migrated and switched by the Mail Source Agent.

Permissions are synchronized together with public folder and calendar data, so the users have uninterrupted access to the data they need. The ongoing two-way synchronization of public folders and calendars lets users in different organizations share the same public folder data and resource mailboxes.

For more information about public folder synchronization, see the Directory Synchronization topic.

For more information about calendar synchronization, see the Calendar Synchronization topic.

CAUTION:  Deleted public folders cannot be migrated again. If you want to do a pilot public folder migration, create a test public folder and use this folder for your experiments. Avoid doing pilots on the production folders. That way you ensure that the pilot project will not interfere with the production migration in the future.

Step 3. Establish Free/Busy Synchronization (Optional)

Establish free/busy synchronization to enable users to schedule common activities. Migration Manager can synchronize free/busy information independently from other data and thus make sure that the information gets updated as closely to real-time as possible.

Step 4. Synchronize Mailbox Data

Mailbox synchronization can be started at any time after the initial directory synchronization has been completed. However if you want users to have full collaboration capabilities and a consistent view in source and target Exchange organization, public folder and calendar data should exist on the target before either the first mailbox is switched to the target Exchange server or a new user and mailbox are created in the target.

To make migration transparent for all users, Migration Manager provides the Remote Users Collection feature, which allows you to preserve the offline folder (OST) files for remote and laptop users who typically work offline and occasionally connect to their Exchange mailboxes. For the mailboxes processed within a Remote Users Collection, Migration Manager keeps the OST file of the source mailbox and makes the target mailbox use this file after migration. For more information about Remote Users Collections, see the Offline Folder (OST) Files and Remote Users Collections topic.

Step 5. Switch to the New Exchange Mailboxes

When a mailbox is switched, Migration Manager sets redirection to the opposite direction: all new mail sent to the old (source) mailbox is automatically forwarded to the new mailbox in the target organization. Migration Manager also marks the mailbox in a way that initiates the Outlook profile update at the user’s next logon.

Migration Manager can automatically switch mailboxes as they become synchronized. Alternatively, administrator can monitor the synchronization status and schedule the switch for a particular date and time.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating