NOTE:  For Global (Domain, Url, Guid, and User) Mappings, the Distributed Database is populated with the local mappings from the very first connecting agent, and these mappings are shared among all agents that connect to the Distributed Database.  

To submit a Distributed Migration job:

1.Make sure the machine is connected to the Distributed Database  (from the Job List, choose File > Connect to Distributed Database).

2.When prompted, if you would like to copy current Global Mappings and local settings to the Distributed Database, click [Yes].  

This will overwrite Global Mappings and local settings currently saved in the Distributed Database and used by all agents

NOTE:  If you made changes to Global Mappings and/or local settings after you connected to the Distributed Database and would like to use them, disconnect from the Distributed Database (by choosing File > Connect to Jobs Database) then reconnect to the Distributed Database to display this dialog.

3.From the Job List, select the job(s) you want to submit.'

NOTE: You can select multiple rows to submit more than one job at a time.

4.From the Job List, select Run Jobs Remotely to submit the job for Distributed Migration. Alternatively, right-click the selected row to display the pop-up action menu. Select the Run selected job remotely option.

The Manage Queue dialog opens. You can now monitor your jobs from this dialog.

5.To view logs that are Running or Done, from the Job List toolbar, choose File > Refresh.

If Content Matrix has been configured for Distributed Migration, you can manage the Distributed Migration job queue from any machine that is connected to the Distributed Database.

To open the Manage Queue dialog:

From the Content Matrix Console ribbon Connection tab, select Manage Queue.

NOTE:  If the Manage Queue button appears disabled, the Content Matrix Console is not connected to use a configured Distribution Database.

The Manage Queue dialog displays a list of migration Jobs, called the Distributed Migration Job list. The information presented in the various columns are as follows:

You can select a job from the list by clicking anywhere on the row. A row selector icon and the highlighted row indicates the selected row.

1.From the Manage Queue dialog, select the job that you want to delete from the Distributed Migration Job list. The row selector icon and the highlighted row indicates the selected row.

NOTE: Only jobs with a status of Queued or Done can be deleted. Deleting a job from the queue will not remove or delete any of the logging information that has already been sent to the main Job list for the Agent Database.

2.Click Delete Job.

(If the button is disabled, check that the selected job has a status that is either Queued or Done.)

A dialog will display asking you to confirm the deletion.

In order to create a PowerShell (PS) script for Content Matrix, a job list (or batch file) must first exist in the Job List section of the Content Matrix Console.  Once created, it can be run from the PowerShell console or scheduled to run as a Windows Scheduled task.

NOTES:

· It is recommended that the connections to the source and target environments have the Remember my password check-box selected. This is to ensure that the PowerShell scripts will be able to establish a connection to both the source and target environments when they are being run. If a password is required and this check-box is not set, the migration will fail. However, users can manually enter this value into the PowerShell script itself if the option was not checked when the script was first generated.

·Web Browser Authentication, O365 Web Browser Authentication, and Forms-based Authentication are not supported for running a job using a PowerShell script.

Refer to the Quest Support Knowledge Base article Connections that will work with PowerShell and Connections that doesn't work with PowerShell for complete details.

To create a PowerShell script:

1.In Job List, and select the job (or jobs) that you want to run in PowerShell.

2.Click the Generate PowerShell Script button in the Job List tool bar, or right-click on one of the items and select Generate PowerShell Script from the context menu.

3.From the drop-down, choose the appropriate option.  Use the information in the following table for guidance.

Once the PS script generation type is selected, Content Matrix Console will generate a PS script for the select Job, which will be written to a Microsoft Notepad file. If multiple jobs are selected they will all be written to the same file.

4.Choose File > Save As... and select any desired save location for the PowerShell script. Give the file any name you want, but change the file type to .PS1.

The PowerShell (PS) script itself contains five sections. They are:

·Section 1 - This first section at the top (starting with an "if" statement) runs a check in the PowerShell console to make sure that the Metalogix snap-ins have been added. If they are not found then it will add them to that instance of the PS console.

·Section 2 - Load Configuration settings - This section will find and load all of the Content Matrix client application configuration settings into the PowerShell script. These are the client application's environmental settings and not the migration/action settings.

·Section 3 - Load source - This section will load all of the data for the source environment connection.

·Section 4 - Load target - Similar to the previous section, this will load target environment's connection information.

·Section 5 - Run the action - Last is the "Run the action" section. This last section will contain all of the other data for the migration, such as the type of migration (i.e. a site migration, list migration, item migration, etc.) and all of the settings and configurations for the migration/action that is being run. This includes things like settings for versions, content types, permissions, etc.

Now you can run or schedule the PowerShell script.