After the first six sections, your Migration Plan should contain sections and subsections that describe suitable choices for all relevant topics in chapter 3 of this guide: Other strategic planning issues.
Most migrations follow a similar basic process with variations to accommodate circumstances and needs—a migration scenario. It is critical that you understand and characterize your scenario before you begin migration planning because your scenario will influence the decisions about the processes and methods you use to accomplish the migration. Most variations to the basic process result from:
• |
• |
Pre-Migration State of Existing Local Active Directory: Part of the migration process depends on whether your organization already has local Active Directory running for login and security purposes and, if so, the state of any objects provisioned there. |
• |
If migrating to proprietary Exchange: Do you already have Active Directory up and running? If AD is already provisioned, are its objects already mail-enabled, mailbox-enabled, or neither? |
• |
If migrating to Office 365: Will you use a proprietary local Active Directory to provision the hosted environment and, if so, will you keep the local AD active after the migration? This method of provisioning permits single sign-on, also called identity federation, so users can access Office 365 services with the same credentials they use for local Active Directory. Alternatively, you could provision Office 365 without local AD, by using Migrator for Notes to Exchange to provision Office 365 directly from the Notes/Domino source. |
Different combinations of target types and existing local AD can produce an array of migration scenarios. The Migrator for Notes to Exchange Scenarios Guide describes the combinations and explains the migration procedures for each:
The MNE Scenarios Guide also describes three special scenarios that can occur in combination with one of the previously listed scenarios:
• |
Offline Migration: A strategy in which Notes source data, previously extracted from Notes, is migrated directly to the Exchange target. An offline strategy can be valuable if |
• |
• |
Phased (Staged) Migration Options: A phased migration strategy is one in which all but the most recent source data is "pre-migrated" to Exchange while users remain active in Notes. The remaining Notes data (a much smaller volume) can be migrated much faster—often all users can be migrated together in a final "cutover" migration. Users continue to receive and send mail and manage their calendars in Notes throughout the transition period while their older data is migrated to Exchange. If the final cutover can be accomplished in a single day or weekend, this strategy can eliminate the need for email, calendar, and free/busy coexistence. |
• |
Silent Mode Options: A strategy to configure the MNE Self-Service Desktop Migrator (SSDM), the per- desktop migration application, to hide some or all of its screens and retrieve its required values from a configured .ini file, eliminating or minimizing any need for interaction with the end user. |
Characterize your migration scenario in the first section of your Migration Plan.
Provisioning includes mail-enabling and/or mailbox-enabling the objects in the target AD. An Active Directory object is said to be mail-enabled when the AD object record contains a forwarding address to which mail can be routed (i.e., to the user Notes address). An object is said to be mailbox-enabled when an Exchange mailbox is created for it.
Other MNE wizards can mailbox-enable the AD accounts and provision groups in AD.
When provisioning a local Active Directory, be sure to provision all Notes users into AD as mail-enabled objects, without Exchange mailboxes before you migrate the first user. Provisioning mail-enabled objects into AD will facilitate Exchange-to-Notes mail forwarding, to correctly route mail that arrives (or originates) in Exchange for not-yet-migrated Notes recipients. But Exchange mailboxes would disable Exchange-to-Notes free/busy queries: Exchange cannot send free/busy queries to an external server for a user who already has an Exchange mailbox.
This Exchange free/busy restriction becomes irrelevant if you defer creating user mailboxes until before their migration, several steps later. The standard scenario procedures (in chapter 2 of the Migrator for Notes to Exchange Scenarios Guide) follow this approach for provisioning local proprietary Active Directory.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center