サポートと今すぐチャット
サポートとのチャット

Content Matrix 9.7 - 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 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 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
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 2013 and Later 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 batch will be resubmitted" Message Displays When Using 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

Set-MetalogixConfigurationVariable

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

Set-MetalogixConfigurationVariable

·Scope - The scope of the configuration variable. Possible values are Environment, EnvironmentSpecific, User, UserSpecific, Application, ApplicationSpecific, ApplicationAndUserSpecific. (Default: ApplicationAndUserSpecific). (Mandatory)

·Name - The name of the configuration variable. (Mandatory)

·Value - The value of the configuration variable. (Mandatory)

Set-MetalogixDefaultResolverSetting

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

Set-MetalogixDefaultResolverSetting

·Name - The name of the configuration variable ("ResourceTableResourceTableLink"). (Mandatory)

·Value - The value of the configuration variable. This value will indicate where to obtain configuration key settings from. Options are local file system ("Metalogix.ResourceFileTableResolver") or agent database (Metalogix.Core.ConfigVariables.ResourceDatabaseTableResolver). (Mandatory)

Metalogix.SharePoint.Commands

Navigation:  Using PowerShell with Content Matrix >

Metalogix Content Matrix PowerShell Cmdlet List

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

Add-MLSharePointSiteCollection

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

Add-MLSharePointSiteCollection

·WebApplicationName - Name of the Web Application to Create the Site Collection in. Web Application must exist in the specified Target. (Mandatory)

·WebTemplateName - Web (Site) Template to use for the Site Collection. Web (Site) Template must exist. The value must be in the form name#configuration. E.g., STS#1 for Blank Site (Mandatory)

·Language - Language to use for the Site Collection. Can be Language Code (LCID) or Language Name. Language must exist in the specified Target. (Mandatory)

·ExperienceVersion - The experience version to use when creating the site. This setting is only used for SharePoint 2013. Use 15 for the 2013 UI and 14 for the 2010 UI.

·Title - The Title for the Site Collection. (Mandatory)

·Description - Description for the Site Collection.

·Path - Managed Path for the Site Collection. Include forward-slash characters where required. E.g., "/sites/" or "/sites/". (Mandatory)

·URL - Server Relative portion of URL solely used to identify the Site Collection itself. E.g., "TestSiteCollection" (Mandatory)

·HostHeaderSiteCollectionURL - The URL of the host-named Site Collection in the format http://servername.

·OwnerLogin - Domain and username to be used as the Primary Administrator for the Site Collection. E.g., "sampledomain\sample.user" (Mandatory)

·SecondaryOwnerLogin - Domain and username to be used as the Secondary Administrator for the Site Collection. E.g., "sampledomain\another.user"

·ContentDatabaseName - Content Database Name to use. Not specifying this value will use the default content database (auto detect).

·SelfServiceCreateMode - Allow users without Farm Administrator privileges to add the Site Collection.

·SetSiteQuota - Set Quota for the Site Collection.

·QuotaMaximum - Limit site storage to maximum size (Mb). SetSiteQuota must be set to true and SelfServiceCreateMode should be false. Mutually exclusive with QuotaID.

·QuotaWarning - Send a warning email when the site storage reaches this size (Mb). SetSiteQuota must be set to true and SelfServiceCreateMode should be false. Mutually exclusive with QuotaID.

·QuotaID - Use Quota Template. Can be the integer ID or the string name of the Quota. SetSiteQuota must be set to true and SelfServiceCreateMode should be false.

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

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択