Chat now with support
Chat with Support

Metalogix Content Matrix 8.8 - File Share Edition User Guide

Introduction Entering the License Key Overview of Content Migration Content Matrix Console End User Interface Enabling Advanced Mode Enabling and Disabling Optimistic Mode Connecting to a File System Connecting to SharePoint Preparing for Your Migration Initiating a Migration Configuring Copying Options Saving or Running a Migration Action Log Files Using PowerShell with Content Matrix
Configuring PowerShell for Use with Content Matrix Content Matrix PowerShell Commandlet List
Modifying Content Matrix Configuration and Settings Frequently Asked Questions About Us

Configuring Content Matrix for Distributed Migration

Metalogix Content Matrix can significantly improve the time it takes to complete migration jobs by using a distributed migration model. This model essentially consists of a Metalogix Content Matrix Console Controller (Host), a central jobs repository or queue, and one or more loosely-coupled Metalogix Content Matrix Console agents.

Distributed Migration Illustration

By automatically selecting the jobs from a central repository, Metalogix Content Matrix Console agents are able to distribute the workload efficiently across the resource pool. The distributed model enables parallel processing of migration jobs that reduces migration time, and enables higher utilization, better workload throughput and higher end-user productivity from deployed resources.

Connection icon

Distributed Migration supports the following SharePoint connection adapters:

·Metalogix Extensions Web Service (MEWS)

·SharePoint Client Side Object Model (CSOM)

·CSOM using the Azure Pipeline

Distributed Migration Components

Distributed Migration is typically used for large migration projects and relies on the following three  components:

Controller (or Host)

This is the primary Metalogix Content Matrix Console that manages agents, the Distributed database and the migration jobs.

Distributed Database

A SQL Server database that contains the repository or queue of migration job definitions which the agents can execute.

NOTE:  The Distributed database cannot be a SQL CE database.


This is a physical or virtual machine that is remote from the Controller machine. It is connected to through the Controller to run jobs remotely. Once connected, the Controller will push an installation of the Metalogix Content Matrix Console onto the Agent machine, which is then configured to execute the migration jobs that are sent from the Controller. Any logging information would then be sent to the Distributed Database. When an agent is executing a migration job, any interaction with the agent such as changing a configuration setting is not recommended.

Distributed Migration System Requirements

Requirements for the Controller (Host) machine

·Metalogix Content Matrix Console must be installed and set-up on the Controller machine. For details on this, please see the Metalogix Content Matrix Console Advanced Installation Guide.  

·The User account that is connecting to and running migrations from the Controller to the Agent machines will require Administrator permissions on both the Controller machine and all of the Agent Machines.

·An X.509 Certificate must be created for the Controller and the same certificate can be installed on all machines in the Distributed Migration model. You do not need to create multiple X.509 certificate files. For more information about creating an X.509 certificate, please see Creating an X.509 Security Certificate for Distributed Migration. For more information about installing an X.509 certificate, please see Installing an X.509 Security Certificate for Remote Agents section.

·The default Metabase settings for Metalogix Content Matrix must be reconfigured to use SQL Server and not a SQL CE database. For more information about configuring the Metabase settings, see Configuring Metabase Settings.

Requirements for the Agent Database

·The Agent Database must use SQL Server 2008 or later.

·The Agent Database can reside on the Controller machine or any other machine in network, provided that the Agents and Controller have access to that machine.

·The Agent database should be created from the Metalogix Content Matrix Console. For more information, see Creating an Agent Database.

NOTE: It is recommended that SQL Server Authentication is used to connect to the Agent Database.

Requirements for an Agent Machine

·An agent machine can be a physical or a virtual machine with 1 GB of free RAM, plus double the size of the largest file being migrated in free RAM.

·The operating system can be Windows 7, 8, 8.1, 10 or Microsoft Windows Server 2008 R2 or later.

·Microsoft .NET Framework 4.6 or higher must be installed on the machine.

·The Agent machine must meet all the prerequisites as specified in the Metalogix Content Matrix Console Advanced Installation Guide.

·It must allow remote connections to itself.

NOTE: It is recommended that the Agent be in the same network as the Controller.

·All instances of Windows PowerShell must be closed.

·An X.509 Security certificate must be created and installed on all machines in the Distributed Migration model. For more information about creating an SSL certificate, please see the Creating an X.509 Security Certificate for Distributed Migration section. For more information about installing an .509 Security certificate, please see the Installing an X.509 Certificate for Remote Agents section.

·The following services must be started:

§Remote Registry

§Server Service

§Workstation Service

Also note that when connecting to an Agent machine the Controller will try to install a copy of Metalogix Content Matrix Console on that Agent. In order to do this Metalogix Content Matrix (on the Controller machine) will look at the following folder location (local to itself) "C:\ProgramData\Metalogix" to see if a copy of the install file is present. It will look for the installer file using the naming convention: Metalogix_Content_Matrix_Console_Setup_8_1_0001.exe. If the file is found, then the installer will be copied to the Agent and deployed. If the file is NOT found, then Metalogix Content Matrix will try to copy the installer from the Metalogix website, rename the download when it completes, then copy that file to the Agent.

Using the Wizard to Set Up Distributed Migration

When using the Distributed Migration feature, a "Controller" machine can be configured to distribute migration jobs to Agent machines in a hub-and-spoke model to help run migration jobs in parallel, to help maximize overall performance. There is a Metalogix Content Matrix Distributed Migration Wizard that is designed to help streamline and configure the setup for both the Controller and Agent machines.

Alternatively, you can set up Distributed Migration manually.

Before setting up Distributed Migration:

Make sure your Controller (Host) machine, Agent Database, and Agent machines meet Distributed Migration Component Requirements.

To use the Distributed Migration Wizard:

1.In the Metalogix Content Matrix ribbon Connection tab, click Configure Distributed Migration.

FS Distributed Migration

The Wizard begins the configuration process with a Getting Started section. Review the information presented on this screen before proceeding to the next step.

Distributed Migration SP_FS Start

NOTE:  Agent machines use a SQL database to share information with each other. This database must reside in a location that all Agent machines, as well as the Controller, are able to access. Please see Agent Databases for Distributed Migration for more details.

2.If you are configuring Distribute migration for the first time, read and accept the terms of the third-party License Agreement, then click [Next>].

3.To Provision Agent Database, either:

§Enter the address of the SQL server where the database is located


§Use the [Browse] button by the SQL Server field to browse for servers on the local system and on the network, then click [OK] to return to the Provision Agent Database dialog.

SQL Server BrowserCONTEN~1_img193

4.Enter the name of an existing SQL database in the SQL Database field, or click [Browse] to view the databases located on the chosen SQL server. To create a new database, select [New Database] in the Browse window, and enter a name for it.

Provision Distribution DB CREATE

5.If specific authentication credentials are required in order to log in to the SQL server, enter them in the appropriate fields. It is recommended that SQL Server Authentication is used to connect to the Distributed database.

6.Click [Next], and to Configure Metabase choose a SQL server and database to use for the Metabase database (which is used by Metalogix Content Matrix to store metadata during the migration process) just as you chose a server and Distributed database in the previous steps.

Distributed Migration SP_FS Metabase

7.If specific authentication credentials are required in order to log in to the SQL server, enter them in the appropriate fields. Then click [Next].

The Wizard will now enable you to copy application, environment, and user mapping settings files from the Controller machine to the Distributed database to be used in place of the default settings on the Agent machines. Please see the Updating an Agent topic for more details.

Distributed Migration SP_FS Mappings

8.Select Copy Settings to copy UserSettings.xml, EnvironmentSettings.xml, and ApplicationSettings.xml from the local system to the Agent database.

A confirmation displays after the settings have been successfully copied.

NOTE:  After these settings have been copied to the Agent database and the console has been restarted, Metalogix Content Matrix will no longer look in local settings files for configuration information. This means that changing local settings files will have no effect on the console's operations.

If changes need to be made to settings after copying them over to the Agent database, make the necessary changes to configuration files on the local system, and then copy those files over to the Agent database using the Wizard.

9.Click [Next].

10.For Create Certificate, select an existing certificate to use, or create a new one via the [Generate New Certificate] button.

Distributed Migration Create Certificate

When creating a new certificate, make sure to use a certificate name that does not contain any spaces. Also use a robust password that you will remember, and export the certificate to a folder where it can be found again in the future.


NOTE:  Metalogix Content Matrix utilizes security certificates in distributed migrations to maintain secure communication between the Controller and Agent machines. This certificate will automatically be used for the Controller machine where the Wizard is currently running from, whether or not it was generated now or at a previous time.  Please see Installing an X.509 Certificate for Use with Remote Agents for more details.  

11.Click [Next>].

12.For Download Installer, click [Download Installer] to download a new copy of the installer to that system.

Please see Distributed Migration System Requirements for more details.

Distributed Migration SP_FS Download Installer

An indicator will appear at the bottom of the Wizard indicating that the download is in progress. Click [Next >] when the button becomes available after the download operation has completed.

13.Enter the name of the Agent computer in the Agent Name field to find it by name, or select [Browse...] to browse for it in the network. The IP address of the system can also be used to locate and connect to it.

REMINDER:  It is recommended that the Agent should be on the same network as the Controller.

Distributed Migration SP_FS Configure Agent

NOTE:  Make sure to enter the correct user name and password for the system before proceeding.

14.Click [Next ].

Distributed Migration SP_FS Prerequisites

NOTE:  If the Wizard finds that any of the services are not running, click [Enable Missing Services] to have the Wizard attempt to enable those services remotely.

Windows Server 2008 R2 or later is the recommended minimum Operating System to be used for Agent machines in Distributed Migration. If the Agent does not meet this requirement, the Wizard will throw a warning message, but it will allow you to proceed so long as the above services are available.

15.When all services are enabled and you are ready to proceed, click [Next >].

16.For Deploy Certificate, click [Deploy Certificate] to deploy the certificate configured above to the Agent system.

Distributed Migration SP_FS Deploy Certificate

A confirmation message displays, confirming successful deployment.

Click [Next>].

17.For Install Agent, select [Deploy Metalogix Content Matrix] to begin the deployment procedure. An indicator displays at the bottom of the Wizard indicating that the deployment is in progress.

Distributed Migration SP_FS Install Agent

The Summary windows shows the configuration options that have been selected for deployment, and the status of the deployment to the specified Agent(s).

Distributed Migration SP_FS Summary

18.To add additional Agents to the distributed migration, click [Deploy New]. The Wizard will then return to the Configure Agents screen (shown above) where the last step can be repeated for the additional Agent.

19.Click [Finish] at the bottom of the Summary screen to close the Distributed Migration Wizard.

20.Close the console and start it up again to make use of the new settings.

Related Documents