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

Converting Classic Pages to Modern Pages After a Migration

Navigation:  [No topics above this level]

Converting Classic Pages to Modern Pages After a Migration

After migrating from a classic site to a modern site, you can use a solution provided by Microsoft and PnP Community to convert classic pages within the migrated site to modern pages via the Content Matrix Console.  

IMPORTANT: The assemblies required to run this action are not shipped with Content Matrix and must be obtained from the PnP Community.  If you initiate a Convert Classic Pages to Modern Pages action and the assemblies are missing, a pop-up message will display which includes a link to a Knowledge Base article with step-by-step instructions.  Quest does not provide support for this solution, as Content Matrix only provides users with the capability to run it.  

Supported Objects

The Convert Classic Pages to Modern Pages action converts all applicable classic pages and their web parts to modern pages.  It is available for the following objects:

Site Level:

· Team Site with no Office 365 group (STS#3)

· Team Site with Office 365 group (GROUP#0)

NOTE:  Currently, Content Matrix does not support migrations to this site type.

·Communication Site (SITEPAGEPUBLISHING#0)[

Note that site root pages will also be converted

List level:

Document libraries within a supported site type.

Item level:

Classic pages in a document library within a supported site type.

Converted Page Naming Conventions

Converted modern pages are saved in Site Pages library, along with the original classic pages. By default, the converted page uses the same name as the classic page and the classic page is renamed “Previous_<original_page_name>.aspx.”  If you want classic pages to retain the original name (and continue to display using the existing url), you must change the value of the configuration variable TargetModernPageTakesSourcePageName in the Application Settings.xml file to False.  The modern page will then be named "Migrated_<original_page_name>.aspx; however, the content approval status of the classic page will be changed from Draft to Pending, and a new version of that page will be created.

To convert classic pages to modern pages:

1.Select the object whose pages you want to convert.

2.Right-click and choose Convert Classic Pages to Modern Pages.

NOTE:  This menu option is available only for supported objects.

You can monitor the progress of the action in the Job List.

Current Limitations and Known Issues

·This action is not supported for use with PowerShell or Distributed Migration.

·Conversion of classic publishing pages is not supported.  

·If the Site Pages library requires checkout, target pages are checked out as unpublished.

·If a classic page is checked out by another user during migration, there may be issues in converting the page.

·Approval status is not preserved.

·Metadata except "CreatedBy, Created, Modified" are not preserved on the target page.

·The Modified by field on the target page is set to the connecting user.

·If Content Matrix is uninstalled, DLLs and files deployed for this action are not be removed automatically and will need to be removed manually.

Configuring Hub Sites

Navigation:  [No topics above this level]

Configuring Hub Sites

Hub sites in SharePoint Online provide a way to connect modern team sites and communication sites so that they share the following experiences without the constraints of a site/subsite relationship:

·Common navigation

·News roll up

·Search within a hub

You can register/unregister a hub, associate sites with the hub and change hub associations, and edit hub site settings either from the Content Matrix Console or using PowerShell.

Requirements and Restrictions

·A tenant-level connection is required to perform hub site actions.

·You cannot perform hub site actions on a site that uses a read-only connection.

·Hub site actions are supported for modern team site and communication site templates only.

·Hub site actions can only be performed on one site at a time.

Configuring Hub Sites from the Content Matrix Console

Navigation:  Configuring Hub Sites >

Configuring Hub Sites from the Content Matrix Console

From the Content Matrix Console right-click menu, you can:

·register/unregister a modern team or communication site as a hub site

·edit hub site settings

·associate a site with a hub site

·change hub site associations

To register a site as a hub site:

1.Select the modern team or communication site that you want to register as a hub site.

2.Right-click and choose Register as a Hub Site.

3.Complete the Register as a Hub Site Dialog with the following information:

a)If different than the default (the Title of the site), enter a Hub Name.

b)For Authorized People, enter either the Display Name or email address of the user(s) or security group(s) authorized to you want to allow to associate sites with the hub.  You can enter multiple users/groups as a comma-separated list.

NOTE:  If you leave this field blank, all users will be able to associate their sites with the hub.

4.Click [OK].

When a modern team or communication site is registered as a hub site, the icon to the left of the site is changed to Hub symbol.

To edit hub site settings:

1.Select the hub site for which you want to edit settings.

2.Right-click and choose Edit Hub Site Settings.

3.Update the Hub Name and/or Authorized People as appropriate.

4.Click [OK].

To associate a site with a hub site:

1.Select the modern team or communication site site that you want to associate with a hub site.

2.Right-click and choose Associate with a Hub.

3.From the Edit Hub Association dialog, Select a hub from the drop-down.

4.Click [OK].

When a site is associate with a hub, the icon to the left of the site is changed to Associate Hub icon.

To change a hub site association:

1.Select the site whose hub association you want to change.

2.Right-click and choose Change Hub Association.

3.From the Edit Hub Association dialog, Select a hub from the drop-down.

NOTE:  If you want to remove a hub association completely, select None from the drop-down.  The site theme and shared navigation of the last associated hub will be retained.

4.Click [OK].

To unregister a hub site:

1.Select the hub site you want to unregister.

2.Right-click and choose Unregister as a Hub Site.

3.Click [OK].

All sites associated with the hub site will be disassociated.  However, these sites will retain the site theme and shared navigation previously inherited from the hub.

Configuring Hub Sites Using PowerShell

Navigation:  Configuring Hub Sites >

Configuring Hub Sites Using PowerShell

Using PowerShell, you can:

·register/unregister a modern team or communication site as a hub site

·edit hub site settings

·associate a site with a hub site

·change hub site associations

To access the PowerShell cmdlets for configuring hub sites:

Open a PowerShell or PowerShell ISE session and add the PowerShell snap-ins for the application framework.

The following cmdlets for configuring hubs are now available:

·Get-MLHubSites

·Register-MLHubSite

·Edit-MLHubSiteSetting

·Join-MLHubSite

·Unregister-MLHubSite

To connect to the SharePoint Online tenant:

Use the New-MLSharePoint Connection cmdlet or connect via the Content Matrix Console.

To display a list of sites in the tenant that are already registered as hub sites:

Run the Get-MLHubsites cmdlet and specify either the TenantConnectionID or TenantUrl.

To register a site as a hub site:

1.Select (from the PowerShell ISE Command Window) or enter Register-MLHubSite.

2.Provide the following information:

a)For HubName, enter the name that you want to assign to the hub.

b)Enter the SiteUrl of the modern teams or communication site that you want to register as a hub site.

c)For AuthorizedPeople, enter either the Display Name or email address of the user(s) or security group(s) authorized to you want to allow to associate sites with the hub.  You can enter multiple users/groups as a comma-separated list.

NOTE:  If you leave this field blank, all users will be able to associate their sites with the hub.

3.Enter either the TenantConnectionID or TenantUrl.

4.Run the cmdlet.

Example Scripts:

Register-MLHubSite -TenantConnectionId 555cff48-babd-000b-b000-12132f929d35 -SiteUrl "https://metalogixsoftware.sharepoint.com/sites/IB_Demo_STS3Source_RegisterAsHubSite" -HubName "Communication Hub" -AuthorizedPeople "devadminuser2@metalogixsoftware.onmicrosoft.com, Dev Admin User 1"

 

Register-MLHubSite -TenantUrl "https://metalogixsoftware-admin.sharepoint.com" -SiteUrl "https://metalogixsoftware.sharepoint.com/sites/IB_Demo_STS3Source_RegisterAsHubSite" -HubName "A" -AuthorizedPeople "devadminuser2@metalogixsoftware.onmicrosoft.com, Dev Admin User 1"

 

When a site is registered as a hub, the icon to the left of the site in the Content Matrix Console  is changed to Hub symbol.

To edit hub settings:

1.Select (from the PowerShell ISE Command Window) or enter Edit-MLHubSiteSetting.

2.Enter the SiteUrl of the hub site that you want to edit and either the TenantConnectionID or TenantUrl.

3.Enter  the HubName and AuthorizedPeople with the appropriate values.

IMPORTANT:  You will need to re-enter all AuthorizedPeople, even those that have not changed.  If you leave this parameter blank, all users will be able to associate their sites with the hub.

4.Click [OK].

Example Scripts:

Edit-MLHubSiteSettings -TenantConnectionId 555cff48-babd-000b-b000-12132f929d35 -SiteUrl "https://metalogixsoftware.sharepoint.com/sites/IB_Demo_STS3Source_RegisterAsHubSite" -HubName "HR Hub" -AuthorizedPeople "devadminuser3@metalogixsotware.onmicrosoft.com"

To associate a site with a hub site:

1.Select (from the PowerShell ISE Command Window) or enter Join-MLHubSite.

2.Enter the HubSiteUrl of the hub site with which you want to associate the site.

3.Enter the SiteUrl of the modern team or communication site you want to associate.

4.Enter either the TenantConnectionID or TenantUrl.

5.Run the cmdlet.

Example Script:

Join-MLHubSite –HubSiteUrl “https://metalogixsoftware.sharepoint.com/sites/vlad_hubSite” -TenantConnectionId 555cff48-babd-484b-b381-12132f929d35 -SiteUrl "https://metalogixsoftware.sharepoint.com/sites/IB_Demo_STS3Source_RegisterAsHubSite"

 

When a site is associated with a hub, the icon to the left of the site in the Content Matrix Console is changed to Associate Hub icon.

To change a hub association:

1.Select (from the PowerShell ISE Command Window) or enter Join-MLHubSite.

2.Enter parameters as you would if you were associating a site with a hub site, using the new HubSiteUrl.

NOTE:  If you want to remove a hub association completely, enter a value of None for the HubSiteUrl.  When the association is removed, the site theme and shared navigation of the last associated hub will be retained.

3.Run the cmdlet.

Example Script (to remove an association):

Join-MLHubSite –HubSiteUrl none -SiteUrl "https://metalogixsoftware.sharepoint.com/sites/IB_Demo_STS3Source_RegisterAsHubSite" -TenantUrl "https://metalogixsoftware-admin.sharepoint.com"

To unregister a hub site

1.Select (from the PowerShell ISE Command Window) or enter Unregister-MLHubSite.

2.Enter the SiteUrl of the hub site you want to unregister.

3.Enter either the TenantConnectionID or TenantUrl.

4.Run the cmdlet.

All sites associated with the hub site will be disassociated.  However, these sites will retain the site theme and shared navigation previously inherited from the hub.

Example Script:

Unregister-MLHubSite -TenantConnectionId 555cff48-babd-484b-b381-12132f929d35 -SiteUrl "https://metalogixsoftware.sharepoint.com/sites/IB_Demo_STS3Source_RegisterAsHubSite"

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione