Groups are typically provisioned separately, after all users have been migrated in the Batch migration process (the preceding section of this chapter). Since the only data associated with a group is its member list, the "migration" of a group consists only of its being provisioned into the target directory. We can use Migrator for Notes to Exchange’s Groups Provisioning Wizard to provision groups either directly from Notes to Office 365, or to a local "staging" AD, from which we can then use Microsoft’s AD Sync tool to provision the groups from the local AD to Office 365.
Before running the Groups Provisioning Wizard, you can divide the groups into collections using Migrator for Notes to Exchange’s Collection Wizard for more convenient processing. If necessary, you can update group membership and attributes in the SQL database (via TSV export and import) prior to provisioning the groups into Active Directory. For operating instructions and application notes, see the Groups Provisioning Wizard chapter of the Migrator for Notes to Exchange Administration Guide.
If you need to provision groups before all Notes users have been migrated, be sure to check the Message Delivery Restrictions for any Exchange group to which you want Notes users to be able to send messages. Any such Exchange group must be of the universal distribution type to be mail-enabled. To change settings, beginning in the Exchange Management Console:
1 |
Select the group under Recipient Configuration | Distribution Group, then double-click the group you want to edit. |
2 |
Click the Mail Flow Settings tab, and highlight Message Delivery Restrictions, then click Properties above. |
3 |
De-select the check box for Require that all senders are authenticated. |
4 |
Save, and then restart the Exchange transport service. |
Conditional Step: This step applies only if you will also maintain a local proprietary AD in addition to the hosted platform. |
• |
If you provisioned Office 365 from a local AD using Microsoft’s AD Sync: Notes users are provisioned into Office 365 as mail-enabled objects in the Pre-migration preparations. |
• |
If you provisioned Office 365 directly from the Notes/Domino source: Notes users are not provisioned into Office 365 until just prior to their migration, per user batch. |
To "clean up" after the last user has been migrated:
1 |
Verify the Notes server is inactive. Make sure that the Notes server is no longer processing mail traffic or utilized for active applications. |
2 |
If you were using SMTP mail coexistence: Delete the temporary mail routing MX domain(s) you created in the Pre-migration preparations to support routing between Notes and Office 365 during the transition. Now that all users have been migrated to Office 365 and inbound traffic is routed directly to Office 365, the temporary routing domain(s) should no longer be required. |
3 |
If you no longer need the Notes environment: After you have verified Notes is inactive, you may take a final backup and decommission the environment. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Termini di utilizzo Privacy Cookie Preference Center