Metalogix Content Matrix can check links within a SharePoint site, list, folder, and item, either before or after a migration.
Unlike Link Correction, which will correct and update links that have been migrated to the target, the Check Links feature runs a check of the links to see if they point to valid URLs inside lists and Web Parts. Results are returned in an XML file that contains a summary, and lists successes, failures, and flagged links.
The Check Links action can be run on any SharePoint node in the Explorer View tab, regardless of the connection type.
This option is only available when Advanced Mode is enabled.
To run a link check:
1.In the Explorer View, select the node whose links you want to check.
2.Right-click and choose Check Links.
3.Make sure the applicable options on the Check Links General Options tab are selected. Use the information in the following table for guidance.
Then make sure the following option is checked
·you are checking links at the site level
·you want to recursively check links through any sub sites.
Check child sites recursively.
NOTE: If you uncheck this box, the Check Links action will be performed on the selected site only.
·you are checking links at the site level
·You want to check links on web parts, including the links in the web part's properties.
Check web parts.
NOTE: This option is also useful for identifying links you may not have known were present in the web parts.
you want the Check Links action to:
·parse through all of the "text" type fields columns (single line of text, multi-line, etc.) for the selected SharePoint node
·run the check on any absolute URLs
This check will only work on absolute URLs (such as "http://Metalogix/Production" but it will not work for relative URLs (such as "./Production").
Check list item text fields (this can take a long time).
If this option is selected, it can significantly increase the amount of time it takes to run the Link Check action. This is because Metalogix Content Matrix will have to parse all the text values, for the included "text" type field columns, and look for links within that content before it can check them. The amount of time taken will be dependent on the amount of data within the text columns.
you want to include successful URL checks in the XML output file
NOTE: If you uncheck this box, only failed or flagged URLs will be included in the output file.
In addition, you can change the "X" Pages response timeout (ms) value, which represents number of miliseconds after which Metalogix Content Matrix will wait before it considers the URL data request to be failed due to a timeout.
4.If you want to flag URLs based on specified conditions, select the Link Flagging tab.
5.To Add a URL flag to the list:
b)In the Check Link Flags Editor dialog, select a Condition from the drop-down.
c)For Value, enter the string within the url that should be flagged.
6.For Flag Type, choose how the condition is to be applied. The options are:
§OR - When multiple "OR" conditions are set, only one of them need to be present in the checked URL for it to be flagged. For example, if one condition is "OR Ends with .aspx" and a second condition is "OR Ends with .docx" then the checked link will be flagged if it ends with either ".aspx" OR ".docx" file extensions.
§AND When multiple "AND" conditions have been set, then ALL of these conditions must be met in order for the link to be flagged.
7.Once of the flag conditions have been set, click [OK].
The conditions display in the window.
NOTE: You can also Edit and Remove previously created flags.
8.To start the Link Check action, click [OK].
The Link Check will start and a status box will be displayed.
The [Details>>] button. After the action has completed a note will be displayed in the bottom left corner of the dialog stating the number of completions, as well as any warnings or errors that may have been encountered.can be viewed (in progress or after the migration is finished) by clicking the
Once the check is complete, a dialog window will open giving users the option to view the XML results. Click [Yes] to review the XML log, or click [No] to close the dialog. The dialog window will also display the location of the generated XML from the Link Check.
Additionally, you can access the results log of the resultsd3de at a later date from thesection.
Metalogix Content Matrix can display the Metalogix StoragePoint details for any document items that have been offloaded to StoragePoint.
NOTE Currently, StoragePoint Details functionality will be disabled for SharePoint 2019 as it is not currently supported.
To view StoragePoint details:
1.In Explorer View, navigate to a SharePoint Document Library that contains items that have been offloaded to StoragePoint.
2.Switch to the Items View tab.
3.Select an item, right-click and choose StoragePoint Details.
NOTE: The StoragePoint Details option will only be available in the menu if the selected items have been offloaded into StoragePoint. If the selected item has not been offloaded to StoragePoint the StoragePoint Details options will not be available. Only one item can be selected at a time.
The Storage Point Details dialog provides the below information:
§Address - The web address for the specified item within SharePoint.
§Endpoint Relative Folder - The folder that has been configured as endpoint for the offloaded item (i.e. the location of the item in the offloaded storage space).
§Filename - The StoragePoint file name reference that is left behind in SharePoint after the item has been offloaded.
4.When finished, click [Close].
Before configuring a migration, it is important to understand how Metalogix Content Matrix migrates various SharePoint components so that you can plan appropriately. These include:
The Master Pages Gallery is basically a Document Library at the root of a site.
Metalogix Content Matrix can work with Master Pages at two levels:
·At the Site Collection level, where it can copy master pages and page layouts.
·At the Site level, where it can preserve the master page association.
When a SharePoint site is migrated, Metalogix Content Matrix will run a check to see if a master page with the same name as the source site's master page exists. There are then two main scenarios:
·Migrating from an older version of SharePoint to a newer version of SharePoint - Because master pages are quite different between different versions of SharePoint, when master pages are migrated from an older version of SharePoint to a newer version, a suffix will be appended to the end of the master page name based on the source UI version. For example, if you are migrating from MOSS 2007 to a later version, the master pages will have "_2007" appended to the end of the master page name. If migrating from SharePoint 2010 to a later version, the suffix would be "_2010" instead.
When a SharePoint site is migrated, Metalogix Content Matrix will look for the source master page by name. If the master page name is found, Metalogix Content Matrix will then do another check to ensure that the correct UI version is being used on the target site collection. If this UI version also matches, then the master page will be used for the migrating site. If the UI version is not the same, then the current default master page will be used instead.
If the master page cannot be found by name, then Metalogix Content Matrix will check to see if there is another master page that has the same name plus the appended UI version suffix that would represent the source. For example, if migrating from SharePoint 2013 to SharePoint 2016 and the master page is named "AccountMaster3," then Metalogix Content Matrix will look for a master page with the same "AccountMaster3" name. If that fails it will then look for a master page with the same name plus "_2013" appended to the end, like "AccountMaster3_2013." If this is found, then the same UI version check will be run that is used for the exact same master page name, and the same results will be given.
If no master page with the same name is found, either the direct same name, or the name with the UI version appended to the end, then the current default master page will be used instead.
NOTE: If the master page belongs to a UI version that is not supported by the target SharePoint instance, the master page will be skipped.
·Migrating between similar versions of SharePoint - For migrations that are run between the same basic UI version of SharePoint, such as SharePoint 2013 to SharePoint 2013 and SharePoint 2016 to SharePoint 2016, Metalogix Content Matrix will look for a master page with exactly the same name as the master page on the source. If one is found, then Metalogix Content Matrix will use that master page. If no master page with the same name is found, then the current default master page will be used instead.