Chatta subito con l'assistenza
Chat con il supporto

Metalogix Content Matrix 9.4 - SharePoint Edition User Guide

Introduction Activating the License Key Selecting the SQL Database You Want to Connect to Content Matrix Console End User Interface Enabling Advanced Mode Connecting and Migrating Account Requirements Multilingual Support Connecting to SharePoint Preparing for a Migration How Content Matrix Handles Various SharePoint Components
How Team Sites are Migrated to Modern Team Sites How SharePoint Sites are Migrated to Modern Communication Sites How MySites are Migrated How "Share With" Metadata is Migrated to SharePoint Online Using the Import Pipeline How Records Centers are Migrated to SharePoint Online Using the Import Pipeline How Master Pages are Migrated How List Template Galleries Are Migrated How Content Types are Migrated Document Version and Checked Out File Limitations How Ghosted and Un-Ghosted Pages are Migrated How Document Sets are Migrated How Navigation is Migrated How Classic Web Parts are Migrated How Site Themes are Preserved How Site Features Are Migrated How Managed Metadata is Migrated How Users and Permissions are Migrated How BCS/BDC Data is Migrated How OneNote Notebooks are Migrated How Customized Form Pages are Migrated How InfoPath Forms are Migrated How SharePoint Workflows are Migrated How Nintex Workflows and Forms are Migrated How Metalogix StoragePoint Content is Migrated How Link Correction Works
Initiating a Migration Configuring Copying Options Saving or Running a Migration Job Copying SharePoint Objects as a Separate Action Converting Classic Pages to Modern Pages After a Migration Configuring Hub Sites Incremental Migration Using PowerShell with Content Matrix
Adding PowerShell Snap-Ins for the Application Framework Content Matrix PowerShell Commandlet List
Metalogix.System.Commands Metalogix.SharePoint.Commands Metalogix.Jobs.Reporting.Commands Metalogix.SharePoint.Migration.Commands
Modifying Content Matrix Configuration and Settings Configuring Content Matrix for Distributed Migration Frequently Asked Questions About Us

Distributed Migration System Requirements

Navigation:  Configuring Content Matrix for Distributed Migration >

Distributed Migration System Requirements

Requirements for the Distributed Database

·The Distributed Database must use a Microsoft-supported SQL server.

·The Distributed Database can reside on any machine in network, provided that all agents have access to that machine.

·The Distributed Database should be created from the Metalogix Content Matrix Console.

NOTE: It is recommended that SQL Server Authentication be used to connect to the Distributed Database, as it will allow for cross-domain connections.

Requirements for an Agent Machine

·An agent machine or workstation should have 16 GB of free RAM.

NOTE:  An agent machine can be a physical or virtual machine.

·Microsoft .NET Framework 4.7.2 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.

·The machine must allow remote connections to itself.

·All instances of Windows PowerShell must be closed.

·The following services must be started:

§Remote Registry

§Server Service


Connection icon

· If a migration job is using SP 2013 or later DB as a source connection, then users can only run jobs remotely on an agent that meets the connection requirements for the same DB version as the machine from which the migration is configured. This means that the agent machines must either:

§Have the same version of SharePoint installed on or be a SharePoint WFE for a comptible version.


§Be a 64-bit machine that has no version of SharePoint installed on it.

·Local Object Model (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.  For making remote Object Model connections, make sure the Metalogix Extension Web Service (MEWS) is installed on each agent machine.  

Configuring Agents for Distributed Migration

Navigation:  Configuring Content Matrix for Distributed Migration >

Configuring Agents for Distributed Migration

Configuring an Agent for Distributed Migration consists of the following high-level tasks:

I.Install the latest version of Content Matrix then create and/or connect to the Distributed Database.

II.Copy the Agent Service installation files to the agent machine and install from a Command Prompt.

III.For the first agent, generate a unique security certificate for the Metalogix Agent Service.

NOTE:  Once created on the first agent, the name of the certificate is stored in the Distributed Database and then it can be copied to other agents.  (The same certificate needs to be used across all agents.)

IV.Install the Metalogix Agent Service, which

·installs the Agent Service as a Windows service

·installs the certificate to “My User Account” storage

·saves the certificate name to the Distributed Database

V.Start the Metalogix Agent Service.

Permission Requirements

The account used to configure agents for Distributed Migration must:

·be an Administrator


·have permissions to Log on as a Service (via Administrative Tools > Local Security Policy > User Rights Assignment).

To install the latest version of Content Matrix then connect to the Distributed Database:

1.Log into the machine using an account that meets Permissions Requirements.

2.Download or copy the latest version of the Content Matrix installation kit to the machine.

3.Install the Content Matrix Console and the Metalogix Extension Web Service (MEWs). (See the Metalogix Advanced Installation Guide for details.)

4.Open the Console and create/connect to the Distributed Database as follows:

a)From the Job List, choose File > Connect to Distributed Database.

                                                                                                                                                                                                                                                                      Distributed Database CONNECT

b)Enter or browse to the SQL Server and SQL Database you want to use.  If the database does not already exist, create it.

NOTE: Remember to use the same Distributed Database for all agents in the "cluster."

Browse to Database

Whenever a machine connects to the Distributed Database, a pop-up will display with the option of copying User Mappings and other local machine settings to the database.

CAUTION:  If you are configuring multiple agents, remember that if you click [Yes], any User Mappings and settings that already exist in the Distributed Database will be overwritten.

Distributed Migration User Mappngs prompt

If you want to use an encrypted connection to the database, check the Encrypt Connection box

NOTE: If the certificate used for encryption is not trusted, you will also need to check the Trust Server Certificate box.

5.Close the Content Matrix Console.

To copy the Agent Service installation files to the agent machine:

1.Copy the ContentMatrixAgentService_[version].zip file from the Content Matrix download folder and extract the files (the recommended location is C:\Program Files (x86)\Metalogix\Agent Service).

2.Open a Command Prompt using the Run as Administrator option.

3.Change the directory to point to the location containing the Agent Service files.

Command Prompt Agent Service

To generate a self-signed certificate for agents:

NOTE: Create the certificate for the first agent only, then copy that certificate to additional agent machines.  Make sure that the folder into which you are generating the certificate already exists.

At the command prompt, use following command to generate a certificate:

Metalogix.Agent.exe --generateCertificate <certificateName> --certificatePassword <certificatePassword> --path <certificatePath>



Metalogix.Agent.exe --generateCertificate ContentMatrixAgentCertificate --certificatePassword certPass --path "C:\Content Matrix Certificates"



·When generating a certificate, there is no need to enter the file extension as it will be ignored.

·It is necessary to use double quotation marks (" ") to enclose:

§a password that contains special characters

§a file path that contains spaces (as shown in the example above).

To install the Metalogix Agent Service:

NOTE:  If you have already created a self-signed certificate on the first agent, make sure it is copied to the other agent(s) before performing this procedure .

At the command prompt, use following command:

Metalogix.Agent.exe -i --user <domain\username> --password <password> --certificatePath <certificatePath>\<certificateName.FileExtension> --certificatePassword <certificatePassword>



Metalogix.Agent.exe -i --user metalogix\Administrator --password userPass# --CertificatePath "C:\Content Matrix Certificates\ContentMatrixAgentCertificate.pfx" --certificatePassword certPass


NOTE:  It is necessary to use double quotation marks (" ") to enclose:

·a password that contains special characters

·a file path that contains spaces (as shown in the example above).

To Start the Metalogix Agent Service:

1.Navigate to Administrative Tools > Services > Metalogix Agent Service.

2.Right-click and choose Start.

Managing Agents

Navigation:  Configuring Content Matrix for Distributed Migration >

Managing Agents

From any agent machine, you view, refresh and disable/enable jobs.

NOTE:  All agents connecting to the same Distributed Database must have the same version of Content Matrix installed.

To open the Manage Agents dialog:

From the Metalogix Content Matrix Console ribbon, choose Connection > Manage Agents.

NOTE:  If the machine is not connected to a configured Distributed Database, Manage options will be disabled.

Manage Agents Dialog

The Manage Agents dialog presents a toolbar with the following options:

·View Agent - Displays more information about a selected agent such as log history, and other pertinent information.

Agent Details

·Refresh - Displays the most recent status of a selected agent.

·Enable/Disable Job  - Allows/prevents the agent from pulling migration jobs from the Distributed Database.

NOTE:  If you want to uninstall the agent completely, use the procedure for Uninstalling a Distributed Migration Agent.

·Agent Support Zip - Generates a zip file containing logs that can be sent to Quest Support for troubleshooting.

Generating an Agent Support Zip File

Navigation:  Configuring Content Matrix for Distributed Migration >

Generating an Agent Support Zip File

From the Manage Agents dialog, you can generate a zip file to send to Quest Support for troubleshooting purposes.

The contents of the zip file will vary, depending on which agent is selected in the grid.

If the agent selected in the grid is ...

Then ...

the local machine

the zip file will contain two files:

·Distributed Database logs for the agent (AgentServiceDBLogs.txt)


·event log entries for the local agent (AgentServiceEventLogs.txt).

a remote machine

the zip file will contain the Distributed Database logs file for the agent (AgentServiceDBLogs.txt) only.

If you want to provide event logs for a remote agent, you will need to log onto that machine and generate a Support zip file from there.

To generate an Agent Support zip file:

1.Make sure the appropriate agent is selected in the grid.

2.From the Manage Agents toolbar, select Agent Support Zip and save the zip file to the desired location.

Send any zip files you generate to Quest Support.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione