When connecting to a SQL database via Content Matrix, you are given the option to connect using TLS/SSL encryption.  

NOTE: Content Matrix can use any version of TLS that is compatible with .NET Framework 4.7.2.  The default version of TLS used by the operating system on the machine from which you are connecting will be used by Content Matrix.    

The encrypted connection can use either:

·a self-signed certificate or a trusted certificate from the third party authority (refer to the Microsoft article https://docs.microsoft.c om/en-us/sql/database-engine/configure-windows/enable-encrypted-connections-to-the-database-engine?view=sql-server-ver15 for instructions on configuring an encrypted connection using a certificate)

OR

·a SQL-generated certificate,  which does not require configuration.

NOTE:  If a trusted certificate is used, it is not necessary to check the Trust Server Certificate box.  However,  if the box is not checked and the certificate is not trusted, the following message will display:

In this case, the Trust Server Certificate box must be checked in order to continue the connection.

In most cases Content Matrix can automatically connect to SharePoint and authenticate license keys, through an environment's proxy setting, However, in some cases the proxy may need to be configured within Content Matrix. In these cases users can specify the proxy settings though the connecting dialog.

There are two basic places where this proxy setting can be configured. The first of these is when activating a license key, and the second when connecting to SharePoint. The  dialogs for these options look slightly different, and the when you are using a proxy to connect to SharePoint, you have the additional option to Import Proxy from Internet Explorer.

To configure proxy settings:

1.In the Proxy server dialog, check the Enable proxy box.

2.Use the information in the following table to determine the appropriate action to take.

3.If you accessed the dialog from the License Activation dialog, click [Set].

Content Matrix provides you with the ability to control what actions are available to the client application through configuring on the SharePoint server. Product behaviors can be restricted along three dimensions:

·Available actions

·Unrestricted users

·Suppressed events

Configuring the behavior of the Content Matrix client from target SharePoint servers requires that an XML configuration file be added to the target SharePoint server web application directory. The XML file must be named ServerAdapterConfig.xml and placed in the ML folder directory located within the SharePoint hive (this is the same directory where the Metalogix SharePoint Extensions Web Service files are). Below are some examples of the typical directory location of the ML folder, depending on SharePoint product version and configuration:

·SharePoint 2013: - C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\isapi\ML

·SharePoint 2016: - C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\isapi\ML

·SharePoint 2019:-  C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\isapi\ML

Below is an example of the simple XML format required for ServerAdapterConfig.xml.

   <ServerAdapterConfig>

     <DisabledActions>

       <Action>Metalogix.SharePoint.Actions.Migration.PasteSiteAction</Action>

       <Action>Metalogix.SharePoint.Actions.Migration.PasteSiteCollectionAction</Action>

       <Action>Metalogix.SharePoint.Actions.Migration.PasteSiteLists</Action>

    <Action>Metalogix.SharePoint.Actions.Migration.CopyRoleAssignmentsAction</Action>

    <Action>Metalogix.SharePoint.Actions.Migration.CopyWorkflowAssociationsAction</Action>

    <Action>Metalogix.SharePoint.Actions.Migration.PasteFolderAction</Action>

     </DisabledActions>

     <ExemptUsers>

       <User>METALOGIX\geordie</User>

       <User>METALOGIX\julien</User>

     </ExemptUsers>

     <SuppressEvents>False</SuppressEvents>

   </ServerAdapterConfig>

There are three main sections within the root ServerAdapterConfig section of this XML:

·DisabledActions: This section defines the set of actions that cannot be run on the client.  See Actions That Can Be Disabled on the Server Side for a complete list.

·ExemptUsers: This section defines the set of users by user name who are exempt from any DisabledActions. In other words, a user in the ExemptUsers is not subject to any restrictions imposed on Content Matrix clients by the DisableActions section.

·SuppressEvents: This section defines if any of SharePoint's event receivers are suppressed/disabled during a migration and then restarted once the action is complete. The value for this section is set to "True" by default, but can be manually configured if want event suppression to be disabled. Suppression of event receivers allows Content Matrix to avoid any potential concurrency issues when migrating (mainly with regards to workflows).