Chatta subito con l'assistenza
Chat con il supporto

Metalogix Content Matrix 9.4 - 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
How Team Sites are Migrated to Modern Team Sites How SharePoint Sites are Migrated to Modern Communication Sites How MySites are Migrated How "Share With" Metadata is Migrated to SharePoint Online Using the Import Pipeline How Records Centers are Migrated to SharePoint Online Using the Import Pipeline How Master Pages are Migrated How List Template Galleries Are Migrated How Content Types are Migrated Document Version and Checked Out File Limitations How Ghosted and Un-Ghosted Pages are Migrated How Document Sets are Migrated How Navigation is Migrated How Classic Web Parts are Migrated How Site Themes are Preserved How Site Features Are Migrated How Managed Metadata is Migrated How Users and Permissions are Migrated How BCS/BDC Data is Migrated How OneNote Notebooks are Migrated How Customized Form Pages are Migrated How InfoPath Forms are Migrated How SharePoint Workflows are Migrated How Nintex Workflows and Forms are Migrated How Metalogix StoragePoint Content is Migrated How Link Correction Works
Initiating a Migration Configuring Copying Options Saving or Running a Migration Job Copying SharePoint Objects as a Separate Action Converting Classic Pages to Modern Pages After a Migration 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

Copy-MLSharePointPermissionLevels

Navigation:  Using PowerShell with Content Matrix > Content Matrix PowerShell Commandlet List > Metalogix.SharePoint.Migration.Commands >

Copy-MLSharePointPermissionLevels

·RecursivelyCopyPermissionLevels - Recursively Copy Permission Levels.

·VerboseLog - Enables verbose logging.

·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.

Copy-MLSharePointPermissions

Navigation:  Using PowerShell with Content Matrix > Content Matrix PowerShell Commandlet List > Metalogix.SharePoint.Migration.Commands >

Copy-MLSharePointPermissions

·LogSkippedItems - Indicates that actions which have been skipped should not be logged at all.

·CheckResults - Indicates whether the user would like to use the Metalogix Comparison tool to compare the source and target. If chosen, differences will be outputted as warnings to the PowerShell console. All results for an operation can be seen by enabling verbose display.

·ComparisonLevel - Indicates whether a strict or moderate comparison is desired. Note that this has no effect if CheckResults is false.

·ForceRefresh - Forces a refresh of the source and target nodes prior to copying to ensure that all cached data is up to date.

·AllowDBUserWriting - Sets user writing operations to use a direct database write when the user is no longer available in Active Directory. Requires that your environment settings be configured to allow DB writing.

·MapGroupsByName - Indicates if mapping of SharePoint groups should be done by name, rather than membership.

·OverwriteGroups - Indicates if groups with matching names should be overwritten. Note that this only applies when mapping is being done by name.

·MapMissingUsersToLoginName - Map all missing users to this Login Name.

·CopyRootPermissions - Indicates that the permissions for the top-level node specified should be migrated even if that object inherits its permissions.

·ClearRoleAssignments - Indicates that permissions that previously existed on the source should be deleted. This options should be set except in the case of merging permissions from distinct sources.

·MapRolesByName - Indicates that the copy operation should map permission levels by name rather than by mapping to the level with the set of enabled rights most similar to the source.

·RoleAssignmentMappings - Defines a set of custom mappings to use for permission levels.

·VerboseLog - Enables verbose logging.

·PersistMappings - When set, any dynamically created link correction or GUID mappings will be persisted to the global mappings store. If the global mappings already contain an entry for a particular source GUID, it will be overwritten with the value dynamically generated by the action.

·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.

Copy-MLSharePointSite

Navigation:  Using PowerShell with Content Matrix > Content Matrix PowerShell Commandlet List > Metalogix.SharePoint.Migration.Commands >

Copy-MLSharePointSite

This is the same as Copy-MLAllSharePointSiteContent with additional parameters:

·WebTemplateName - Defines the name of a new web template for the site being copied.

Copy-MLSharePointSiteAlerts

Navigation:  Using PowerShell with Content Matrix > Content Matrix PowerShell Commandlet List > Metalogix.SharePoint.Migration.Commands >

Copy-MLSharePointSiteAlerts

·RecursivelyCopySubsiteAlerts - Indicates if the copy operation should copy the alerts for child sub sites.

·CopyListItemAlerts - Indicates if the copy operation should copy the alerts for items in lists.

·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.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione