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

License Key Troubleshooting


I have been unable to get Metalogix Content Matrix to recognize my license key. When I copy and paste it into the box, I get a "the specified license key is invalid" error.


Here are some things to check:

·Confirm that the license you are installing is for the correct application versions of Metalogix Content Matrix. Contact Quest to verify that it is.

·When performing an offline key activation, make sure to enter the long key in its entirety, including the "=" symbol at the end of it.

·Verify that you have write privileges to the registry. The installer will fail if the registry is locked. In some cases there may be a group policy that is preventing the user from adding the key in the registry, despite the user having the correct permissions.

·Some versions of Windows will automatically block write access to the registry under the user account, even if that account has write access to the registry. In this case you can go to the application installation folder, right click on the application executable, and choose 'Run as Administrator'. Then re-enter the license key.

Optimal Setup for Best Performance


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


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

Connecting to SharePoint via Proxy, Load Balancing or Alternative Access Mappings


How does Metalogix Content Matrix Console - Blogs and Wikis Edition deal with environments that use proxy's, load balancing and/or Alternate Access Mappings (AAM)?


Metalogix Content Matrix Console - Blogs and Wikis Edition should not run into any issues with these three things. Blogs and Wikis Edition uses an Extensions Web Service that 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 AAM. Since the Metalogix Extensions Web Service acts the same as a SharePoint web service it also gets all of these benefits.

If you can access the regular native web services with all of your network configurations active, you should also be able to reach the Metalogix Extensions Web Service, and migrate your content.

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

CSV Exported Content is not Rendering when the File is Opened


I have exported my content to a CSV file, but when I open it in Microsoft Excel (or similar programs) the column value is incorrect, and the value covers multiple rows. What are the potential causes of this issue?


This issue is not actually caused by Metalogix Content Matrix Console. What is happening is that the value in one of the columns is actually exceeding the character length of the cell in Microsoft Excel.

In most cases, some of the page content is placed in a column and is then included in the CSV Export. Microsoft Excel has a maximum character limit of 32,767. If the exported column value is longer than the 32,767 character limit, the file will be incorrectly read, and Excel will run into issues when trying to open the CSV file. For more information on this character limit, refer to Microsoft Office documentation.

It is recommended that if users are exporting to CSV and think that one of the column values may exceed the 32,767 character limit, then that cell value should be broken down into multiple column values (the number of columns would depend on the column value's character length). The CSV file should then open correctly after being exported, and user should be able to work with the content before migration.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating