If you chose the Generate PowerShell Script option (that is, to configure the migration job directly in the Windows Task Scheduler) and saved the PowerShell script to the location of your choice, follow the steps below.
1.On the system where the scheduled task will run, open the Windows Task Scheduler.
2.Choose Actions > Create Task.
3.Enter a task Name and Description.
4.In the General tab, go to Security options and specify the user account that the task should be run under. Change the settings so the task will run regardless of whether the user is logged in.
5.Select the Triggers tab, and click [New] to add a new trigger for the scheduled task. This new task should use the On a schedule option. The start date can be set to a desired time, and the frequency and duration of the task can be set based on your specific needs. Click [OK] when your desired settings are entered.
6.Select the Actions tab and click [New] to set the action for this task to run. Set the Action to Start a program.
7.In the Program/script box enter "PowerShell."
8.In the Add arguments (optional) box enter the value ".\[Your PowerShell Script Name]." For example, if your PowerShell Script is named "Migration1.ps1" then you would enter ".\Migration1.ps1" as the value.
9.In the Start in (optional) box, add the location of the folder that contains your PowerShell script.
NOTE: The location used in the Start in box will also be used for storing the scheduled task run times, the job history for the copies, and any additional logging that may occur.
10.When all the desired settings are made, click [OK].
11.Next, set any other desired settings in the Conditions and Settings tabs. You can also set up additional actions, such as emailing an Administrator each time the script is run.
12.Once all the desired actions have been made (or added), click [OK].
The task will be immediately set, and is ready to run.
If the Metalogix Content Matrix Console is configured as the Controller (Host) for Distributed Migration, you can submit a Distributed Migration job.
·Local OM connections to SharePoint are not supported when using Remote Agents. - A Local OM connection to SharePoint can only be made when Metalogix Content Matrix is installed on a machine that is running SharePoint (a SharePoint server or WFE). Since this type of connection can be made on the Host machine, but cannot be guaranteed to also be available on an Agent machine, it is not a supported connection adapter for running migrations using remote Agents.
·Connections to SharePoint Online must be made using accounts that do not use Multi-Factor Authentication or "modern" authentication - Because the Distributed Migration model relies heavily on PowerShell to perform migrations without user intervention, Web Browser Authentication cannot be used. Therefore, connections to SharePoint Online must use an account that is not part of a SharePoint Online Multi-Factor Authentication policy and does not use "modern" authentication, because these authentication methods require Web Browser Authentication.
·Transformer scripts will not work using a Remote Agent if the script is used as an attachment (i.e. if the script is stored as a file on the local file system, and added to the migration configuration as an attachment) - When running a migration, uses can go to the 'Transformations' tab in the configuration options and set the migration to use a transformer. If the transformer is added by using the Invoke PowerShell script > Use Script From File option, then the transformer will be added by selecting a script file from the file system and attaching it to the configuration options. Transformer script files that are attached in this manner do not get transferred to the Agent machines, so when the Agent tries to run the migration it will run without the configured transformer script.
·If an action in Metalogix Content Matrix is not supported for generating/running the action over PowerShell, then that action is not supported to run remotely on an Agent machine. - Not all actions in Metalogix Content Matrix are supported when using PowerShell. Since running a migration on a remote Agent relies on PowerShell, some actions are not supported to be run remotely. For example:
§Copy Site > Paste Site Objects > List E-mail Notification
§Copy Site > Paste Site Objects > Managed Metadata Local Site Collection Group
§Copy Site > Paste Site Objects > Managed Metadata Term Store
§Copy Site > Paste Site Objects > Site column
§Copy List > Paste List Objects > Permission
·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
·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.)