Component |
Requirement |
---|---|
Operating System |
Any of the following Microsoft-supported versions: ·Windows Server 2022 ·Windows Server 2019 ·Windows Server 2016 ·Windows 11 ·Windows 10 NOTE: While it is possible to run Content Matrix on an earlier version of the operating system, support cannot be guaranteed. |
Database |
Any of the following Microsoft-supported versions: ·SQL Server 2022 ·SQL Server 2019 ·SQL Server 2016 ·SQL Server 2014 ·SQL Server 2012 ·A SQL Server hosted in Azure ·Azure SQL databases NOTES: §While it is possible to run Content Matrix on an earlier version of SQL Server, support cannot be guaranteed. §The use of SQL CE in a production environment is discouraged because of the following limitations: ·It uses a single .lst file that is less robust and reliable and may be corrupted after the database reaches 4 GB. ·Data compression is not supported. ·Support for large objects is limited. ·Microsoft support for SQL CE has ended. If you still want to use SQL CE, then SQL Server Compact 4.0 must be installed on the machine. You can download a copy from Microsoft. |
Windows PowerShell |
Content Matrix Console has the ability to run migrations using a pre-configured PowerShell console, provided that PowerShell Version 3.0 or later is installed prior to Content Matrix. |
.NET Framework |
Microsoft .NET Framework 4.7.2 (for each machine on which the Content Matrix Console is installed) NOTE: Content Matrix cannot make a local Object Model (OM) connection on a SharePoint 2007 or 2010 environment, because SharePoint 2007 and 2010 require an earlier version of the .NET Framework (v.3.5), which prohibits Content Matrix from completing the connection. Because of this, any migration jobs configured to connect to SharePoint 2007 and 2010 environments using a Local OM connection type will cease to work, and these jobs will need to be recreated for use over a different adapter type such as MEWS or DB. |
The below requirements are the standard set of requirements if you are installing Content Matrix on a non-SharePoint machine (i.e. installing on a machine that is not running SharePoint, but has access to the source and target environments).
If you are installing the Content Matrix client application directly on a target SharePoint Server or Web Front End (WFE), then you would need the same permissions that are required for installing the Metalogix Extensions Web Service (MEWS).
Component |
Requirement |
---|---|
Installing User |
The user account installing on a SharePoint server, will require Local Administrator permissions on the local machine. NOTE: The user account that is installing on a client machine only needs permissions to install a client application. Content Matrix Installer will attempt to elevate permissions as part of the installation process. |
Application Pool Accounts |
If connecting to a remote, on premises instance of SharePoint the Metalogix Extensions Web Service can be used (for SharePoint 2007 or later). This is a SharePoint solution file that is installed and will use the Application pool user account. See the Installing and Configuring the Content Matrix SharePoint WSPs section of this document for more details and permission specifications. |
Connecting/Migrating Users |
Permissions for connecting to SharePoint and migrating content vary, depending on the type of connection being made and the content being migrated. See User Account Access Requirements for details. |
The following URLs need to unblocked by your firewall for Content Matrix to connect/perform migrations.
Purpose |
URL |
---|---|
Connection to Quest license server |
|
Migrating to SharePoint Online |
·https://login.microsoftonline.com When migrating using the Import Pipeline, the following URLs must also be unblocked for diagnostic and logging purposes: NOTE: When migrating using the Import Pipeline, the Azure endpoint URL depends on the provided Azure storage connection string. Refer to the following Microsoft article for more information: https://docs.microsoft.com/en-gb/office365/enterprise/URLs-and-ip-address-ranges?redirectSourcePath=%252farticle%252foffice-365-URLs-and-ip-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2 |
Migrating Nintex Forms and/or workflows to SharePoint Online |
·https://discovery.nintexO365.com (Forms and workflows) ·https://nintex.onmetalogix.com (workflows only) |
The following ports need to be open for Content Matrix to connect/perform migrations.
Purpose |
Port(s) |
---|---|
Connection to SQL Server |
1433 NOTE: By default, Microsoft Windows enables the Windows Firewall, which closes port 1433 to prevent Internet computers from connecting to a default instance of SQL Server on your computer. Connections to the default instance using TCP/IP are not possible unless you reopen port 1433. |
Connection to SharePoint on premises Web applications |
The port for each Web application to which you want to connect. These can be found on the Central Administration > Application Management > Manage Web Applications page. |
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center