Content Matrix 9.9 - Advanced Installation Guide

Supported Source and Target SharePoint Versions

Content Matrix Console supports the following versions of SharePoint.

NOTE:  With Content Matrix SharePoint Edition, you can migrate into a target version of SharePoint that is the same or later than the version of SharePoint on the source.  (Migration from a later version of SharePoint to an earlier version is supported for documents and list items only.)

* While it may be possible to migrate from earlier versions of SharePoint (e.g., SharePoint 2003), some long out-of-date functionality may present special challenges when migrating to a supported target. However, Quest Professional Services can provide assistance.

If you want to migrate from a SharePoint Online source to a SharePoint Online target:

Quest offers On Demand Migration, which specializes in Microsoft 365 and SharePoint Online migrations.  

Connecting and Migrating Account Requirements

OAuth Authentication Permissions

The first time that OAuth Authentication is selected when connecting to SharePoint Online, the Content Matrix SharePoint Client application must be registered for the tenant. Instructions are available in the Using Microsoft 365 OAuth Authentication section of the user documentation.

It is recommended that an account with the Global Administrator role be used to register the application, because a Global Administrator can provide consent on behalf of the entire organization.

In the event that a Global Administrator does not register the application, users with the Application Administrator role can register the application for their own account only.

IMPORTANT:  For an Application Administrator, the Content Matrix SharePoint Client application records current SharePoint permissions as part of the registration process.  Therefore, a user who registers as an Application Administrator must already have the appropriate permissions to connect and perform migrations using OAuth authentication.  For example, at the time of registration, a user who is going to make tenant-level connections must also be a SharePoint Administrator if they want the app to allow them to access to all site collections within the tenant and to be able to Paste as a Site Collection. Similarly, a user who will be migrating Managed Metadata must also be a Term Store Administrator at the time of registration.

Connecting and Migrating Account Permissions

The following table provides an overview of the minimum account permissions required to connect to SharePoint and perform various Content Matrix operations.

* For a SharePoint 2013, 2016, or 2019/Subscription Edition database connection, the combination of Reader and Execute is is the minimum set of permissions required, but the combination of db_dataReader and SPDataAccess can also be used.

** For a source farm, read permissions to the term store may be sufficient (depending on your environment), but it is recommended that Term Store Administrator permissions be set.

Installation

This section describes various installation scenarios, as well as how to install the Content Matrix Console client application(s) and the Extensions Web Service.

Basic Installation Scenarios for Content Matrix Console

One of the more powerful aspects of Content Matrix Console is its flexibility for installation scenarios. Each Edition of Content Matrix Console has multiple scenarios that can be utilized to help with system installation limitations and optimization for performance.

There are three basic scenarios that can be applied when installing Content Matrix Console:

1.Installing the console directly on the Source system. This scenario is most likely with SharePoint Edition since the ECM (Electronic Content Management) Editions are sufficiently different enough from SharePoint that installing the console on these systems provide any real benefit for migration performance.

2.Installing the console directly on the Target system. In most cases this can be the most beneficial since it will help reduce the network traffic when communicating with the target SharePoint environment during a migration, which helps improve migration performance. Another benefit of this scenario is that it provides the client application with direct access to the local SharePoint Object Model (OM), giving Content Matrix greater fidelity when migrating content. This scenario is not possible when migrating to a target SharePoint Cloud environment.

Many companies have internal policies in place that restrict or limit the installation of any software directly on the server, usually due to general security and/or software quality concerns. Depending on the policy, this could mean that all software must go through an approval/testing phase before it is allowed to be installed on the server. The testing/approval process can take anywhere from a few days to a few months depending on the organization. This can be a hindrance if any short timelines are involved with a migration. These strict limitations could also completely prevent any third party software from being installed on a server directly.

3.Installing the console on a third machine that has access to both the Source and Target systems. This is the most common use case for most customers. This scenario allows users to install, run, and even upgrade their version of Content Matrix without needing to access the source or target environments. And with the use of the Metalogix Extensions Web Service (installed on the target SharePoint environment) users can install the client on their own machine and still have remote access to the SharePoint Object Model for any on premises installations, providing the same level of fidelity that the local OM connection would give if Content Matrix was installed locally on the target SharePoint server or a Web Front End (WFE).

Connections to other source environments are all roughly similar and only have one method for direct connection. However, there are multiple connection types for SharePoint. These connection types consist of:

·SharePoint Database Connection – This is a read-only connection directly to a SharePoint Database (DB). This connection type is only used in SharePoint Edition for connection to a SharePoint on premises source environment, and is valid for any version.

·SharePoint Local Object Model Connection – This connection can only be made when Content Matrix is installed directly on the target SharePoint server or WFE. It accesses the SharePoint OM locally on the machine, which allows it to preserve more existing metadata and grant deeper access for some Content Matrix features.

·SharePoint Remote Object Model Connection – This connection requires the installation of the Metalogix Extensions Web Service on the target SharePoint environment. The Extensions Web Service allows Content Matrix to have a remote connection to the SharePoint OM. This grants all of the same access for features and metadata that is available from the Local OM connection (see above). This connection type is available for on premises installation.

·SharePoint Client Side Object Model (CSOM) Connection – This connection is used when connecting to Microsoft 365 environments.

Please see the Connecting to SharePoint section of the appropriate edition of the user documentation for complete details.