Migration involves migrating Active Directory objects (such as users, contacts and groups) from the source domain to Microsoft Office 365, synchronizing calendars and migrating mailboxes from on-premises Exchange organization to Microsoft Exchange Online.
While migrating to Microsoft Office 365 you will need to use both Migration Manager for Active Directory and Migration Manager for Exchange as shown in the figure below:
Migration to Office 365 Considerations:
One instance of Migration Agent for Exchange cannot process collections from on-premises Exchange migration and Microsoft Office 365 migration projects at the same time.
Likewise, one set of public folder synchronization agents cannot process collections from on-premises Exchange migration and Microsoft Office 365 migration projects at the same time.
In the first step of migrating to Microsoft Office 365, you need to provision user accounts in Microsoft Office 365. All steps from this section should be performed in Migration Manager for Active Directory (Office 365) console:
|
Caution: Migration Manager for Active Directory always creates user accounts enabled in Microsoft Office 365 regardless of their states in Active Directory. |
Both migration and synchronization tasks are handled by the specific engine called Directory Migration Agent (abbreviated to DMA). Before you start your migration activities, be sure to install at least one DMA instance in your environment. For that, perform the following:
|
Note: A server where you plan to install DMA must satisfy specific system requirements listed in the corresponding section of the System Requirements and Access Rights document. |
All migration activities are performed between pairs of Active Directory domains and Microsoft Office 365 tenants. Such pairs along with corresponding configuration settings are referred as migration pairs in the console.
To create a new migration pair, perform the following:
|
Note: You can later edit the migration pair settings or delete it using the corresponding action items on the migration pair node in the management tree. |
When you specify a set of configuration settings, it is saved as a specific entity called connection. The connection is a set of configuration settings that are used to access the Active Directory domain or Microsoft Office 365 tenant. You can use connections in future migrations instead of reentering the configuration settings.
By default, when Migration Manager creates a user in Microsoft Office 365 during migration process, it generates a temporary password for the user and then sends it by email. However, you can choose not to send passwords to users. For that, select a migration pair node in the management tree, click the Edit Initial Password Settings item in the Actions pane and select the desired option in the dialog box opened.
|
Caution: Take the following into consideration:
|
|
TIP: You will be able to reset passwords for migrated users later using the Reset Password action item available on the collection node level. Note that when you reset password for a user using Migration Manager for Active Directory, the generated password is sent to the user by email automatically. |
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy