You can enable trace logging on the machine where Content Matrix is installed and migrations are run to assist Quest Support with troubleshooting.
To enable trace logging:
1.Open the file LogSettings.xml, which can be found in one of the following folders:
·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
2.Set <LoggingLevel> to one of the values described in the following table.
WARNING: When trace logging is enabled, entries are appended to the log file for each migration job that is run, and the same log file is used for all editions. This means the log file can become very large, which is why it is recommended that you only enable trace logging at the request of Quest Support.
Value |
Description |
---|---|
None [Default] |
Trace logging is disabled (i.e., no entries are written to the log file). |
Error |
Only Error messages are logged. |
Debug |
Error and Debug messages are logged. NOTE: Debug should only be used for advanced troubleshooting as it may impact migration performance. |
Log entries are written to the file MetalogixGlobalLog.txt, which is located in the same folder as LogSettings.xml.
Content Matrix can generate PowerShell scripts to be used to migrate SharePoint content through the PowerShell command window. You can also use PowerShell to perform other actions, including:
·triggering a job in the Content Matrix Console to run
The Content Matrix PowerShell Console shortcut is added to the same Start Menu folder location where the to Content Matrix Consoles are placed after installation. The same PowerShell console can be used for any edition, as long as the edition-specific snap-ins are used. You can also use a standard PowerShell console or PowerShell ISE.
Whenever a new PowerShell session is launched, the edition-specific snap-ins must be added before you can perform a Content Matrix action.
NOTES:
· If you have more than one edition of Content Matrix, only one edition can be run per PowerShell session.
·If Content Matrix settings is changed, in order to apply new settings all PowerShell sessions must be restarted.
To add the PowerShell cmdlets for the application framework:
1.Open a Powershell ISE or PowerShell console session.
2.Run the Add-PSSnapin command and by pasting in the following text:
if ( $PsVersionTable.PSVersion.Major -lt 3 ) { Write-Host "Windows PowerShell Version 3.0 or later needs to be installed in order to run Content Matrix PowerShell scripts."; exit; }if ( (Get-PSSnapin -Name Metalogix.System.Commands -ErrorAction SilentlyContinue) -eq $null ) { add-pssnapin Metalogix.System.Commands | out-null }if ( (Get-PSSnapin -Name Metalogix.Exchange.Commands -ErrorAction SilentlyContinue) -eq $null ) { add-pssnapin Metalogix.Exchange.Commands | out-null }if ( (Get-PSSnapin -Name Metalogix.SharePoint.Commands -ErrorAction SilentlyContinue) -eq $null ) { add-pssnapin Metalogix.SharePoint.Commands | out-null }if (Get-Command Set-MetalogixJobPrerequisites -ErrorAction SilentlyContinue){ Set-MetalogixJobPrerequisites -Value "Content Matrix Console - Public Folder Edition" }
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.
© ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center