Chat now with support
Chat with Support

Metalogix Content Matrix 9.2 - SharePoint Edition User Guide

Introduction Entering the License Key Metalogix Content Matrix Console End User Interface Enabling Advanced Mode Connecting to SharePoint Migrating to SharePoint Online Using the Import Pipeline Preparing for a Migration How Content Matrix Handles Various SharePoint Components
How Team Sites are Migrated to SharePoint Online and SharePoint 2019 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 Records Centers are Migrated to SharePoint Online Using the Import Pipeline How Document Sets are Migrated How Navigation is Migrated How MySites are Migrated How Managed Metadata, Terms, and Term Stores are Migrated How "Share With" Metadata is Migrated to SharePoint Online Using the Import Pipeline How Web Parts are Migrated How Site Themes are Preserved How Site Features Are 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 Link Correction Works
Initiating a Migration Configuring Copying Options Saving or Running a Migration Job Copying SharePoint Objects as a Separate Action Incremental Migration 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.SharePoint.Migration.Commands
Modifying Content Matrix Configuration and Settings Configuring Content Matrix for Distributed Migration Frequently Asked Questions About Us

Optimal Setup for Best Performance

Question

What is the optimal setup for best performance for Metalogix Content Matrix?

Answer

The optimal setup for performance with Metalogix Content Matrix is to have the application itself installed on the target server, and the Metalogix Extensions Web Service (MEWS) installed on the source server. Then use a SharePoint Database (DB) connection to connect to the source. The Metalogix Extensions Web Service would not need to be installed on the target since the application itself would be installed, allowing for a direct connection to the SharePoint Object Model (OM).

There are a few trade-offs for using the DB connection for the source. In these cases you will be limited with: no write access, no server level connections or actions, and the potential to run into issues when dealing with custom site templates. If these are trade-offs that you are not willing to deal with then it is recommended to connect to the source using a Metalogix Extensions Web Service connection.

The main issue that can cause slowdown with the Metalogix Content Matrix Console is copying file structure. If the content that is being migrated contains a large file structure the migration will go slower because Metalogix Content Matrix will try to recreate this structure.

For example, if we have two sites that contain the same amount of data, Site A and Site B, and Site A uses a more complex file structure than Site B, the migration of Site A will run slower then the migration of Site B. Even though these sites contain the same amount of data Metalogix Content Matrix will require more time to recreate the complicated structure of Site A, resulting in Site B finishing it's migration first.

Using Proxies, Load Balancing or Alternate Access Mappings

Question

How does Metalogix Content Matrix deal with environments that use proxies, load balancing and/or alternate access mappings (AAM)?

Answer

Metalogix Content Matrix Console should not run into any issues with these three things. Metalogix Content Matrix uses the Metalogix Extensions Web Service (MEWS), which deploys over a whole farm and functions identically to a regular SharePoint web service. SharePoint web service's get the benefits of IIS redirection, proxy pushing, and anything else that SharePoint can utilize, such as Alternate Access Mappings (AAM). Since the Metalogix Extensions Web Service acts the same as a SharePoint web service it also gets all of these benefits.

In the case for load balanced environments the Metalogix Extensions Web Service would need to be deployed through the target side SharePoint farm. When the Web Service is installed it automatically gets deployed to all the SharePoint instances within that farm, as a SharePoint solution. Once the Web Service is installed on the target server, then load balancing should no longer be an issue.

There are, however, some cases where proxy settings may not work correctly by default. In these cases it is possible to set some specific proxy settings for the specified connection. Please see the Configuring Proxy Settings page for more details, or the Manually Configuring Proxy Settings page if the proxy settings need to be manually configured.

Troubleshooting the Extensions Web Service

Question

I am having trouble installing the Metalogix Extensions Web Service. Are there any steps I can take to troubleshoot?

Answer

Yes, there are some steps you can take to troubleshoot installation issues for the Metalogix Extensions Web Service.

The first thing that you want to check is that the account that is being used to install the Metalogix Extensions Web Service has all the necessary permissions. This user account needs to be able to run the STSADM commands on the installing system, and also needs the following permissions:

·SharePoint Site Collection Administrator

·Farm Administrator

·Read/Write access to the Content Database (DB)

·Administrator on the installing system

In some cases users can receive a message saying "Could not deploy SharePoint solution: Cannot open SPAdminV4 service on computer." when they try to install the Metalogix Extensions Web Service. There are two possible methods for working around this issue.

1.Navigate to the folder containing the Metalogix Extensions Web Service installation EXE file. Right-click on this file and choose Run as Administrator. The Web Service should now be able to install. Some instances of Windows will automatically block services from being registered fully. In these cases, running as administrator should get around this issue.

2.In some cases, users are not able to use the Run as Administrator command, or this does not solve the issue, then there is a second workaround method that can be used. The alternate solution is to turn off the User Access Control (UAC) and reboot the server. This should allow the installing account to correctly install and deploy the Metalogix Extensions Web Service. Once installed and deployed you can re-enable UAC.

After the Web Service has been installed, there is a check that can be made to see if the Web Service can be detected on any given machine. For more information on running this check please see the After Installing the Metalogix Extensions Web Service section of the Installing the Metalogix Extensions Web Service page.

Installing the Extensions Web Service on Specific Systems

Question

I want to have more control over installing the Metalogix Extensions Web Service, and only install it on some systems. Is this possible?

Answer

Yes this is possible, however, the method for this will change slightly depending on the version of the Metalogix Extensions Web Service you are trying to install. The Metalogix Extensions Web Service installation file contains and deploys a WSP solution file throughout a SharePoint farm.

If you are trying to install version 5.1.0.0 or later:

1.Open a Command Prompt window, and set the directory to the same directory that the EXE installer file is located in.

2.Enter the name of the EXE installer file followed by /v and /a. For example, Metalogix Extensions Web Service Setup v.5.1.X.X /v /a (replacing the "X" with the version number). It is important to make sure there is a space between the "/v" and "/a" values.

NOTE: A "/?" value can be entered after the name of the EXE file to see a list of the command line parameters.

3.This will open the InstallShield, but will not actually install the Metalogix SharePoint Extensions Web Service. Instead it will allow you to select a desired extraction location and it will extract the WSP file and the MSI file.

If you are trying to install a version before v.5.1.0.0 you can (extracting from the WSP file):

1.Open a Command Prompt window, and set the directory to the same directory that the EXE installer file is located in.

2.Then enter the command: msiexec /a "Metalogix SharePoint Extensions Web Service - vX.X.XX.XX.msi" (replacing the "X" with the version number).

3.This will open the Install wizard, but will not actually install the Metalogix Extensions Web Service. Instead it will allow you to select a desired extraction location and it will extract the WSP file to that location.

After the files are extracted users can install the files as they choose.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating