Chat now with support
Chat with Support

Metalogix Content Matrix 8.9 - eRoom Edition User Guide

Introduction Entering the License Key Content Matrix Console End User Interface Connecting to eRoom Connecting to SharePoint Preparing for Your Migration Initiating a Migration Configuring Copying Options Saving or Running a Migration Action Mapping Links and Running Link Correction Incremental Migration Log Files Using PowerShell with Content Matrix
Configuring PowerShell for Use with Content Matrix
Registering the Metalogix Command DLL Files Adding the PowerShell Snap-Ins for the Application Framework Content Matrix PowerShell Commandlet List
Metalogix.System.Commands Metalogix.SharePoint.Commands Metalogix.Jobs.Reporting.Commands Metalogix.ERoom.Commands
Using Powershell for Nested Content Reports and Pre-Migration Check
Modifying Content Matrix Configuration and Settings Configuring Content Matrix for Distributed Migration Frequently Asked Questions About Us

Scheduling a Migration Job via the Content Matrix UI

If you chose the Schedule Task option (that is, to schedule a migration job via the UI), once PowerShell script has been saved the Create Task Wizard dialog opens, allowing you to start configuring the scheduling for the migration task.

1.Complete the Create Task Wizard as follows:

a)Enter a desired name for the scheduled task in the Task Name field.

The Description section displays some additional details about migration action, such as the source and target locations.

CONTEN~1_img141

Click [Next].

Set the Trigger for the scheduled task. Use the information in the following table for guidance.

CONTEN~1_img142

If you want the scheduled job to run …

Select …

at the same time every day

Daily.

whenever a specific system event is logged

When a specific event is logged.

on specified days during specified months

Monthly.

one time only at a specific date/time

One Time.

on one or more specified days on the week

Weekly.

2.Click [Next].

3.Use the information in the following table to determine the appropriate action to take.

If you selected …

Then …

Daily

·Select a Start date and time, and

·For Recur every….days, select the interval at which you want the job to run.

CONTEN~1_img143

When a specific event is logged

·Select the Log from which you want Metalogix Content Matrix to search for the event.

·Select the Source program, application, or service from which the Logs are filed.

·Enter the specific Event ID used trigger the scheduled task.

CONTEN~1_img144

Monthly

 

·Select a Start date and time.

·From the Months drop-down, use the checkboxes to select/deselect the months during which you want the scheduled task to run.

CONTEN~1_img145

·Select the appropriate option:

§If you want the scheduled task to run on specific calendar days, select the Days radio button, and from the drop-down use the checkboxes to select/deselect the days when you want the scheduled task to run.

CONTEN~1_img146

§If you want the scheduled task to run on specific days of the week, select the On radio button, and from the drop-downs select the frequency and week day(s).

 

For example, if first, third and last are selected in the first drop down menu, and Monday and Thursday are selected in the second drop down menu. the scheduled task will be run on the first, third, and last Monday of the month, as well as the first, third, and last Thursday of the month.

CONTEN~1_img147

One Time

Select a Start date and time.

CONTEN~1_img148

Weekly

·Select a Start date and time.

·For Recur every n weeks on:

§Specify how often the scheduled task should occur.

For example, if the value is set to 5 then the scheduled task will run on every fifth week. If the value is set to 2 then the task will be run every other (every second) week.

§Check each day of the week on which you want the task to run.

For example, if the Recur every value is set to "3" and the day is set to "Wednesday", then on every third week the scheduled task will be run on Wednesday at the entered value for the start time. If the recur value is set to "1" and both "Wednesday" and "Sunday" have been selected, then the scheduled task will be run on Sunday and Wednesday of every week.

CONTEN~1_img149

 

A Summary of the scheduled task displays. If the summary looks correct, click the Finish button to complete the scheduling of the migration task. The task will now be added in the Windows Task Scheduler under a Metalogix folder.  (You may need to Refresh the Windows Task Scheduler dialog before the scheduled tasks will be displayed.)

Viewing the scheduled task, making any modifications or deleting the task itself must be done from within the Windows Task Scheduler, which can be accessed via the Metalogix Content Matrix Console’s Jobs List section Scheduled Task >

CONTEN~1_img150

After a scheduled task has been run, a new entry for the migration will be added into the  Job List section.

Scheduling a Migration Job via the Windows Task Scheduler

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.

Submitting a Distributed Migration Job

If the Metalogix Content Matrix Console is configured as the Controller (Host) for Distributed Migration, you can submit a Distributed Migration job.

Distributed Migration Job Limitations

Connection icon

·

·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

Related Documents