Groups are typically provisioned separately, after all users are migrated in the Batch migration process (the preceding section of this chapter). Since the only data associated with a group is its member list, group migration consists only of the group being provisioned into the target directory. Use the MNE Groups Provisioning Wizard to provision groups either directly from Notes to Microsoft 365, or to a local “staging” AD from which you can use Microsoft AD Sync tool to provision the groups from the local AD to Microsoft 365.
Before you run the Groups Provisioning Wizard, you can divide the groups into collections using the MNE Collection Wizard for 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 instructions, see the Groups Provisioning Wizard chapter of the Migrator for Notes to Exchange Administration Guide.
To provision groups before all Notes users are migrated, 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.
1 |
In the Exchange Management Console under Recipient Configuration | Distribution Group, select and double-click the group you want to edit. |
2 |
3 |
Clear the check box for Require that all senders are authenticated. |
4 |
Click Save and 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 Microsoft 365 from a local AD using Microsoft AD Sync: Notes users are provisioned into Microsoft 365 as mail-enabled objects in the Pre-migration preparations. |
• |
If you provisioned Microsoft 365 directly from the Notes/Domino source: Notes users are not provisioned into Microsoft 365 until prior to their migration, per user batch. |
To clean up after the last user has been migrated:
1 |
Verify the Notes server is inactive. Ensure 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 Microsoft 365 during the transition. Now that all users have been migrated to Microsoft 365 and inbound traffic is routed directly to Microsoft 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. |
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center