Chat now with support
Chat with Support

Metalogix Content Matrix 8.9 - Blogs and Wikis Edition User Guide

Introduction Entering the License Key Content Matrix Console End User Interface Source Blog and Wiki Structure Connecting to a Source Blog or Wiki Connecting to SharePoint Preparing for Your Migration Initiating a Migration Configuring Copying Options Saving or Running a Migration Action Running Link Correction as a Post-Migration Task Log Files Using PowerShell with Content Matrix
Configuring PowerShell for Use with Content Matrix
Registering Metalogix Command DLL Files Adding PowerShell Snap-Ins for the Application Framework Content Matrix PowerShell Commandlet List
Metalogix.System.Commands Metalogix.SharePoint.Commands Metalogix.Jobs.Reporting.Commands Metalogix.Blog.Commands
Modifying Content Matrix Configuration and Settings Configuring Content Matrix for Distributed Migration Frequently Asked Questions About Us

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.

·Distributed Migration cannot be used with a Blogger connection.

 

·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

Before Submitting a Distributed Migration Job

·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.)

Procedure for Submitting a Distributed Migration Job

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.

Distributed Migration Run Jobs Remotely

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.

Managing the Distributed Migration Job Queue

If Metalogix Content Matrix has been configured for Distributed Migration, the Console that is set up as the Controller (Host), provides a single point of management control over the job queue.

To open the Manage Queue dialog:

From the Metalogix Content Matrix Console ribbon Connection tab, select Manage Queue.

CONTEN~1_img153Distributed Migration Manage Queue

NOTE:  If the Manage Queue button appears disabled, your Metalogix Content Matrix Console edition is not connected to use a configured Agent Database. To configure an agent database, see Creating/Connecting to an Agent Database for Distributed Migration.

The Manage Queue dialog displays a list of migration Jobs, called the Distributed Migration Job list. The information presented in the various columns are as follows:

Column

Description

Job ID

The unique identifier of the job.

Job Name

The name of the job.

Created

The date and time the job was saved (and not when the job was queued).

Source URL

The source of the migration content.

Target URL

The target of the migration content.

Agent Name

The name of the Agent where the job is running. The value is blank when the job is queued.

Status

Recent state of the job. The status values could be one of the following values:

·Queued - the migration job is ready to start.

·Running - a migration is in progress.

·Failed - the job has encountered a fault condition.

·Done - the migration has completed.

You can select a job from the list by clicking anywhere on the row. A row selector icon and the highlighted row indicates the selected row.

Related Documents