·Scope - The scope of the configuration variable. Possible values are Environment, EnvironmentSpecific, User, UserSpecific, Application, ApplicationSpecific, ApplicationAndUserSpecific. (Default: ApplicationAndUserSpecific). (Mandatory)

·Name - The name of the configuration variable. (Mandatory)

·Value - The value of the configuration variable. (Mandatory)

·Name - The name of the configuration variable ("ResourceTableResourceTableLink"). (Mandatory)

·Value - The value of the configuration variable. This value will indicate where to obtain configuration key settings from. Options are local file system ("Metalogix.ResourceFileTableResolver") or agent database (Metalogix.Core.ConfigVariables.ResourceDatabaseTableResolver). (Mandatory)

Metalogix Content Matrix can generate PowerShell script for you, for any migration action that is available through it. The below cmdlets are used in the generated PowerShell script, but can also be used to write your own script, should you desire to do so. For more information on each cmdlet, simply type get-help [cmdlet]. For example, if you want more information on Copy-MLSharePointList cmdlet you would enter get-help Copy-MLSharePointList, followed by the Enter (return) key.

Below is a list of the available cmdlets (and their parameters), broken up into the available commands for each snap-in.

·WebApplicationName - Name of the Web Application to Create the Site Collection in. Web Application must exist in the specified Target. (Mandatory)

·WebTemplateName - Web (Site) Template to use for the Site Collection. Web (Site) Template must exist. The value must be in the form name#configuration. E.g., STS#1 for Blank Site (Mandatory)

·Language - Language to use for the Site Collection. Can be Language Code (LCID) or Language Name. Language must exist in the specified Target. (Mandatory)

·ExperienceVersion - The experience version to use when creating the site. This setting is only used for SharePoint 2013. Use 15 for the 2013 UI and 14 for the 2010 UI.

·Title - The Title for the Site Collection. (Mandatory)

·Description - Description for the Site Collection.

·Path - Managed Path for the Site Collection. Include forward-slash characters where required. E.g., "/sites/" or "/sites/". (Mandatory)

·URL - Server Relative portion of URL solely used to identify the Site Collection itself. E.g., "TestSiteCollection" (Mandatory)

·HostHeaderSiteCollectionURL - The URL of the host-named Site Collection in the format http://servername.

·OwnerLogin - Domain and username to be used as the Primary Administrator for the Site Collection. E.g., "sampledomain\sample.user" (Mandatory)

·SecondaryOwnerLogin - Domain and username to be used as the Secondary Administrator for the Site Collection. E.g., "sampledomain\another.user"

·ContentDatabaseName - Content Database Name to use. Not specifying this value will use the default content database (auto detect).

·SelfServiceCreateMode - Allow users without Farm Administrator privileges to add the Site Collection.

·SetSiteQuota - Set Quota for the Site Collection.

·QuotaMaximum - Limit site storage to maximum size (Mb). SetSiteQuota must be set to true and SelfServiceCreateMode should be false. Mutually exclusive with QuotaID.

·QuotaWarning - Send a warning email when the site storage reaches this size (Mb). SetSiteQuota must be set to true and SelfServiceCreateMode should be false. Mutually exclusive with QuotaID.

·QuotaID - Use Quota Template. Can be the integer ID or the string name of the Quota. SetSiteQuota must be set to true and SelfServiceCreateMode should be false.

·Transformers - The collection of data transformers which the action needs to run. Note that if the passed-in value for this parameter does not include transformers which are considered mandatory, they will be added automatically.

·Quiet - If set, the operation will not report progress to the PowerShell console.

·JobFile - The name of a job file to use for logging. If the file does not exist it will be created.

·Source - The source node for the actions.

·Target - The target node for the actions.

·JobDatabase - The connection string of a jobs database to use for logging. If the connection string is invalid, an exception is thrown. If both 'JobFile' and 'JobDatabase' parameters are specified, then the 'JobDatabase' parameter will take precedence and the job will only be written to the job database.