Content Matrix 9.3 Release Notes February 2021
Total Page:16
File Type:pdf, Size:1020Kb
Metalogix® Content Matrix 9.3 Release Notes February 2021 These release notes provide information about the latest Metalogix® Content Matrix release. · New Features · Resolved Issues · Known Issues · System Requirements · Product Licensing · Third Party Contributions · About Us New Features Version 9.3 of Metalogix Content Matrix introduces the following features: · Content Matrix supports Windows Server 2019 and SQL Server 2019. · The Content Matrix Console client application requires Microsoft .NET Framework 4.7.2 to run. · Support for the migration of Publishing sites to Communication sites has been added. · You can convert classic pages to modern pages from within Content Matrix using a solution provided by the PnP Community. · Support for the migration of classic web parts via the Import Pipeline has been added. (Refer to the SharePoint Edition user documentation for a complete list of supported web parts.) · An option has been added to the Connect to SharePoint dialog which allows you to connect to an Office 365 tenant that uses a custom domain with OAuth authentication. · Azure private container naming conventions have been implemented to make it easier to identify and delete containers and queues created by Content Matrix during migrations that use the Import Pipeline. · The following enhanced security practices have been implemented (which include practices that comply with Federal Information Processing Standards (FIPS)): § Users have the option to encrypt a connection to a SQL Server database. Content Matrix 1 § An option has been added to installer which will allow users to run Content Matrix without being a local Administrator on the machine where it is installed. § Content Matrix now validates certificates used when making on-premises SSL/TLS connections to SharePoint. NOTE: For self-signed certificates, this validation must be disabled in order to make the connection. Refer to the topic "Connecting with Certificates" in the applicable edition of the Content Matrix user documentation for details. § Content Matrix no longer stores the Azure Private Connection String for migrations using the Import Pipeline. Going forward, a user is required to enter the connection string for each new migration job that uses Azure private containers. § Okta authentication is supported for SharePoint on-premises connections. § GCC High Tenant connections and migrations are supported. (Refer to the SharePoint Edition user documentation for limitations.) · Migration of Nintex Responsive forms from SharePoint 2016 to SharePoint Online is now supported. · The Nintex provisioning certificate has been replaced, with a certificate that is valid from 29/09/2020 to 29/09/2023. · You can now generate a Support zip file from a Distributed Migration agent machine. · When connecting to a SharePoint database from a server machine, the database must have the same version of SharePoint as the content being migrated. · Simplified Mode has been removed from the Configure Copy Options dialog. · The option to send an email notification upon job completion has been removed. · The Metalogix Metabase ( which was formerly used in SharePoint Edition to temporarily store data used for Transformations and Distributed Migration) has been removed. Resolved Issues The following is a list of issues addressed in this release. Description Work Item Case No. The issue "Running 'Compare List' after copying that list 479273 4779924-1 results in the error Cannot run action. The target is the same as the source" has been resolved. The issue "Paste Exchange Folder to List' performance 448157 4610530-1 slows after first batch is migrated via Azure Pipeline" 479607 4788528-1 has been resolved. Content Matrix 2 Description Work Item Case No. the issue "The Document Service ID is not getting 465516 4697346-1 preserved for picture libraries on a SharePoint on premises target" has been resolved. The issue "When migrating Nintex Responsive Forms, 483644 4827537-1 the error "'d5p1' is an undeclared prefix.. occurs" has been resolved. The issue "Nintex forms fail to migrate to SPO and 470474 4735355-1 results in the error Error occurred while Saving Nintex 468924 Forms. Save Response: StatusCode: 400..." has been resolved. The issue "User Alerts are being duplicated when they 411204 4433128-1 are remigrated to SPO using the Import Pipeline" has been resolved. The issue "When migrating mapped AD Domain 464755 4708096-1 (security) groups to SPO using the Import Pipeline, the error The user does not exist or is not unique... occurs" has been resolved. The issue "When Fiddler is running, online license 478563 4769200-1 activation cannot be performed and results in the error Could not establish trust relationship for the SSL/TLS secure channel" has been resolved. The issue "System Environment variable 'PATH' keeps 416667 4439035-1 being appended to when running consecutive remote jobs through PowerShell, eventually resulting in an overflow error" has been resolved. The issue "When migrating Navigation settings to SPO 204347 ML-165794 using a Database source connection, hidden pages become visible on the target" has been resolved. The issue "MEWS connection fails with An error 460311 4684130-1 occurred while fetching child nodes for Node ... when a 4796339-1 custom list is involved" has been resolved. The issue "List level migration for a saved job results in 478173 4771068-1 the error The action does not apply in the configured 479277 Content Matrix 3 Description Work Item Case No. context. The source or target of this job may no longer exist" has been resolved. The issue "The error Object reference not set to an 478556 4785556-1 instance of an objecto occurs when migrating a Public 480282 Folder to an existing Doc library " has been resolved. Content Matrix will now migrate permissions on empty 477290 4778379-1 lists when using the Import Pipeline. 478575 By default, Content Matrix now migrates large lists in 447464 4605971-1 chunks from DB and MEWS source connections to 467454 avoid timeout issues. (This setting is configurable.) 468653 The Content Matrix installer will now notify if WSP 466480 4721955-1 deployment was not successful. You now have the option to preserve Document IDs 465926 4672426-1 when performing a Paste All List Items action. Content Matrix will now preserve column validation 411096 4424073-2 data when Preserve Item ID is selected. You can use a configurable variable to map the 408151 4419886-1 Contribute role on a SharePoint 2010 source to the Edit 4645397-1 role on an SPO target for default groups. 4647318-1 When comparing SharePoint objects, file size 474190 4765150-1 comparisons are only performed when a Database connection is used. Known Issues The following is a list of issues, including those issues attributed to third-party products, known to exist at the time of release. Content Matrix 4 All Editions PowerShell Description Issue ID · After installing all editions and running cmdlets related to 438271 User Mappings, the mappings are performed in the wrong edition. This issue occurs because after all editions are installed, the path to the snap-ins of the last edition installed are registered in registry. WORKAROUND: Change the path for the snap-ins to the edition that you are currently using in the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft \PowerShell\1\PowerShellSnapIns. Multi-factor Authentication Description Issue ID If a non-MFA (Mult-factor Authentication) user who has 389424 created SharePoint Online site-level connections is converted to an MFA user, when the connections are refreshed via the Content Matrix Console, they remain active instead of being disconnected. WORKAROUND: Relaunch Content Matrix and re-run the migration. SharePoint Edition Migration to SharePoint Online Description Issue ID · 403 error is thrown when creating Site 251718 Collection at tenant-level WORKAROUND: Keep the tenant open in the browser, restart the Console, and perform migration. · When performing a migration using a 417247 SharePoint 2013 database connection to a Content Matrix 5 Description Issue ID SharePoint Online tenant, some list/library content may become encrypted/corrupted at the target. WORKAROUND: Use a MEWS source connection. · Large document (50MB or greater) fail to 426597 migrate to SharePoint Online only when the Content Matrix Console is installed on client (non-SharePoint) machine using a SharePoint 2013 or 2016 database connection. · While migrating a site from SharePoint 2016 420126 (using an OM or CSOM connection) to SharePoint Online, an Index was out of range error is logged. · File migration fails when migration is done via 204168 the Import Pipeline and file is already present at destination when copy list or copy folder is run. WORKAROUND: Delete existing items on target, and re-migrate. Or, if the existing items have not been changed, the error can be disregarded because the rest of the migration will complete successfully. · When migrating items with versions from an 180924 Issue Tracking list the version numbers are not preserved. While all of the versions and metadata are migrated, the version numbers are slightly off. NOTE: This is due to a current bug in the Import Pipeline. · Custom Content Types on "Folders" do not get 194826 applied on the target, when migrating to SharePoint Online (SPO) using the Import Pipeline. By default all folders get tagged with the "Folder" Content Type instead. Content Matrix 6 Description Issue ID · Content Matrix is showing incorrect logs if a 417164 user is trying to migrate a list which contains corrupted attachments to a SPO site using the Import Pipeline. · When migrating a list with checked out items 439422 using the Import Pipeline, a fatal error occurs for those items because Content Matrix is attempting to migrate them as the latest version. Migrations from Publishing Site to Communication Site Description Issue ID When migrating from a Publishing Site to a 483623 Communication site, custom Community content types are not migrated to the target. WORKAROUND: Create a Communication site collection on the target and activate SharePoint Server Standard Site Collection features before migrating the content.