Converse agora com nosso suporte
Chat com o suporte

Content Matrix 9.5 - SharePoint Edition User Guide

Introduction Activating the License Key Selecting the SQL Database You Want to Connect to Content Matrix Console End User Interface Enabling Advanced Mode Connecting and Migrating Account Requirements Multilingual Support Connecting to SharePoint Preparing for a Migration How Content Matrix Handles Various SharePoint Components
Team Site to Modern Team Site Migration SharePoint Sites to Modern Communication Site Migration MySite Migration "Share With" Metadata and "Sharing Links" Access Permissions Migration Records Center to SharePoint Online Migration Using the Import Pipeline Master Page Migration List Template Gallery Migration Content Types Migration Document Version and Checked Out File Limitations Ghosted and Un-Ghosted Page Migration Document Set Migration Navigation Migration Classic Web Parts Migration Site Theme Preservation Site Feature Migration Managed Metadata Migration Users and Permissions Migration BCS/BDC Data Migration OneNote Notebooks Migration Customized Form Pages Migration InfoPath Forms Migration SharePoint Workflow Migration Nintex Workflows and Forms Migration StoragePoint Content Migration Link Correction
Initiating a Migration Configuring Copying Options Saving or Running a Migration Job Copying SharePoint Objects as a Separate Action Configuring Hub Sites Incremental Migration Using PowerShell with Content Matrix
Adding PowerShell Snap-Ins for the Application Framework Content Matrix PowerShell Commandlet List
Metalogix.System.Commands Metalogix.SharePoint.Commands Metalogix.Jobs.Reporting.Commands Metalogix.SharePoint.Migration.Commands
Modifying Content Matrix Configuration and Settings Configuring Content Matrix for Distributed Migration Frequently Asked Questions About Us

Auto User Mapping

For migrations to SharePoint Online, unless users are mapped explicitly all users will be automatically mapped from a source domain to a domain with the same name on the target.

IMPORTANT: Users will not be automapped if the Import Pipeline is used.

For example, if you are migrating users from an Active Directory domain called quest on the source to users in an Office 365 tenant domain has the same name, the users would be migrated as follows:

quest\amahfudh -> amahfudh@quest.onmicrosoft.com

quest\doconnor -> doconnor@quest.onmicrosoft.com

quest\fsullivan -> fsullivan@quest.onmicrosoft.com

quest\gbond -> gbond@quest.onmicrosoft.com

and so on.

NOTE:  If the source and target domains have different names, you can use Domain Mappings.

To bypass some of the limitations with Auto User Mapping (including use of the Import Pipeline) and to provide more flexible mapping options for both on premises and online targets, you can instead use a utility available from Quest Support to generate, configure, and import User Mappings.

Generating, Configuring, and Importing User Mappings with the UserMappingCLI Utility

Navigation:  Configuring Copying Options > Mapping Options > Global Mappings > User Mappings >

Generating, Configuring, and Importing User Mappings with the UserMappingCLI Utility

Quest Support offers a powerful command line utility to help with automatically generating and configuring user mapping files, along with PowerShell Cmdlets for importing user mappings as a .csv file.  For a copy of the utility with complete instructions, visit https://support.quest.com/metalogix-content-matrix/kb/311358/best-practices-for-generating-configuring-and-importing-user-mapping.

Domain Mappings

Navigation:  Configuring Copying Options > Mapping Options > Global Mappings >

Domain Mappings

In addition to allowing you to map individual users explicitly, Metalogix Content Matrix allows you to map all users from one domain to another, across both SharePoint on premises and SharePoint Online environments.  

Domain Mapping can be used in conjunction with explicit user mapping.  For example, you can map all users across a domain, and then map specific users into other user accounts.

NOTE:  Domain mappings can also be imported using the Import mappings from XML option, but Quest recommends the use of the UserMappingCLI utility as the most powerful way to generate, configure, and import user mappings for a variety of scenarios.

 

IMPORTANT:  If you want to migrate an AD group to an Office 365 group that does not already exist on the target site, then you must use the Import mappings from XML option to map the source AD group SID to the target Office 365 group ID.

Specify Global Mapings

 

Connection icon

Domain Mapping supports the following connection types on both source and target:

·SharePoint on premises local and remote (MEWS) Object Model

·SharePoint Online CSOM and the Import Pipeline.

 

NOTE:  If you do not specify an extension for an online domain, .com will be used.  

EXAMPLES:

·If you have an on premises source domain called quest, and you map it to a SharePoint Online target domain called questsoftware.com, you could enter the mapping as shown below.

DomainMapping Wild Card

In this example, users would be migrated as follows:

quest\amahfudh -> amahfudh@questsoftware.com

quest\doconnor -> doconnor@questsoftware.com

quest\fsullivan -> fsullivan@questsoftware.com

quest\gbond -> gbond@questsoftware.com

and so on.

·If you have an on premises source domain called quest, and you map it to a SharePoint Online target domain called questsoftware.net, you would enter the mapping as shown below.

Domain Mapping.net

In this example, users would be migrated as follows:

quest\amahfudh -> amahfudh@questsoftware.net

quest\doconnor -> doconnor@questsoftware.net

quest\fsullivan -> fsullivan@questsoftware.net

quest\gbond -> gbond@questsoftware.net

and so on.

·If you have an online source domain called questsoftware.com and you map it to a target domain called questsoftware.net, you could enter the mapping as shown below.

Domain Mapping SPO to SPO

In this example, users would be migrated as follows:

amahfudh@questsoftware.com -> amahfudh@questsoftware.net

doconnor@questsoftware.com -> doconnor@questsoftware.net

fsullivan@questsoftware.com -> fsullivan@questsoftware.net

gbond@questsoftware.com -> gbond@questsoftware.net

To map domains:

1.In the Specify Global Mappings dialog select the Domain Mappings tab.

2.Click New to display the Create Domain Mapping dialog.

CONTEN~1_img106

3.Enter the Source Domain name and the Target Domain name.  Use the information in the following table for guidance.

Source

Target

Format/Example

On Premises

On Premises

Source Domain: quest

Target Domain:   questsoftware 

NOTES:  When migrating Claims-enabled accounts, remember to include the Claims prefix.  For example: i:0#.w|quest -> i:0#.w|questsoftware.

On Premises

SPO

Source Domain: quest

Target Domain:   questsoftware (or questsoftware.com)

SPO

On Premises

Source Domain: questsoftware (or questsoftware.com)

Target Domain:   quest

4.Click [OK].

URL Mappings

Navigation:  Configuring Copying Options > Mapping Options > Global Mappings >

URL Mappings

Metalogix Content Matrix can set explicit mappings for URLs which can be used with link correction.  While link correction only applies to the content that exists within the scope of the migration, URL mapping can help by-pass this issue for any mappings that are specifically set.

For example, if there is a link within some content that is being migrated, and this link points to a URL location that is outside of the migrating content, a URL mapping can be set up for it. Then after migration, this link will point to the URL that the mapping was set up for, despite the target URL being outside the scope of the migrating content. If there are any other links to content that exists under the location that the URL is mapped to, the links to that sub-content will be corrected as well. For example, if a URL mapping is set to a document library in a location that is outside the scope of the current migration, the URL mapping will correct the links that point to this document library. In addition, any links within the migrating content that are pointing to any folders or documents within the document library will also be corrected. Links that point to that document library's site, or other lists in the same site, will not be corrected.

The URL mapping behavior may change if the URLs being mapped exist within the scope of the migration. In this case the link correction within Metalogix Content Matrix will likely override the URL mapping, if the source link has a mapping created for it through the normal link correction process.

You have the option of using the Sites, Lists, and Folders renamed on target option. This option allows you to specify any sites, lists, or folders that may have been renamed during migration. This is only used for link correction purposes, and will not actually rename any sites, lists, or folders

For example, if a site was renamed during migration, this renaming would be entered here so that the link correction would be able to correctly identify the site and correct all the necessary navigation links for it, during the navigation copy.

You can add as many additional mappings as desired. You can also map a single source URL to multiple target URLs.

URL mappings can also be imported using the Import mappings from XML option.

To map URLs:

1.In the Specify Global Mappings dialog select the URL Mappings tab.

CONTEN~1_img107

2.In the Source Address column enter the URL for the source location.

This must be a full URL, and cannot be a relative URL. For example, "http://OldServer/Sales/FactsAndFigures" would be a valid URL value, while "./Sales/FactsAndFigures" or "www.OldServer/Sales/FactsAndFigures" would both be considered relative or invalid URL values.

3.Enter a value in the Target Address column.

This is the same relative address as the Source Address, but using the location of the target side URL.

NOTE: Metalogix Content Matrix will check to see if any entered values in the URL mappings window are valid. This check will ignore any letter case differences or encoding (meaning that "encoding space" and "encoding%20space" are viewed as the same). It should also be noted that spaces in the hostname of the URL are not considered valid. This check applies to both the Source Address and Target Address columns.

4.Click [OK] to return to the Specify Global Mappings dialog.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação