·Make sure all dependencies exist on the agent machines. For example, if the mappings were changed, then the Agents must be updated with the new configuration files before performing a migration. For instructions about updating the configuration files, see Managing Agents and Workstations.
·If the Distributed Migration model is installed across multiple domains, it is recommended that the connection to the SharePoint site is made with the SharePoint site credentials instead of using the current Users windows credentials. The Agent will use the same credentials and will then be able to access the SharePoint site. Make sure you save the password when you establish the SharePoint connection with the user credentials.
·If the SharePoint site requires another user's credentials, the connection to the SharePoint site will require those credentials in the Metalogix Content Matrix Console connection dialog on the Controller (Host) machine. The Agent will use the same credentials and will then be able to access the SharePoint site.
REMINDER: A connection to SharePoint Online must use an account that is not part of a SharePoint Online Multi-Factor Authentication Policy and that does not use "modern" authentication. (See also Distributed Migration Job Limitations.)
To submit a Distributed Migration job:
1.Open Metalogix Content Matrix Console on the Controller (Host), and verify that you are connected to the Agent Database.
2.Configure and save your migration job on the Controller.
3.From the Job list in the main application window, highlight the row to select the job.
4.From the Job List toolbar, click Run Jobs Remotely to submit the job for Distributed Migration. Alternatively, right-click the selected row to display the pop-up action menu. Select the Run selected job remotely option.
Note: You can select multiple rows to submit more than one job at a time.
IMPORTANT: If Distributed Migration was configured prior to version 8.8, the first time you submit a job remotely, you will be prompted to agree to the terms of a third-party license agreement before being able to continue. (If Distributed Migration was configured in version 8.8 or later, the third-party license agreement is accepted as part of Distributed Migration Configuration.)
The Manage Queue dialog opens. You can now monitor your jobs from this dialog.
5.To view logs that are Running or Done, from the Job List toolbar, choose File > Refresh.
1.From the Manage Queue dialog, select the job that you want to delete from the Distributed Migration Job list. The row selector icon and the highlighted row indicates the selected row.
NOTE: Only jobs with a status of Queued or Done can be deleted. Deleting a job from the queue will not remove or delete any of the logging information that has already been sent to the main Job list for the Agent Database.
2.Click Delete Job.
(If the button is disabled, check that the selected job has a status that is either Queued or Done.)
A dialog will display asking you to confirm the deletion.
Many migration actions can be performed as a separate action after the initial migration is performed.
The following objects and settings can only be copied as a separate, post-migration task:
The following objects and settings can be copied both as part of a full migration or as a separate action: