Content Matrix Release Notes

Metalogix® Content Matrix 8.
8
Release Notes
April 2019
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 8.8 of Metalogix Content Matrix introduces the following features:
· Metalogix Expert and Intelligent Migration are now bundled with Content Matrix.
· The new licensing model eliminates the need to install Organizer or License Check, and these
options will be disabled unless you have a Content Under Management (CUM) type license that
was issued prior to version 8.8.
· Content Matrix supports migrations involving SharePoint Online modern team sites.
· Content Matrix Public Folder Edition now supports migrations using SPO containers.
· When connecting to SharePoint, you now have the option to import a proxy from Internet
Explorer.
· You can now make a SharePoint 2013 or 2016 database connection remotely, from a non-
SharePoint machine.
· Content Matrix now supports multi-factor authentication (MFA) for SharePoint Online.
· Content Matrix supports the migration of folder structure URLs up to the SharePoint maximum
of 400 characters for SharePoint Online targets (and 260 characters for SharePoint On Premises
targets).
· The performance of migrations to SharePoint Online using the Azure Pipeline has been
improved.
Metalogix Content Matrix

1
Release Notes
Resolved Issues
The following is a list of issues addressed in version 8.8.
8.8.0.1
Content Matrix Description Work Item Case No.

Edition
SharePoint Edition The way the migration 405151 ML-168935-1

of items with
attachments is
handled has been
improved when a
MEWS connection is
used.
SharePoint Edition When migrating some 397023 00170631

list types from 00171099
SharePoint 2013 to 00171164
SharePoint Online the 00171127
migration throws the 00169492
following exception 00171304
00171294
when updating the list
properties:
Exception: Error
[Specified method is
not supported.]
SharePoint Edition InfoPath forms on a 397172 00170562

Issue Tracking list are
not migrated.
SharePoint Edition An error occurs when 399746 00171169

migrating renamed
SharePoint Designer
Workflows using
SharePoint 2013 DB
and MEWS source
connections.
SharePoint Edition Content Type 397793 00170649

workflow associations
for out-of-the-box and
custom are not being
preserved.

2
Release Notes
Edition
SharePoint Edition Warning occurs while 400767 --

migrating workflows
with duplicate names.
SharePoint Edition Web Parts are not 397748 00170580

copied when Structure 00170405
and Content Copy jobs
are run separately.
SharePoint Edition Exception "No 293117 00159095

ObjectXml" occurs 365987 00168232
while performing
migrations from
SharePoint Online
CSOM connections to
2013(OM)/(MEWS)/
(CSOM) connections
with all actions.
SharePoint Edition An exception occurs 394666 00169965

when copying 124094 00140144
Personal Sites
(MySites) to
SharePoint Online.
SharePoint Edition Read only' users on 409157 4434620-1

SPO target see
unapproved content
of documents
migrated from SPO.
SharePoint Edition Syntax Error on 303384 00147042

Calculated field with
date/time column.
SharePoint Edition Getting Value Cannot 409934 4438193-1

be null, when trying to
copy Items using
Azure Pipeline.
SharePoint Edition Connecting to 411205 4452246-1

SharePoint 2016 DB

3
Release Notes
Edition
shows duplicate lists in

the Explorer View.
Core When performing 380704 00167256

Distributed 394520 00168831
Migrations, 400674 00168998
experiencing issues 401571 00167256
with Controller 00168831
lockups and 00170234
intermittently blocked 00171200
Agents. 4399990
4400375
Core Modify use of 398176 --

SharePoint Online
CSOM "Interactive"
flag to reduce amount
of calls for better
compliance with
Microsoft guidelines.
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.
All Editions
Automatic Updates
Description Issue ID
· The error 407 Proxy Authentication required is 408256

logged when you try to download the latest
version of Content Matrix from within the
Console if:
§ Content Matrix is using a proxy that has

been imported from Internet Explorer
AND
§ the proxy server is configured as "Permit

Only" with Username/Password
authentication.

4
Release Notes
WORKAROUND: Run the "Proxy Login

Automator" script as described in the '407
Proxy Authentication' article located in the
Metalogix Content Matrix section of the Quest
Support Knowledge Base.
Multi-factor Authentication
If a non-MFA (Mult-factor Authentication) user 389424

who has 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 Modern Team Sites
If you are using Web Browser Authentication and 402033

try to connect to or load in the Console an SPO
private modern team site for which you are not a
Site Collection Administrator, the error You need
permission to access this site displays in the login
browser.
WORKAROUND:
· Make sure the account you are using to

connect is a Site Collection Administrator for
the private modern team site
OR
· Use Office 365 ADFS authentication to

connect.

5
Release Notes
SharePoint Edition
Migration to O35 Tenant
403 error is thrown when creating Site Collection 251718

at tenant-level
WORKAROUND: Keep the tenant open in

Internet Explorer, restart the Console, and
perform migration.
When performing a migration using a SharePoint 417247

2013 database connection to a SharePoint
Online tenant, some list/library content may
become encrypted/corrupted at the target.
WORKAROUND: Use a MEWS source

connection.
Locked Site Collections
A locked source site collection won’t allow a 115704

migration to complete when set to “No Access.”
NOTE: This is by design as SharePoint will not

allow access to the content.
Modern Team Sites
· The theme of a modern team site is not 397817

preserved when migrated from an "old style"
team site.
WORKAROUND: Filter out Home.aspx page

from the migration.
· If the name of a subsite is changed on the Site 414281

Options tab, the site is created on the target
modern team site with the default name.

6
Release Notes
· When data is migrated from one modern team 410789

site to another, landing page are not migrated
(i.e., the page on the target is blank).
· Unlicensed users in a SharePoint Online tenant 414364

are migrated as Office 365 Group Members
and not as Office 365 Group Owners.
Community Site Migration
· The migrating account always gets added to a 232167

Community Site Members list at SPO target
when a CSOM connection is used.
· Members of a Community Site Member list are 232176

not copied on SPO when a CSOM connection is
used.
· Map missing user Option is not updating 233345

metadata for Member list of Community Site
when mapping multiple source users to a single
target on Community Sites.
NOTE: Should multiple source users be

mapped to a single target user when migrating
a Community Site, the metadata values of that
user in the target Member List will not
concatenate the total metadata values from the
source. This will only reflect the user with the
most recent migration.
· Metadata will always get copied with Member 233278

List with Community Sites.
NOTE: When migrating ONLY the members list

from a source Community Site to the target, the
metadata for the list is set (even if the relevant
Discussion list is not migrated). This is a narrow
scenario. The workaround is to migrate the
Member List as part of a larger migration.
WORKAROUND: migrate the Member List as

part of a larger migration.

7
Release Notes
· Gifted badge values are not getting migrated 232168

properly in a community site Member list.
· Best Reply inside discussion list is not migrated 233283

on target when migrating from SharePoint 2016
Community Sites.
WORKAROUND: Migrate the Member List

as part of a larger migration.
· Duplicate replies are created inside discussion 233290

list in case of incremental migration of
Community Sites.
WORKAROUND: Delete the Discussion List

from the target and re-migrate.
· 'PostedBy’ column value is not preserved for 233554

target as SPO (AZURE) when target is a
Community Site.
WORKAROUND: Migrate using CSOM only.
Blog Site Migration
· Warning Mapped template '301' to 'CustomList' 180900

as '301' does not exist on the target is logged
when migrating blog sites with "Clear Default
features on Target" option when migrating to
SharePoint Online.
WORKAROUND: Do not change the default

selected option which is "Preserve default
Features on target"
Publishing Portal Migration
· Unable to create or paste a Public Publishing 203983

Portal template (EHS#2) as Site when migrating
to SharePoint Online.

8
Release Notes
NOTE: This template is unavailable in

SharePoint Online.
MySite Migration
· Copying MySite Social Collaboration "Note 176692

Board" Web Part is not supported in
SharePoint 2013 to SharePoint 2013
migrations.
· “Access is denied” error observed during the 179036

MySite Migration from SharePoint on premises
to SharePoint Online when trying to update a
read only content type.
NOTE: During the first 24 hours after user

creation, this error will not occur. However,
after that time, admins should enable the
'Allow Users to run Custom Scripts' setting in
SharePoint Admin Settings.
· Theme setting are not migrated to the Tenant 179060

with ‘Paste as Site Collection’ option.
SharePoint Permissions Migration
· Exception 'Value does not fall within the 178568

expected range' when replacing a single Site
Collection Administrator with another during
migration.
WORKAROUND: Add a new Site Collection

Administrator before removing the first
one.
· The exception message You cannot customize 181193

permission levels in a web site with inherited
permission level is logged.

9
Release Notes
NOTE: Content Matrix does not currently

support permission level migrations over the
CSOM or SPO/Tenant connection types.
· Permission inheritance not always preserved for 179750

item level permissions on incremental copy.
WORKAROUND: Perform a permissions-

only migration (e.g. Paste Site Objects >
Permissions) after the incremental migration
completes.
· Permissions for items in an Access Request list 178409

are duplicated when running a Paste Site > All
Site Content migration for the second time.
WORKAROUND: When running a “Paste All

Content” migration, set the “Migration
Mode” tab to use the “Custom Copy” option
with the “Preserve existing” checkbox
selected, instead of using the “Full Copy”
option.
Alert Migration
· Migration of alerts using Paste Site Objects > 181067

Alerts action are skipped when there are users
mapped for other sites.
WORKAROUND: Remove the mappings

and recreate them for the target in order to
migrate.
Content Type Migration
· When copying a list, if the configuration 182147

option "Apply new content types" is selected,
the content types that are not present on
source get hidden on the target.

10
Release Notes
When migrating custom content types from SP 274505

20072010 into SP 2013 and later, columns from
the custom content type may added to the
“Document” content type on the target.
Document Set Migration
· Document Sets are not migrated correctly when 204343

the Document Set Features is not enabled.
WORKAROUND: Activate the feature at the

target and re-migrate.
· When migrating Document Set Snapshots 284465

(versions) over a CSOM or Azure connection to
the target, there are some metadata fields that
are not preserved. These include: People and
Group fields, Lookup fields and MMD fields.
NOTE: This is a current limitation of the

SharePoint APIs.
· The migration account user is not added inside --

the Document Set Version History metadata
when there is no user mapping for the actual
user account.
NOTE: When migrating Document Set

snapshots (versions), if the user account in the
snapshot metadata has not been mapped and
the user account cannot be found, then
Content Matrix will not default to the migrating
account.
Instead Content Matrix will try to apply the
user account using the “Migrate missing AD
user” methods for SPO targets.
General List, Folder, and Item Migration
· Content Matrix Jobs get inconsistently stuck in the 245657

"copying document" action for migrating

11
Release Notes
documents and document libraries.
NOTE: This is typically caused by a corruption in

the document itself. If you try to manually
upload the same file to the new SharePoint
environment, you will also see a delay in the
upload. For Content Matrix, it looks like the
migration job is ‘stuck’ but the job is actually
waiting for SharePoint to respond before
continuing the rest of the migration.
· When trying to migrate a folder with the “Copying 171550

Folder” option, the message Unable to add folder
'This operation can only be performed on a file'
error is returned.
NOTE: This is an issue with "_files" which are

special folders in SharePoint. These types of
folders get created when you export an HTML
page using IE. IE will save all the dependent files
in a "_files" folder. If the user then uploads the
HTML page to SP, IE will also automatically pick
up the dependent files in the “_files” folder.
These folders become hidden and you cannot
access the files via the SharePoint OM calls.
· 'Copy Folder Permissions' is disabled in the List 181170

Content Options when copying/pasting a custom
SharePoint 2007 list via the Paste List Action.
WORKAROUND:
§ Run the migration using the Copy/Paste

Site action.
OR
§ Run a separate permissions copy action

after the "Paste List" action has been
completed.
· List item versions created before the approved 176588

version are missing after migration from 2010
using a Database connection to 2013 using a local
object model (OM) or client side object model
(CSOM)

12
Release Notes
WORKAROUND: Use an OM or MEWS

connection for the source.
· When migrating from SharePoint 2007 (using the 181383

MEWS connection) into SharePoint 2013/2016
(MEWS or CSOM connections) or SharePoint
Online (SPO) there are some cases where version
metadata values can be lost. This mainly seems to
occur when the items/documents are using a
custom content type and have versions.
WORKAROUND: Ensure that the custom

content type that is used on the exists on the
target before the item/document migration
has been run. (You may also need to select
the 'Apply new content type during copy'
option in the in the job configuration.)
· Custom List Forms created in SharePoint Designer 179625

are not being migrated on list or site copy when
using a database connection.

connection.
· Documents with versions that have an invalid hex 311332

character in the Title or another metadata
311682
property field are failing to migrate from a CSOM
source connection.
WORKAROUND: Use a DB or OM/MEWS

source connection.
· Document versions fail to migrate when 201631

author/editor are not mapped (DB to tenant).
NOTE: The user accounts that populate the

'Created By' and 'Modified By' fields for
document versions must be mapped to the
appropriate target SPO user accounts in order to
migrate these values correctly. If the user
accounts are not mapped to the target, the
values will not be preserved.
· Moderation status values are not preserved when 27687

migrating Video files from a SharePoint 2007

13
Release Notes
Publishing Library to SharePoint 2013 or later.
Access Request List Migration
· User Name value for the first message of an 180492

Access Request list's conversation history is
not preserved.
NOTE: This is behavior is observed only for

the first message in the conversation history.
All the other conversations after that bear
correct name which is same as that of the
source.
Access Request Items are not migrated in 179462

Subsites when running a migration using the
Paste Site Content > All Subsites option.
Task List Migration
· Unable to migrate a Task list from SharePoint 194778

Online (SPO) to SP 2013 when a child Task has
an earlier ID than the parent Task.
NOTE: While not directly restricted to SPO >

SP 2013 migration, the issue is that in the task
list there is a Parent Task that has a higher ID
then it’s child Task. This isn’t possible through
the normal SharePoint UI and is the result of
either a modification or a custom template
change.
For example, If the parent Task has an ID

value of 7 but the child Task has a ID value of
4. The parent typically needs to exist before
the child, so users should never be able to
create this scenario without direct
modification.
When a migration of Tasks in this state occurs

it returns the error message:

14
Release Notes
Exception: AddListItem - No ObjectXml [The

list item could not be inserted or updated
because invalid lookup values were found for
the following field(s) in the list: [Parent ID].
· After migrating a SP 2010 Tasks list to SP 2013, 194730

users are unable to select the Task list in the
drop down for Timeline Web Parts.
NOTE: In SharePoint 2013 there are two

types of Tasks lists, and each uses a different
Template value. They are: Tasks (template =
107) and TaskWithTimelineHierarchy
(Template = 171). In this case the SP 2010
Task list is migrated using the 107 template,
but on the target, the users is trying to use
the 171 template.
WORKAROUND: It is possible to use a

Transformer to catch and convert the
template type that is being used, so the Task
list is added as the
TaskWithTimelineHierarchy template
instead.
Survey List Migration
· The “Allow multiple responses” setting value 181216

turns from “Yes” to “No” after survey
migration.
NOTE: The “Allow Multiple Responses”

setting value for Survey Lists is not currently
supported.
Page Migration
· Migrating an out-of-the-box Master Page that 182519

has been modified to have versions from a
SP2007 source to a SP2013 or later target fails
with an error on fetching the version metadata.

15
Release Notes
WORKAROUND: Copy Master Pages with

versioning turned off.
· (SP 2007 OM/MEWS/ DB sources only) The first 171548

Wiki page fails to migrate for chained Wiki
pages and returns the error message Cannot
complete this action. Please try again.
WORKAROUND: Use the NWS connection

for migrating 2007 Wiki Libraries.
· Wiki Pages and Web Part Pages that have been 194745
customized using SharePoint Designer (SPD) are
not displaying their Page contents on the target
after migration.
NOTE: When migrating Wiki Pages, Content

Matrix use the “WikiField” sub-section to
migrate content, and for Web Part Pages the
“Web part zones” sub-section is used. Both of
these are inside the “PlaceHolderMain” section
of the page. If the “PlaceHolderMain” section,
or the “WikiField”/”Web part zones” sub-
section(s) are removed from the page during
the customization, then Content Matrix will not
be able to migrate the page contents to the
target.
· Custom master page migration is not supported 179198

for 2010/2013 DB source.
WORKAROUND: Use an OM/MEWS

connection when migrating custom master
pages.
· When using a Database source connection, Page 181072

Layouts for pages that have custom page
layouts are not preserved at destination.

connection.
· Page layout migration across versions of 203876

SharePoint is not supported, but the UI allows
for this to be selected. This results in the layouts
not being migrated.

16
Release Notes
· After migrating a Site Collection, Theme Pages 178382

like DesignGallery do not load for Site Owners
from the root.
NOTE: Starting with SharePoint 2013, the

migrating account needs access to the Master
Page Gallery to change the 'look' of a page.
· When migrating from SharePoint Online source 204252

to a SharePoint Online target and the ”Copy
Customized Form” or “Copy List Form” option is
selected,, the error 'Object reference not set to
an instance of an object on server. The object is
associated with property ModifiedBy. Is thrown.
Settings Migration
· When using the CSOM adapter to migrate to 179058

SharePoint 2013 on-premises, “Launch forms in
dialog?” settings are not migrated.
WORKAROUND: Use OM/MEWS as the

target adapter.
· Theme setting are not migrated to the Tenant 179060

with ‘Paste as Site Collection’ option.
Managed Metadata Migration
· Empty MMD Field value in versioned list 124696

migrates as non-empty value for all open xml file
formats.
WORKAROUND: This is due to property

promotion behavior in SharePoint for
MMD columns. This can be bypassed by
checking the option “Disable SharePoint
Document Parsing” under “List Content
Options.”

17
Release Notes
· Migrations return different results for document 271320

migrations with the Managed Metadata and
GUID Mapping options enabled, when migrating
using the CSOM adapter or the Azure Pipeline
options on the target connection.
NOTE: When migrating Managed Metadata

(MMD) over a CSOM connection, SharePoint
will return information to Content Matrix if the
terms are valid or not. When migrating MMD
over Azure, SharePoint doesn’t have a way to
return information on if the terms are valid or
not to the container.
This means that the logging and end results of

migrating MMD over Azure or CSOM will look
slightly different, and can sometimes result in
the terms migrated over Azure having a red line
under them, indicating that the terms may not
be valid.
Column Migration
· When migrating a SP 2010 list that contains a 307507

BCS column an “Error: AddListItem – No
ObjectXml” message is returned.
NOTE: This is cause by Content Matrix trying

to fetch the data from a Database table, but a
different column is set as the “Identifier”
column.
WORKAROUND: Please see the Support

Knowledge Base Article.
· When performing the operation "Custom 180869

Copy"-> Preserve Lists -> Update Fields, while
migrating BDC fields, the error An error
occurred. Administrators, see the server log for
more information is logged.
WORKAROUND: Delete the target list and

re-migrate it.

18
Release Notes
· When web parts are added to a page after 281741

column validation settings have been activated,
the web parts conflict with the validation
settings and the error is thrown.
· Lookup column referencing the same library in

which it is present does not migrate. (Work Item
182112).
NOTE: This is only applicable for Document

Libraries and is not supported in that instance.
InfoPath Migration
· When copying a site that has browser enabled 204356

InfoPath forms there is an exception migrating
to SharePoint Online.
· Authorship Metadata is not preserved when 256779

migrating Customized Info Path forms.
Because the relevant files live at the root, they

will always be created with the currently logged
in user (the connecting user account in Content
Matrix) and they cannot be updated. This is a
SharePoint limitation.
· Migrating InfoPath lists that use UDCX (Data 310825

Connection Files), the link correction is not
310826
properly updating the link inside the data
connection file.
WORKAROUND: After migration, manually

open the Data Connection File and enter the
correct web URL and list ID for the
list/library that the InfoPath is referencing.
Workflow Migration
· Renamed list and web workflows fail to migrate when 404724

workflows are renamed with the Console open.

19
Release Notes
WORKAROUND: Re-launch the Console after

renaming the workflows.
· Out-of-box 2007 workflow association cannot be opened 99326

after migration in SP 210 or 2013.
WORKAROUND: Activate 2007 workflows on the

target as described in the following Microsoft
technet article:
http://blogs.technet.com/b/vinitt/archive/2
011/02/23/moss-2007-workflows-no longer-
available-visible-when-weupgrade-from-2007-to-
2010-databaseattach-method.aspx
· When migrating a SP 2013 SPD workflow from a CSOM 283742

source connection to a Site Collection that is set to “Read
273643
Only”, the migration fails.
WORKAROUNDS:
§ Switch connection types on the source and use the

Local (OM) or Remote (MEWS).
OR
§ Manually turn off the “Read Only” setting on the

source.
· The Workflow status column for SPD reusable and SPD 204376
globally reusable workflows with versions and workflow
instances is changed to name of first version of SPD
workflow after migration.
· SPD Global Reusable workflow migration not supported 204377

with Copy Site > Paste All Site Content,
WORKAROUND: Use the “Paste as Site Collection”

action, which is encouraged for these types of
migrations.
· An exception is thrown when performing copy site -> 252485

paste as subsite/all site content second time and Nintex
app is present on target site.
WORKAROUND: Content Matrix cannot currently

delete a SharePoint site while it contains any
SharePoint App/Add-In.

20
Release Notes
· Nintex workflows having the Calculate a Date activity with 253468

the option “Use date when action is executed” do not
migrate from SharePoint 2007 to SharePoint Online.
· Nintex workflows containing custom variables in the 254006

“Pause For” activity do not have the variables migrated to
SharePoint Online.
NOTE: This is currently not supported and the variables

are being tagged as comments instead.
· The error 407 Proxy Authentication required is logged 408256

when you try to migrate Nintex workflows if:
§ Content Matrix is using a proxy that has been

imported from Internet Explorer
AND
§ the proxy server is configured as "Permit Only" with

Username/Password authentication.
WORKAROUND: Run the "Proxy Login Automator" script

as described in the '407 Proxy Authentication' article
located in the Metalogix Content Matrix section of the
Quest Support Knowledge Base.
Web Part Migration
· Connected Web parts are lost after migrating 102229

to O365. (Work Item )
WORKAROUND: This is due to current
limitations of Microsoft's Client Side Object
Model API. After migration, connections
between web parts should be manually re-
created on the O365 site.
· Due to a bug in SharePoint 2010, the Calendar 178682

web part (with summary view) is not migrated to
the destination from SP2010 DB to SP2013 OM.
WORKAROUND:
1. On the source, browse to the page with

the affected web part.

21
Release Notes
2. Confirm that you are not editing the page
3. Click the arrow in the top-right of the web

part
4. Click Edit Web Part
5. Change the view to the desired one.
6. Click OK
7. Re-run the migration.
· Web parts in a wiki page are not migrated when 204321

content approval is in-place at the target.
WORKAROUND: Disable content approval of

the wiki pages library before migration.
· When migrating web parts from SP 2010 to SPO,

any contents/settings inside a “Wiki Content web
part” are not preserved. (Work Item 258370)
NOTE: This issue is specifically for using

NWS/CSOM as a source or target adapter. The
NWS/CSOM APIs do not have access to fetch or
write these values, and as a result Content
Matrix cannot set them (or if using NWS/CSOM
on the source, it can’t read the values).
WORKAROUND: To resolve the issue of

reading the values from a source, users can
use the DB, OM, or MEWS adapters instead.
For the target, the OM or MEWS adapters are
recommended. In the case of migrating to a
SharePoint Online target (SPO) there is no
current workaround.
· When migrating web parts from a SP 2010 source 258370

using a NWS connection to SPO using a CSOM
connection, any contents/settings inside a “Wiki
Content web part” are not preserved.
NOTE: The NWS/CSOM APIs do not have access

to fetch or write these values, and as a result
Content Matrix cannot set them (or if using
NWS/CSOM on the source, it can’t read the
values).

22
Release Notes
· Web parts not migrated when added inside Wiki 180285

page having draft with minor version enabled
from SP 2010 (MEWS) to 20103 (CSOM).
NOTE: This issue is only encountered when

using the Paste Site Content > All Site Content
option. The issue does not occur when migrating
and pasting as a Site Collection.
· Some XSLTListView Web parts do not migrate 203857

from SharePoint 2010 to SharePoint 2013 when
using the Database Adapter for the source
connection.
WORKAROUND: Use 2010 MEWS or OM

source and the XSLLISTVIEWWEBPARTS will
migrate successfully. Continue other aspects
of migration using the database adapter if
needed.
· When migrating “list view” web parts from SP 194742

2007, they are added as “list view” web parts in
194814
SP 2013 instead of converting them to “XSLT list
view” web parts. In addition, there are also some
web part settings on the source that that use
different default values on the target, and
Content Matrix does not currently change these
values (for example, the Base ID value).
WORKAROUND: There is a configuration

setting in the Content Matrix
“ApplicationSettings.xml” file that can be
modified to convert standard “list view” web
parts into “XSLT list view” web parts. This
must be used in conjunction with a
Transformer to correctly set the other web
part settings (like the Base ID value). A KB
article on this WORKAROUND can be found on
the Support Knowledge Base portal.
· Due to some SharePoint API limitations, when 264911

migrating to a SP 2013/SP 2016/SPO target, the
web part ‘Miscellaneous’ option for ‘Display
Search Box’ is being enabled.
Azure Pipeline Migration

23
Release Notes
· File migration fails when migration is done via 204168

Azure SPO Pipeline and file is already present at
destination when copy list or copy folder is
executed.
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 Azure

Pipeline.
· Custom Content Types on "Folders" do not get 194826

applied on the target, when migrating to
SharePoint Online (SPO) using the Azure
Pipeline. By default all folders get tagged with
the "Folder" Content Type instead.
· The error 407 Proxy Authentication required is 408256

logged when you try to migrate using the Azure
Pipeline if:
§ Content Matrix is using a proxy that has

been imported from Internet Explorer
AND
§ the proxy server is configured as "Permit

Only" with Username/Password
authentication.

Metalogix Content Matrix section of the Quest
Support Knowledge Base.
Content Matrix is showing incorrect logs if a user 417164

is trying to migrate a list which contains corrupted

24
Release Notes
attachments to a SPO site using Azure.
Migrations from SharePoint Online to SharePoint On Premises
Migrations from SharePoint Online using a 408023

CSOM connection to SharePoint On Premises
failing with "Unable to obtain SharePoint
Online authentication cookie" message.
Incremental Migration
· Custom folder content type Metadata is not 181984

migrated during incremental migration from
SharePoint 2010 to a target that uses a CSOM
connection.
· Blog Sites cannot support incremental copies to 176629

Office 365 /SharePoint Online.
NOTE: This limitation exists because Blog sites

automatically start with a blog item already
created, and that blog item ID cannot be
changed by Content Matrix.
WORKAROUND: Copy blog sites at the end of

the full migration as follows:
a) Perform an initial Copy with Blog sites

filtered out: On the Configuration Options
> Filter Options tab, Apply filter on Lists
and Libraries using the filter
WebTemplateID NotEquals 9.”
b) Re-run the migration on the same

object(s) using the filter WebTemplateID
Equals 9.”
Distributed and Self-Service Migration

25
Release Notes
· If a Self-Service Workstation was previously a 352855

full install of Content Matrix, old connection will
still be visible in the Explorer View unless the
old ‘ActiveConnections.xml’ file is deleted.
WORKAROUND: After closing the

Workstation console, manually navigate to
the ‘ActiveConnections.xml’ file (located at:
C:
\Users\<USER>\AppData\Roaming\Metalogi
x\Content Matrix Console - SharePoint
Edition) and delete the file. Then restart the
Workstation
· If a migration is performed from SharePoint On 409813

Premises to SharePoint Online and a proxy is
configured using both IP address and
username/password, the message Unable to
obtain SharePoint Online authentication cookie is
logged.

Metalogix Content Matrix section of the
Quest Support Knowledge Base.
PowerShell
· When running a PowerShell script created in a 220248

release prior to 8.1, an error is thrown if you try
to connect to the Jobs or Distributed database
using SQL authentication.
WORKAROUND: Re-create the PowerShell

script using a later version of Content
Matrix.
· An error is thrown when running Content Type 181226

migrations using PowerShell 2.0 when mapping
term stores - 2010 OM to 2013 MEWS or SPO.
WORKAROUND: Install PowerShell 4.0

26
Release Notes
· When using a Content Matrix version that is 258931

earlier tha 8.3, PowerShell scripts that have the
“Azure” options set to “False” will be set to
“True” even for On-Premises migrations.
WORKAROUND: Re-create the PowerShell

script using a later version of Content Matrix.
Blogs and Wikis Edition

Special Characters
· Page title prefix gets omitted when the page 181782

title starts with a special character.
NOTE: The special character only is omitted,

and is a character that would be illegal in
SharePoint regardless. This is by design to
ensure proper SharePoint naming standards.
Resized Images
· Resized images are not rendered on page at 194862

target for Blogs and Wiki >> SP 2010
publishing site
· Metadata of Resized images (Authorship 194864

Information, Modified by, Modified Date, and
Page Name) are not preserved when
migrating from Blogs & Wiki Edition for SP
2010/2013/SPO using OM/CSOM
MediaWiki Source Connection
· When connecting to a MediaWiki 300492

environment, Redirect pages will not be
displayed.

27
Release Notes
NOTE: When connected to MediaWiki

environments, Content Matrix does not
populate redirect pages in the ‘Explorer View’
tab. This is because they are not ‘content’
pages and have no equivalent pages/concepts
in SharePoint.
eRoom Edition
Deleted Items Report
· Deleted items report is not generated when you 181954

connect a web application from a URL that is
not the root to a site collection.
WORKAROUND: Reconnect using the root

site collection URL.
Custom Field Value Migration
· Custom fields values using the Document 203891

Content Type are not migrated at target after
mapping the column.
WORKAROUND: Choose a different Content

Type.
eRoom Permissions Migration
· When migrating eRoom permissions and groups 181083

user that are present in custom groups are
added in the SharePoint custom groups, as well
as inside SharePoint Out of Box (OOB) groups
instead of just getting added inside the Custom
group
· Additional permissions are given directly to 182312

users that belong to custom or OOB groups

28
Release Notes
(eRoom > SP 2010/2013)
· Permissions to users are given both via their 182340

respective group and directly, resulting in
redundant/duplicated permissions for users on
the SharePoint target.
· User and Group permissions are appended 182341

instead of overwritten if they already have
permissions on the target and the 'Use Existing
content' collision option is selected.
WORKAROUND: Use another collision

option for migration; either:
? Overwrite existing content with same

name.
OR
? Rename current content with unique

name.
FileShare Edition
Imported Content
· In rare cases, updated values are not reflected 170959

properly in the “Items View” Grid after an
import from Excel/CSV.
WORKAROUND: Restart the console, and

the updated values will be displayed.
Multi-Threading
· Migration of large number of Folders as Sites 171324

with large multi-threading settings causes
"Duplicate key value found" exceptions.

29
Release Notes
WORKAROUND: In the Settings Menu, lower

the Resource Utilization Settings towards
the Efficiency side and try again. This will
reduce the number of threads, and
decrease the probability of causing
SharePoint to be overwhelmed by the
number of Site creation requests.
Source Column Migration
· When adding a lookup column to a File Folder 171527

in Content Matrix File Share Edition, if that
lookup column has a very large number of
options, not all of them will populate, and some
may need to be typed in manually.
WORKAROUND: Lookup columns with more

than 10 entries are not recommended for
SharePoint in general. Managed Metadata
should be used in those instances instead.
· BCS values are not populated in items view 182312

when target External Content Type contains
filter on Read Operation and DB column used in
display property is of type other than string.
WORKAROUND: This works when the

column type is String.
FileShare Permissions Migration
· Permission mappings are not persisted if you 182248

attempt to run a job a second time.
WORKAROUND: Go back into the settings

for the previously run migration (i.e. the
second attempt) and manually remap the
permissions mapping again before
continuing.

30
Release Notes
Public Folder Edition
Exchange Server - MAPI and/or Redemption Connector
Exception "A text field contains invalid data" is 397853

thrown in Public Folder Edition while migrating
some data using MAPI and Redemption
connectors
Migration Using SPO Containers
After re-running Paste Exchange Folder job, 408273

Items are duplicated on target when job is
configured selecting overwrite and unchecking
Use SPO Container O365 Upload option.
Website Edition
Installation
· After installing Website Edition v. 8.2.0.2 from 303787

an MSI file, the console crashes on startup with
the error: An error has caused application to exit
abnormally.
WORKAROUND: Since Admin permissions

are required to register all of the DLLs
correctly, when installing Content Matrix
from an MSI file, make sure that the
installation is run with ‘Administrator’
credentials (using ‘run as Admin’ or
installing with an Admin command line,
etc.).
Connecting to SharePoint

31
Release Notes
· The Website Edition requires the use of 179191

MEWS rather than Local Object Model for
connections to on-premises SharePoint
farms.
Content View
· The Website Edition requires the use of 179191

MEWS rather than Local Object Model for
connections to on-premises SharePoint
farms.
Organizer
User Interface
· Organizer Filtering Add Expression and Group 177338

button images are not showing in IE 9.
WORKAROUND: Try a different browser, such

as IE 10.0 or greater or Chrome.
· The required field indicator (red asterisk *) is not

178091
displayed in the copy/move dialog for site
columns set as required which are added to a list
content type.
WORKAROUND:
1. Temporarily set the site column properties

from Required to 'Optional' 2
2. Perform the Organizer copy/move action

again. This issue will be resolved in future
versions of Content Matrix.
· The required field indicator (red asterisk *) is not 178091

displayed in the copy/move dialog for site
columns set as required which are added to a list
content type. ()
WORKAROUND:

32
Release Notes
1. Temporarily set the site column properties

from Required to 'Optional'.
2. Perform the Organizer copy/move action

again. This issue will be resolved in future
versions of Content Matrix.
Application Error Messages
· Editing a "User" field and then clicking the Undo 177973

button when using Internet Explorer 11 causes
an unexpected error on SharePoint.
WORKAROUNDS:
? Close the Organizer dialog and complete

the operation with the correct value in the
User field.
? Use Chrome or an earlier version of IE.
StoragePoint
· Uninstalling Organizer can inadvertently break 177382

StoragePoint Central Administration links.
WORKAROUND: Re-run the StoragePoint

Configuration Wizard, and that should bring
everything back to normal.
Reorganize
· Extra site is populated in Reorganize with the 201990

URL of “SiteMaster<GUID>”
NOTE: This is due to the new feature in

SharePoint 2016 for Fast Site Creation. All Site
Collection templates will appear this way.
Column Copy

33
Release Notes
· Applying Metadata from the Content Matrix 83462

Ribbon on a list item that uses BCS external
content fails.
· Incompatible columns with taxonomy columns 170719

are incorrectly displayed during a copy/move
operation.
WORKAROUND: Select the compatible

column with taxonomy fields such as string
or choice.
· Rich Media data for publishing’ column can’t be 171526

edited using Organizer.
· File Applying Metadata from the Content Matrix 83462

Ribbon on a list item that uses BCS external
content fails.
· When copying items with the Organizer Ribbon, 181259

and the items belong to a custom content type
that have a numeric column with a name
suffixed with a number (e.g. 'No1' or 'Num1'),
the columns with the numeric suffix (e.g. 'No1'
and 'Num1') are not migrated. This issue is also
observed for calculated columns when its name
has a number suffix.
WORKAROUND: Remove the suffix

numbering from the column name and run
the copy again.
File Copy
· If you attempt to move a file that is larger than 171572

the supported file size in the destination web
application then the file is copied but remains
checked out on the destination and it is not
removed from the source.
WORKAROUND: If you are moving a file and

the file still remains in the source, then
manually remove the file from the source.

34
Release Notes
Organizer/License Check
Online Activation
· Unable to use the Online license activation 337255

when the Solution is installed in SharePoint
337414
2013 Server/WFE.
NOTE: This issue only occurs in SharePoint 2013

environments, when either the Organizer or
License Check solutions are installed, and the
environment is specifically configured to use TLS
1.1 or 1.2. While Content Matrix v.8.6.0.1 has
been upgraded to use .NET 4.6 to resolve this
issue, the Organizer and License Check solutions
will still operate in the same runtime as the
SharePoint environment. For SharePoint 2013,
that means the solutions will use .NET 4.5. Since
.NET 4.5 does not handle the communication
between versions of TLS 1.1 and up natively,
both Organizer and License Check will run into
issues trying to run the Online license Activation
back to the Metalogix Servers.
WORKAROUND: Activate the license by

using the Offline License Check option.
System Requirements
The following tables describe the hardware, software, and access requirements for Metalogix
Content Matrix Console. If our requirements are equivalent to, or less restrictive than a SharePoint
requirement, it will not be described here.
Hardware Requirements
Component Requirement
Processor Under normal circumstances, the Metalogix Content Matrix processor

requirements are the same as SharePoint.

35
Release Notes
Memory 1 GB of free RAM, plus double the size of the largest file being migrated in free
RAM.
Disk Space The amount of available hard disk space will change depending on what
components of the Metalogix Content Matrix Console are installed.
Each component ranges in hard disk space from 20MB to 50MB.
Display 1024 x 768 screen resolution.
Software Requirements
Operating System Any of:
· Windows Server 2003

· Windows Server 2008 R2
· Windows XP Professional
· Windows Vista
· Windows 7
· Windows 8 and 8.1
· Windows 10
All of these Operating Systems are supported on both 32-bit and 64-bit
systems.
SharePoint Target Any of:

Environment
· Windows SharePoint Services (WSS) 3.0
· Microsoft Office SharePoint Server (MOSS) 2007
· SharePoint Server 2010
NOTE: If users are creating Publishing Sites in the SharePoint 2010
environment they are migrating into, it is recommended that the
Office 2010 SP1 Windows update is installed on the same system that

36
Release Notes
the Metalogix Content Matrix Console client application is installed

on.
· SharePoint 2013
· SharePoint 2016
· Microsoft Office 365 – Standard and Dedicated versions.
Database Any of:
· SQL Server 2000

· SQL Server 2005
· SQL Server 2008
· SQL Server 2008 R2
· SQL Server 2012
· SQL Server 2014
· SQL Server 2016
As well as :
· SQL CE 4.0 SP1
Windows PowerShell Metalogix Content Matrix Console has the ability to run migrations using
a pre-configured PowerShell console, provided that PowerShell Version
3.0 or later is installed prior to Metalogix Content Matrix.
Web Browser Microsoft Internet Explorer 6.x or later (8.x or higher is required if
browser authentication is being used).
.NET Framework Microsoft .NET Framework 4.6 or later.

Since this .NET requirement applies to the machine on which Metalogix
Content Matrix is installed, Metalogix Content Matrix cannot make a
local Object Model (OM) connection on a SharePoint 2007 or 2010
environment, because SharePoint 2007 and 2010 require an earlier
version of the .NET Framework (v.3.5), which prohibits Metalogix
Content Matrix from completing the connection. Because of this, any
migration ‘jobs’ configured to connect to SharePoint 2007 and 2010
environments using a Local OM connection type will cease to work, and
these jobs will need to be recreated for use over a different adapter type
such as MEWS or DB.

37
Release Notes
Access Requirements
All of the installation and migration permissions/access requirements can change depending
where the Metalogix Content Matrix Console client application is installed. The below
requirements are the standard set of requirements if you are installing Metalogix Content Matrix
on a non-SharePoint machine (i.e. installing on a machine that is not running SharePoint, but has
access to the source and target environments).
If you are installing the Metalogix Content Matrix client application directly on a target SharePoint
Server or Web Front End (WFE), then you would need the same permissions that are required for
installing the Metalogix Extensions Web Service (MEWS).
Installing User The user account that is installing the client only needs permissions to
install a client application on the target/installation machine. This is
because the Metalogix Content Matrix Installer will attempt to elevate
permissions as part of the installation process. However, any user
account that is going to be running the Metalogix Content Matrix Console
application will require Administrator permission.
Application Pool If connecting to a remote, on-premises instance of SharePoint the

Accounts Metalogix Extensions Web Service can be used (for SharePoint 2007 or
later). This is a SharePoint solution file that is installed and will use the
Application pool user account.
Server Access The installing user, and any user launching Metalogix Content Matrix
Console, will require Administrator permissions on the local machine.
SharePoint Access The migrating user requires the following permissions (provided that the
Extensions Web Service is installed on the SharePoint target).
· Site Collection Administrator on the target SharePoint environment.

· Farm Administrator on the target SharePoint environment.
· Permissions to access all of the content that is being migrated.
Firewalls Access to any ports that allow access to the SharePoint Web Application.
Activation A valid license key is required.
Metalogix Metalogix Extensions Web Service is an additional component that can be

Extensions Web installed which can be installed on remote SharePoint instances and
Services (MEWS) provides additional permission/access.

38
Release Notes
See Installing and Configuring the Metalogix Content Matrix SharePoint

WSPs for details.
Product Licensing
When installing the Metalogix Content Matrix Console for the first time or when launching the
Console after your license has expired, you will be prompted to input an Activation License Key. If
you are trying to install a new license key over an existing key, choose Help > Update License from
the Metalogix Content Matrix Console ribbon.
Third Party Contributions

This product contains the following third-party components. For more third-party license
information, see https://www.quest.com/legal/third-party-licenses.aspx.
Component License or Acknowledgement
AeroWizard 1.2.6 Use of this component is governed by the MIT 1.0

license.
Copyright © 2013 David Hall
CertEnroll 1.0.0.0 Use of this component is governed by the Microsoft

Windows SDK license.
Portions utilize Microsoft Windows Media

Technologies.
Copyright © 2006 Microsoft Corporation. All Rights

Reserved.
CommandLineParser 1.9.71 Use of this component is governed by the MIT license.
Copyright © 2005-2012 Giacomo Stelluti Scala
DevExpress WinForms 16.1.4 Use of this component is governed by the following

licenses:
· jQuery JavaScript Library (Open Source - MIT

License)
Copyright © jQuery Foundation and other
contributors
· jQueryUI JavaScript Library (Open Source - MIT

License)

39
Release Notes
Copyright © jQuery Foundation and other

contributors
· Knockout JavaScript Library (Open Source - MIT

License)
Copyright @
- http://knockoutjs.com/
- https://opensource.org/licenses/mit-license.php.
· Globalize JavaScript Library (Open Source - MIT

License)
Copyright @ Software Freedom Conservancy, Inc.
· Ace (Ajax.org Cloud9 Editor) (Open Source - BSD

License)
Copyright @ 2010, Ajax.org B.V.
· JS Beautifier (Open Source - MIT License)

Copyright @ 2007-2013 Einar Lielmanis and
contributors
· CodeMirror (Open Source - MIT License)

Copyright @ 2015 Marijn Haverbeke
dsofile.dll 2.1.0.0 Portions utilize Microsoft Windows Media

Technologies.

Reserved.
Interop.CERTENROLLLib 1.0.0.0 Portions utilize Microsoft Windows Media

Technologies.

Reserved.
Interop.MAPIConnectorLib 1.0.0.0 Portions utilize Microsoft Windows Media

Technologies.

Reserved.
Interop.Redemption 5.3.0.0 Portions utilize Microsoft Windows Media

Technologies.

Reserved.

40
Release Notes
Json.NET 9.0.1 Use of this component is governed by the MIT 1.0

license.
Copyright © 2017 Newtonsoft
MathNet.Numerics 2.6.1.30 Use of this component is governed by the MIT 1.0

license.
Copyright © 2002-2018 Math.NET
Microsoft SQL CE 4.0.8876.1 Distributable Code is not to be run on a non-Windows

platform.
Microsoft.Azure.KeyVault.Core 3.0.0.1 Use of this component is governed by theMIT license.
Copyright © 2018 Microsoft
Microsoft.Identiy.Client 1.1.2.8 Copyright © 2018 Microsoft Corporation. All rights

reserved.
Microsoft.IdentityModel Portions utilize Microsoft Windows Media

6.3.96000.16384 Technologies.

Reserved.
Microsoft ODataLib for OData 5.6.3 Use of this component is governed by the MIT 1.0
license.
Copyright © 2018 Microsoft. All rights reserved.
org.in2bits.MyXls 0.6.0.0 Use of this component is governed by the MIT 1.0

license.
Copyright © 2007 Tim Erickson
stdole.dll 7.00.7466 Portions utilize Microsoft Windows Media

Technologies.

Reserved.
System.Numerics 4.0.30319.17929 Use of this component is governed by the MIT 1.0

license.
Copyright .NET Foundation and Contributors. All

rights reserved.

41
Release Notes
Task Scheduler Editor 2.0 Use of this component is governed by the MIT 1.0
license.
Copyright © 2003-2010 David Hall
TaskScheduler 2.0 Use of this component is governed by the MIT license.
Copyright © 2003-2010 David Hall
Time Span 2.0.2.0 Use of this component is governed by the BSD 3-

clause license.
Copyright © 2009, dahall. All rights reserved.

42
Release Notes
Third Party License Information
The following third-party license applies to:
· Dotfuscator 2.3
· Fluent Assertion 3.0.107
· Group Controls 1.3.8
· Microsoft.VisualStudio.QualityTools.UnitTestFramework 11.0.61030.0
· Microsoft.WindowsAzure.Storage 4.3.0.0
For more third-party license information, see https://www.quest.com/legal/third-

partylicenses.aspx.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction, and distribution as defined
by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is
granting the License.
"Legal Entity" shall mean the union of the acting entity and all other entities that control, are
controlled by, or are under common control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the direction or management of such
entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this
License.
"Source" form shall mean the preferred form for making modifications, including but not limited to
software source code, documentation source, and configuration files.
"Object" form shall mean any form resulting from mechanical transformation or translation of a
Source form, including but not limited to compiled object code, generated documentation, and
conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or Object form, made available
under the License, as indicated by a copyright notice that is included in or attached to the work (an
example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or
derived from) the Work and for which the editorial revisions, annotations, elaborations, or other
modifications represent, as a whole, an original work of authorship. For the purposes of this

43
Release Notes
License, Derivative Works shall not include works that remain separable from, or merely link (or
bind by name) to the interfaces of the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including the original version of the Work and
any modifications or additions to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal
Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition,
"submitted" means any form of electronic, verbal, or written communication sent to the Licensor
or its representatives, including but not limited to communication on electronic mailing lists, source
code control systems, and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but excluding communication that
is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a
Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of
whom a Contribution has been received by Licensor and subsequently incorporated within the
Work.
2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor
hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable.
copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform,
sublicense, and distribute the Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor
hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made, use, offer to sell, sell, import,
and otherwise transfer the Work, where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination
of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit)
alleging that the Work or a Contribution incorporated within the Work constitutes direct or
contributory patent infringement, then any patent licenses granted to You under this License for
that Work shall terminate as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works
thereof in any medium, with or without modifications, and in Source or Object form, provided that
You meet the following conditions:
(a) You must give any other recipients of the Work or Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices stating that You changed the files;
and
(c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright,
patent, trademark, and attribution notices from the Source form of the Work, excluding those
notices that do not pertain to any part of the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works
that You distribute must include a readable copy of the attribution notices contained within such
NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at
least one of the following places: within a NOTICE text file distributed as part of the Derivative
Works; within the Source form or documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and wherever such third-party notices
normally appear. The contents of the NOTICE file are for informational purposes only and do not

44
Release Notes
modify the License. You may add Your own attribution notices within Derivative Works that You
distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such
additional attribution notices cannot be construed as modifying the License.
You may add Your own copyright statement to Your modifications and may provide additional or
different license terms and conditions for use, reproduction, or distribution of Your modifications,
or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of
the Work otherwise complies with the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution

intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms
and conditions of this License, without any additional terms or conditions. Notwithstanding the
above, nothing herein shall supersede or modify the terms of any separate license agreement you
may have executed with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade names, trademarks, service
marks, or product names of the Licensor, except as required for reasonable and customary use in
describing the origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor

provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including,
without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY,
or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any risks associated with Your
exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory, whether in tort (including
negligence), contract, or otherwise, unless required by applicable law (such as deliberate and
grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages,
including any direct, indirect, special, incidental, or consequential damages of any character arising
as a result of this License or out of the use or inability to use the Work (including but not limited to
damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other
commercial damages or losses), even if such Contributor has been advised of the possibility of
such damages.
9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works
thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty,
indemnity, or other liability obligations and/or rights consistent with this License. However, in
accepting such obligations, You may act only on Your own behalf and on Your sole responsibility,
not on behalf of any other Contributor, and only if You agree to indemnify,defend, and hold each
Contributor harmless for any liabilityincurred by, or claims asserted against, such Contributor by
reason of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS

45
Release Notes
About Us
We are more than just a name

We are on a quest to make your information technology work harder for you. That is why we build
community-driven software solutions that help you spend less time on IT administration and more
time on business innovation. We help you modernize your data center, get you to the cloud
quicker and provide the expertise, security and accessibility you need to grow your data-driven
business. Combined with Quest’s invitation to the global community to be a part of its innovation,
and our firm commitment to ensuring customer satisfaction, we continue to deliver solutions that
have a real impact on our customers today and leave a legacy we are proud of. We are challenging
the status quo by transforming into a new software company. And as your partner, we work
tirelessly to make sure your information technology is designed for you and by you. This is our
mission, and we are in this together. Welcome to a new Quest. You are invited to Join the
Innovation™.
Our brand, our vision. Together.

Our logo reflects our story: innovation, community and support. An important part of this story
begins with the letter Q. It is a perfect circle, representing our commitment to technological
precision and strength. The space in the Q itself symbolizes our need to add the missing piece —
you — to the community, to the new Quest.
Contacting Quest
For sales or other inquiries, visit www.quest.com/contact.
Technical Support Resources

Technical support is available to Quest customers with a valid maintenance contract and
customers who have trial versions. You can access the Quest Support Portal at
https://support.quest.com
The Support Portal provides self-help tools you can use to solve problems quickly and
independently, 24 hours a day, 365 days a year. The Support Portal enables you to:
· Submit and manage a Service Request
· View Knowledge Base articles
· Sign up for product notifications
· Download software and technical documentation
· View how-to-videos
· Engage in community discussions
· Chat with support engineers online

46
Release Notes
· View services to assist you with your product

47
Release Notes
Copyright
© 2019 Quest Software Inc. ALL RIGHTS RESERVED.
This guide contains proprietary information protected by copyright. The software described in this guide is
furnished under a software license or nondisclosure agreement. This software may be used or copied only in
accordance with the terms of the applicable agreement. No part of this guide may be reproduced or
transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for
any purpose other than the purchaser’s personal use without the written permission of Quest Software Inc.
The information in this document is provided in connection with Quest Software products. No license, express
or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in
connection with the sale of Quest Software products. EXCEPT AS SET FORTH IN THE TERMS AND CONDITIONS
AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST SOFTWARE ASSUMES NO LIABILITY
WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS
PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST SOFTWARE BE LIABLE FOR ANY
DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT
LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING
OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST SOFTWARE HAS BEEN ADVISED OF
THE POSSIBILITY OF SUCH DAMAGES. Quest Software makes no representations or warranties with respect to
the accuracy or completeness of the contents of this document and reserves the right to make changes to
specifications and product descriptions at any time without notice. Quest Software does not make any
commitment to update the information contained in this document.
If you have any questions regarding your potential use of this material, contact:
Quest Software Inc.

Attn: LEGAL Dept.
4 Polaris Way
Aliso Viejo, CA 92656
Refer to our Web site (https://www.quest.com) for regional and international office information.
Patents
Quest Software is proud of our advanced technology. Patents and pending patents may apply to this product.
For the most current information about applicable patents for this product, please visit our website at
https://www.quest.com/legal.
Trademarks
Quest, the Quest logo, and Metalogix are trademarks and registered trademarks of Quest Software Inc. and its
affiliates. For a complete list of Quest marks, visit https://www.quest.com/legal/trademark-information.aspx. All
other trademarks and registered trademarks are property of their respective owners.Metalogix® Content
Matrix
Updated April 2019

Version 8.8

48
Release Notes

Content Matrix Release Notes

Uploaded by

Copyright:

Available Formats

Content Matrix Release Notes

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Content Matrix Release Notes

Uploaded by

Copyright:

Available Formats

Metalogix® Content Matrix 8.

· Third Party Contributions

Metalogix Content Matrix

Content Matrix Description Work Item Case No.

SharePoint Edition The way the migration 405151 ML-168935-1

SharePoint Edition When migrating some 397023 00170631

SharePoint Edition InfoPath forms on a 397172 00170562

SharePoint Edition An error occurs when 399746 00171169

SharePoint Edition Content Type 397793 00170649

Metalogix Content Matrix

SharePoint Edition Warning occurs while 400767 --

SharePoint Edition Web Parts are not 397748 00170580

SharePoint Edition Exception "No 293117 00159095

SharePoint Edition An exception occurs 394666 00169965

SharePoint Edition Read only' users on 409157 4434620-1

SharePoint Edition Syntax Error on 303384 00147042

SharePoint Edition Getting Value Cannot 409934 4438193-1

SharePoint Edition Connecting to 411205 4452246-1

Metalogix Content Matrix

shows duplicate lists in

Core When performing 380704 00167256

Core Modify use of 398176 --

· The error 407 Proxy Authentication required is 408256

§ Content Matrix is using a proxy that has

§ the proxy server is configured as "Permit

Metalogix Content Matrix

WORKAROUND: Run the "Proxy Login

If a non-MFA (Mult-factor Authentication) user 389424

WORKAROUND: Relaunch Content Matrix

SharePoint Modern Team Sites

If you are using Web Browser Authentication and 402033

· Make sure the account you are using to

· Use Office 365 ADFS authentication to

Metalogix Content Matrix

403 error is thrown when creating Site Collection 251718

WORKAROUND: Keep the tenant open in

When performing a migration using a SharePoint 417247

WORKAROUND: Use a MEWS source

Locked Site Collections

A locked source site collection won’t allow a 115704

NOTE: This is by design as SharePoint will not

Modern Team Sites

· The theme of a modern team site is not 397817

WORKAROUND: Filter out Home.aspx page

· If the name of a subsite is changed on the Site 414281

Metalogix Content Matrix

· When data is migrated from one modern team 410789

· Unlicensed users in a SharePoint Online tenant 414364

Community Site Migration

· The migrating account always gets added to a 232167

· Members of a Community Site Member list are 232176

· Map missing user Option is not updating 233345

NOTE: Should multiple source users be

· Metadata will always get copied with Member 233278

NOTE: When migrating ONLY the members list

WORKAROUND: migrate the Member List as

Metalogix Content Matrix

· Gifted badge values are not getting migrated 232168

· Best Reply inside discussion list is not migrated 233283

WORKAROUND: Migrate the Member List