When you are finished with this batch ...
Repeat these steps for each batch of migrating users until the entire user population is migrated. You may also integrate some of the Pre-Migration Preparations into this process, depending on your circumstances. When you have migrated the last user batch, proceed to the Post-Migration Activities.
Post-migration activities
These post-migration activities apply to migrations to Office 365. Perform these tasks only after you have migrated the last user batch (by the Admin Batch Migrator) or the last individual user (by the SSDM).
Step 1: Provision public distribution lists in Exchange
Run Migrator for GroupWise’s Administrator-Driven Batch Migrator to provision GroupWise public distribution lists (PDLs) as Exchange distribution groups. The program reads a GroupsToProvision.txt data file, generated by the Directory Exporter, to provision PDLs into Office 365. If necessary, you can update PDL content and/or membership in the GroupsToProvision.txt file prior to provisioning the PDLs into Active Directory.
PDLs are typically provisioned in Office 365 separately, after users are migrated in the batch-migration process. For more information and field notes, see the Administrator-Driven Batch Migrator chapter of the Migrator for GroupWise Administration Guide.
After your distribution lists are provisioned into Office 365, check the Message Delivery Restrictions settings for any Exchange (Office 365) group to which you want GroupWise users to be able to send messages. Any such Exchange group must be of the universal distribution type to be mail-enabled. To change the settings, beginning in the Office 365 Exchange admin center:
|
1 |
Select recipients (in the navigation bar at left), and then groups. Then select and double-click the Distribution group you want to edit. |
|
2 |
Click the delivery management tab, and select the radio button for Sender inside and outside of my organization. |
