Chatta subito con l'assistenza
Chat con il supporto

Metalogix Content Matrix 9.4 - Advanced Installation Guide

Supported Source and Target SharePoint Versions

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

Source Version

(SharePoint Edition)*

Target Version
(All Editions)

SharePoint 2013
(Foundation and Server)

SharePoint 2016

SharePoint 2019

Microsoft Office 365
(SharePoint Online)

Windows SharePoint Services (WSS) 3.0

Green Checkmark

Green Checkmark

Green Checkmark

Green Checkmark

Microsoft Office SharePoint Server (MOSS) 2007

Green Checkmark

Green Checkmark

Green Checkmark

Green Checkmark

SharePoint 2010
(Foundation and Server)

Green Checkmark

Green Checkmark

Green Checkmark

Green Checkmark

SharePoint 2013
(Foundation and Server)

Green Checkmark

Green Checkmark

Green Checkmark

Green Checkmark

SharePoint 2016

 

Green Checkmark

Green Checkmark

Green Checkmark

SharePoint 2019

--

-

Green Checkmark

Green Checkmark

* 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 Metalogix Essentials for Office 365 and On Demand Migration, tools that specialize in Office 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 Metalogix Content Matrix SharePoint Client application must be registered for the tenant. Instructions are available in the Using Office 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 Metalogix 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 Metalogix Content Matrix operations.

 

 

Operation

SharePoint

SQL

Global Admin

Farm/
SharePoint Admin

Site Collection
Admin

Term Store
Admin

db_owner on
SP Databases

Reader on
SP Content Database*

Execute on
SP Content Database*

Connecting to SharePoint

SharePoint 2013, 2016, or 2019 Database Connection

 

 

 

 

 

Green Checkmark

Green Checkmark

SharePoint 2007 or 2010 Database Connection

 

 

 

 

 

Green Checkmark

 

Local Object Model Connection

 

 

Green Checkmark

 

Green Checkmark

 

 

Remote Object Model Connection

 

 

Green Checkmark

 

 

 

 

Client side Object Model Connection
(Site Level)

 

 

Green Checkmark

 

 

 

 

Office 365 Tenant Connection

 

Green Checkmark

Green Checkmark

 

 

 

 

Migration Actions(SharePoint Edition)

Deploying Nintex Apps to SharePoint Online

Green Checkmark

 

 

 

 

 

 

Migrating as a Site Collection

 

Green Checkmark

 

 

 

 

 

Migrating Managed Metadata

 

 

 

Green Checkmark**

 

 

 

* For a SharePoint 2013, 2016, or 2019 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 Metalogix Content Matrix Console client application(s) and the Extensions Web Service.

Special Considerations When Upgrading from Version 8.9 or Earlier

As of version 9.0, Blogs and Wikis and File Share Editions are no longer being offered, and you will not have the option of installing or upgrading them.  If you have either or both of these editions installed on the same server as other editions that you want to upgrade, it is recommended that you uninstall them before upgrading to version 9.0.  If you want to continue using an older version of these editions, you may re-install the older version of the Consoles on a different server.

NOTE:  Because all Content Matrix editions share several PowerShell scripts, you will no longer be able to perform migrations using PowerShell for Blogs and Wikis and File Share Editions if an upgrade to version 9.0 has been performed.

Additionally, Intelligent Migration will not work with Content Matrix version 9.0 or later. Therefore, if Intelligent Migration is currently installed, it is recommended that you uninstall it.  

Basic Installation Scenarios for Content Matrix Console

One of the more powerful aspects of Metalogix Content Matrix Console is its flexibility for installation scenarios. Each Edition of Metalogix 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 Metalogix 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 Metalogix 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 Metalogix 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 Metalogix 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 Metalogix 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 Metalogix 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 Metalogix 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 Connection – This connection is available for SharePoint 2013 or later environments. While it connects through the SharePoint Client Side Object Model (CSOM), it does not have the same level of fidelity that the Local OM or Remote OM connections have. This connection type is mainly used when connecting to O365 environments, or when remotely connecting to a SharePoint server/WFE that does not have the Extensions Web Service installed.

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

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione