Release Notes
September 2021
These release notes provide information about the latest Metalogix® Content Matrix release.
Version 9.4 of Metalogix Content Matrix introduces the following features:
·The new consolidated installer installs all editions of Content Matrix. You can then use the edition(s) for which you are licensed. In addition, a single Content Matrix PowerShell console is used for all editions. It just requires the addition of the edition-specific snap-in for each session.
·Content Matrix supports SharePoint 2019 as a source, including SharePoint 2019 database connections.
·Content Matrix supports migrations from a SharePoint 2019 communication site to SharePoint 2019 or SharePoint Online communication site and a SharePoint 2019 modern team ste to a SharePoint 2019 or SharePoint Online modern team site.
·Nintex Classic and Responsive forms can be migrated from and to SharePoint 2019.
·Multi-lingual support: Content Matrix supports migrations to SharePoint Online when the default language used on the source is different than the default language used on the target. Refer to the SharePoint Edition documentation for a list of tested languages.
·Content types are migrated at the list level, even when the parent content type is not available at site level on source
·The Managed Metadata taxonomy utility allows you to create mappings between source and target Managed Metadata term groups, term sets, and terms and (using PowerShell) import them to Job and Distributed Migration databases for use in migrations.
·You can register a modern team or communication site as a hub site and associate sites with it, either through the Content Matrix Console or using PowerShell.
·Using PowerShell, you can:
§make an active connection to SharePoint in the Content Matrix Console
§trigger a job to run in the Content Matrix Console
·For Distributed Migration:
§Global mappings are saved to the Distributed Database, so they can be shared by all agents.
§Active connections are now stored in the Distributed Database rather than in the agent's local file. This allows active connections to be shared among agents.
·You have the option to override the current version of Metalogix Extension Web Service (MEWS) and use an older installed version.
·When using a 2013 or later database connection, you can make an external connection to SharePoint, which allows files to be migrated using CSOM. This will allow large files to be migrated in chunks so that the migration of large files (over 400 MB) is less likely to fail.
·SQL CE is no longer distributed with Content Matrix. If you want to continue using it for running jobs, then SQL Server Compact 4.0 must be installed on the machine.
·SharePoint 2010 OOB and SPD 2010 style workflows are no longer supported by Microsoft for SharePoint Online and will be skipped during migration.
·Support for multi-authentication using CSOM has been added.
·In Public Folder Edition, the "Paste all exchange folder items" action now copies items in all folders, including subfolders (not just the root folder).
The following is a list of issues addressed in this release.
|
Description |
Work Item |
Case No. |
|---|---|---|
|
The issue "Content Matrix traffic is being blocked on customer network due to entry in User Agent string" has been resolved. |
497223 |
4872356-1 |
|
The issue "There is a sorting problem in SharePoint Online document libraries when there is a mix of migrated files and manually updated files" has been resolved. |
497220 |
4858383-1 |
|
The issue "The Paste Role Assignment action randomly produces Object reference not set to an instance of an object" error has been resolved. |
499415 |
4881116-1 |
|
The issue "Permissions are not getting migrated properly for the Paste List Objects > Permissions action" has been resolved. |
500646 |
4881116-1 |
|
The issue "'HasUniquePermissions' attribute value inside list properties is false for libraries having has unique permissions in source" has been resolved. |
500648 |
4881116-2 |
|
The issue "When Document Library has unique permissions with no user or group assigned to library, then permissions are migrated to target as inherited" has been resolved. |
502768 |
4903403-1 |
|
The issue "Document Library's Unique permissions are intermittently not being migrated successfully to target and produces the error Updates to system roles is not allowed" has been resolved. |
502955 |
4904475-1 |
|
The issue "When Document Library only has draft files, then the library on the target is created with inherited permissions rather than the unique permissions set up on the source" has been resolved. |
502958 |
4903402-1 |
|
The issue "Unable to migrate unique permissions at the list level from SP2010 to SPO during incremental migration" has been resolved. |
497222 |
4845567-1 |
|
Support for migration of lists with list scoped content types has been improved. |
491506 |
96344 |
|
The issue "Unable to connect to distributed Azure database if DB password contains special characters, resulting in the error Format of the initialization string does not conform to specification starting at index 138 has been resolved. |
483944 |
4822818-1 |
|
The issue "Unable to connect to SP on prem server on CM 9.3 when using certificates, which results in the error Could not create SSL/TLS secure channel" has been resolved. |
501089 |
4860101-1 |
|
The issue "Some 'Modified By' metadata on files is intermittently being replaced with the migrating user's ID" has been resolved. |
484789 |
4808869-2 |
|
The issue "Compare report is not checking major or minor versions - it should be reporting missing versioning on target files" has been resolved. |
499000 |
4885402-1 |
|
The issue "Cannot edit Site Policies on Target - results in Sorry, something went wrong. An unexpected error has occurred" has been resolved. |
482674 |
4791977-1 |
|
The issue "Error migrating list with language variations from French site to French site with the error Demand uses too many resources" has been resolved. |
499004 |
4876498-1 |
|
The issue "Migrating a library with more than 5000 folders via PowerShell, results in the error The pipeline has been stopped. |
498588 |
4875545-1 |
|
The issue "Auto-generated PowerShell scripts for site collections fail with the exception The pipeline has been stopped. The source of the copy is null, please initialize a proper source node has been resolved with the inclusion of A password is required in the message when the Remember my password option has not been enabled." |
365923 |
00161159 |
|
The issue "When Mappings are imported from an xml file, there are issues with case-sensitivity" has been resolved. All mappings are now imported from xml regardless of the case used for the xml tags. |
489742 |
4861296-1 |
|
The issue "Limit Site Collection functionality is not loading site collections - if host name of admin site and site collection are different" has been resolved. It was a case-sensitivity issue resolved by Work Item 489742. |
432828 |
4543546-1 |
|
The issue "Cannot use XML to load site collections on tenancy with 100,000 sites and custom URL. The error Url is not part of the current connection is produced." has been resolved. |
431460 |
4543546-1 |
|
The issue "Chunking on source read is not working for incremental migration of large document libraries" has been resolved. |
496959 |
4867140-1 |
|
The issue "Migrating Terms from SP2013 to SPO is generating a number of errors for TermStoreEx:Failed to read from or write to database" has been resolved. |
466396 |
4712152-1 |
|
The issue "Migrating content for a folder fails when using PowerShell and results in the exception parents to folder... with parent id... was not found; or a file stream is associated with a folder" has been resolved. |
498577 |
4876183-1 |
|
The issue "TimeLines are not getting migrated between German language sites" has been resolved. |
499351 |
4877628-1 |
|
The issue "After migrating a SPD workflow from SP2010 to SP2019, it cannot be edited in Sharepoint Designer 2019, resulting in the error Could not deserialize object. The type 'Microsoft.Office.Workflow.Actions.BuildAssignmentsXmlActivity' could not be resolved" has been resolved. |
485596 |
4833111-1 |
|
The issue "When migrating a term set, terms created by disabled or deleted user are not migrated - even if that disabled/deleted user is mapped to a valid 'active' user, which results in the error'he user name {user} can not be found" has been resolved. |
414001 |
4454933-1 |
|
The issue "Content Matrix is unable to migrate 'large' externalized StoragePoint files" has been resolved. |
487478 |
4812785-1 |
|
The issue "SharePoint Group Description is not being retrieved, resulting in an Index out of range" error has been resolved." |
491539 |
4635249-1 |
|
The spelling error in the PowerShellTransformer object "BeginTranform" has been corrected to "BeginTransform.." However, scripts created before the correction will continue to work. |
471747 |
4750567-1 |
|
Tthe issue "Incorrect columns are being written to in SPO when migrating 'To', 'CC' and 'BCC' values using Public Folder edition" has been resolved. |
485602 |
4802439-1 |
|
The issue "Incorrect permission is getting set after migration when migrating using Azure Pipeline in Public Folder edition" has been resolved. |
485603 |
-- |
The following is a list of issues, including those issues attributed to third-party products, known to exist at the time of release.
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy
