·SqlCeDbFilePath - Specify the path to the SQLCE database file that contains the Job History data. (Mandatory)
·ServerName - The name of the SQL Server. (Mandatory)
·DatabaseName - The name of the Job History database. (Mandatory)
·AuthType - Indicates whether to use Integrated (Windows) or SQL Authentication. If not specified will Integrated Authentication will be used.
·Username - Specify the username for SQL Authentication.
·Password - Specify the password for SQL Authentication.
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.
·UserMapper - Defines the user mapping between Exchange and SharePoint users.
·KeepAllDayEvent - Indicates how all day events should be copied between different time zones. If this switch is on all day events will start in the same local time (hours:minutes) in target as were defined in source. Time zone difference is not calculated.
·OutputType - Defines the format in which Exchange items will be migrated to SharePoint. Possible options are: msg, eml.
·SelectedFields - Defines fields which will be migrated from Exchange item to SharePoint item.
·ContainerSplitLimit - Defines the limit for item count in SharePoint lists. If the item count in source Exchange folder reaches this limit, items will be placed in separate folders, which will be created on the fly. These folders will contain no more items than the defined limit.
·VerboseLogging - Indicates if the more detailed logging should be enabled.
·Overwrite - Indicates if the copy operation should overwrite existing items and documents.
·Filters - Defines a filter expression used to determine if a document or item should be copied.
·ContentTypeOptions - Defines a set of content type application rules for the item copying operation.
·EmailServer - An email server to use for sending job completion emails.
·EmailUserName - A user name to use when connecting to the specified email server. If not set, default credentials will be used.
·EmailPassword - A password to use for the specified user when connecting to the specified email server. If no user name is set, default credentials will be used.
·ToEmailAddress - A semicolon delimited list of email addresses to which the job completion email will be sent.
·FromEmailAddress - The email address of the mailbox from which the job completion emails will be sent.
·CCEmailAddress - A semicolon delimited list of email addresses to CC on the job completion email.
·BCCEmailAddress - A semicolon delimited list of email addresses to BCC on the job completion email.
·EmailSuccessTemplateFilePath - The absolute file path of the html template to use for the job completion email when the job is successful.
·EmailFailureTemplateFilePath - The absolute file path of the html template to use for the job completion email when the job fails.
·EmailSubject - A custom subject for the job completion email.
·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.
This is the same as Copy-ExchangeItem with additional parameters.