Converse agora com nosso suporte
Chat com o suporte

Content Matrix 9.10 - SharePoint Edition

Introduction Activating the License Key Selecting the SQL Database You Want to Connect to Content Matrix Console End User Interface Enabling Advanced Mode 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 Promotion of First Level Subsites to Site Collections 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 Link Correction StoragePoint Content Migration
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
DB_Owner Permission Keyboard Shortcuts Activating the License Key Silently License Key Troubleshooting Errors Connecting to SharePoint 2019 or SharePoint Server Subscription Edition in a FIPS-Enabled Environment Determining the Status of a Migration Running in the Background MySite and User Profile Migration Issues Optimal Setup for Best Performance Migrating SharePoint On Premises Using Proxies, Load Balancing or Alternate Access Mappings Extensions Web Service Installation Files Migrating JavaScript Migrating Site Variations Migrating with SharePoint Document IDs Changing a Job Configuration for Multiple Files SharePoint Site Collection Creation Issue Customized Wiki Page Web Part Zones Not Being Migrated Preserving SharePoint List Item IDs When Migrating to SharePoint Online Retrying Failed Document Copies to SharePoint Online CSOM Connections Import Pipeline Batches Getting Stuck Migrating Content When the Source Custom List Template is Missing When Migrating to SharePoint Online HTTP Status Code 429 (“Too many requests”) or 503 (“Server Too Busy”) Message Returned How Do I Identify and Remove Containers and Queues from My Azure Private Storage Account? Error: 'The object is associated with property AssociatedMemberGroup.' Migration Error: 'ERROR, the batch will be resubmitted to the import pipeline' Item Count at Target is Increased When Migrating Using the Import Pipeline Custom Lists with Versioning Enabled Not Being Migrated When Using the Import Pipeline Supported Nintex Actions for SPO Migration Support for GCC High Tenants
About Us

Copy-MLSharePointSiteCollection

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

·OwnerLogin - The login name of the primary owner of the site collection to be added. (Mandatory)

·WebApplicationName - The name of the web application to add the site collection to. (Mandatory)

·Path - The managed path in the web application to add the site collection under. (Mandatory)

·Name - The site collection URL name. Can not include the managed path. (Mandatory)

·URL - DO NOT USE: The URL of the site collection. Includes managed path, and will be set automatically via other parameters. Exists for automated script generation purposes and bypasses validation.

·SecondaryOwnerLogin - The login name of the secondary owner of the site collection to be added.

·Description - The description of the site collection.

·ContentDatabaseName - The content database name to add the new site collection to.

·LanguageCode - The 32 bit integer language code of the SharePoint language to use.

·CopySiteQuota - Indicates if a site quota template should be set on the target. If no QuotaID or individual values are specified, the quota will be set to match the source.

·QuotaID - The ID of the quota template to use.

·QuotaMaximum - The maximum storage limit to use for this site collection. Note that if a valid QuotaID is also specified, that quota template will be used instead.

·QuotaWarning - The storage level to send out a warning email to use for this site collection. Note that if a valid QuotaID is also specified, that quota template will be used instead.

·StorageQuota - The Microsoft 365 tenant storage quota.

·ResourceQuota - The Microsoft 365 tenant resource quota.

·CopySiteAdmins - Indicates if the source site collection administrators gets copied to the target. If not selected, the Primary and Secondary site admins will be copied.

·SiteCollectionAdministrators - The source site collection administrators to be migrated to the target site collection.

·CorrectMasterPageLinks - Indicates if link correction should be run on the contents of master pages.

·CopyAuditSettings - Indicates if site collection level audit settings should be copied.

·CopyListTemplateGallery - Indicates if the list template gallery should be copied.

·CopyMasterPageGallery - Indicates if the master page gallery should be copied.

·CopyMasterPages - Indicates if master pages in the master page gallery should be copied.

·CopyPageLayouts - Indicates if page layouts in the master page gallery should be copied.

·CopyOtherResources - Indicates if other resources, such as images, in the master page gallery should be copied.

·PromoteSubsiteToSiteCollection - Indicates if the first level of subsites should be promoted as site collections on the target.

·AssociateSiteCollectionWithHub - Indicates if the source root site should be migrated as a hub site and the promoted site collections should be associated to the new hub site.

·AssociateRootAndPromotedSubSiteToHubSite - Indicates if the root site and the promoted site collections should be associated to an existing hub site of the same tenant.

·HubSiteUrlToAssociate - Indicates existing hub site URL to which the root and the promoted site collections need to be associated to.

 

Copy-MLSharePointSiteCollectionWithConfigFile

·Source - The source node for the actions. (Mandatory, should be specified as Get-MLSharePointSite)

·Target - The target node for the actions. (Mandatory, should be specified as Get-MLSharePointServer)

·JobConfigFile - The filepath of the job configuration XML file. (Mandatory)

·JobFile - The name of a job file to use for logging. If the file does not exist it will be created.

Note: If any additional parameters are provided, or if the job configuration XML file is improperly formatted, an error may appear and the migration action may fail.

Copy-MLSharePointSiteWithConfigFile

Source - The source node for the actions. (Mandatory, should be specified as Get-MLSharePointSite)

Target - The target node for the actions. (Mandatory, should be specified as Get-MLSharePointSite)

JobConfigFile - The filepath of the job configuration XML file. (Mandatory)

JobFile - The name of a job file to use for logging. If the file does not exist it will be created.

Note: If any additional parameters are provided, or if the job configuration XML file is improperly formatted, an error may appear and the migration action may fail.

Copy-MLSharePointUsers

·SourceUsers - A collection of users to be copied to the target site.

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

·OverrideCheckouts - Indicates that the checkout status of a pre-existing target file will be overridden.

·CorrectingLinks - Indicates whether the user would like to employ automatic link correction to metadata fields within their copy.

·LinkCorrectTextFields - Indicates whether the user would like to employ automatic HTML link correction in text fields of items/documents.

·LinkCorrectionScope - Specifies the scope at which links are corrected. The current options are 'SiteCollection' and 'MigrationOnly' level scope.

·UseComprehensiveLinkCorrection - Indicates whether link correction mapping generation is performed before the migration or as the migration occurs.

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

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

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

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

·MapAudiences - Enabled the mapping of audiences during a copy.

·VerboseLog - Enables verbose logging.

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

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

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação