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 Metalogix 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 Metalogix Content Matrix to avoid any potential concurrency issues when migrating (mainly with regards to workflows).

Many of the SharePoint related actions available in the Metalogix Content Matrix Console can be disabled on the server side. The table below lists the complete set of client actions that can be disabled from the server and provides the format of the action name required in the DisabledActions section of the ServerAdapaterCongifuration.xml file.

NOTE: When an action that is available via the client UI is disabled on the server, it will be visible in client menus but disabled.

Note that many of the above listed actions are used by other actions. When a given action is enabled, but one or more of its sub-action is disabled, the sub-actions will not run. When a user attempts to run an action for which sub-actions are disabled, they will be notified with a dialog similar to the following:

Metalogix Content Matrix uses a set of configuration variable files behind the scenes to help set and manage settings for all of the Metalogix Content Matrix Editions. This section explains what the configuration variable files are, their general behavior, and where to find them.

Configuration variables are contained in the following three files:

·EnvironmentSettings.xml

·UserSettings.xml

·ApplicationSettings.xml

Some settings can be configured for all Product Editions, while other settings are limited to individual Product Editions.

Any settings that are configured in multiple files will be scoped to the lowest level (either in the "UserSettings.xml" file or the "ApplicationSettings.xml" file), including values that are pulled from the old EnvironmentSettings.xml file.

IMPORTANT:  Make sure the Content Matrix Console is closed when making updates to configuration variable files.

EnvironmentSettings.xml File

This file allows users to configure general settings for all Product Editions. This means that these settings only need to be set in a single file, either for all users of the machine (if users are required to be local administrators) or for each individual user of the machine (if users are not required to be local administrators) and can be found in one of the following locations:

·If you are required to be a local administrator on the machine where Content Matrix is installed: C:\ProgramData\Metalogix

OR

·If you are not required to be a local administrator on the machine where Content Matrix is installed: C:\Users\<username>\AppData\Roaming\Metalogix\Common

UserSettings.xml File

This file allows users to configure general settings for all Product Editions for a specific user account (the logged in account). This means that these settings will be configured for all Product Editions, but only for the current user account. If another user would like to configure these same settings to work for them, they must be configured manually under the appropriate user account.  It can be found in the following location:

C:\Users\<USER>\AppData\Roaming\Metalogix

ApplicationSettings.xml File

This file allows users to configure settings that are limited to the specific Product Edition of Metalogix Content Matrix Console, for a specific user account (the logged in account). This means that each Product Edition, for every user account, must be configuredindividually. While the "ApplicationSettings.xml" file for each Product Edition can contain some of the same settings, there are some settings that are Edition specific (for example, some settings may only work for eRoom Edition, so they will only be available in eRoom Edition). Any settings that are replicated through various version of the file will only be applied to the specific Edition.

For example, the "AllowCheckResults" setting is available in every "ApplicationSettings.xml" file, but it must be set on an individual Product Edition basis. Setting it for SharePoint Edition will not configure it for eRoom Edition.  It can be found in the following location:

C:\Users\<USER>\AppData\Roaming\Metalogix\Content Matrix Console - <Product> Edition.

For an individual Metalogix Content Matrix Console instance, you can Change the Managed Metadata Migration Batch Size, Configure Settings for Migrations Using the Import Pipeline, and/or Configure Content Matrix to Run in a FIPS-Enalbled Environment.