Question
Why am I getting an error when I try to connect to SharePoint 2019 or SharePoint Server Subscription Edition in a FIPS-enabled environment?
Answer
Content Matrix uses some assemblies for FIPS compliance that are not supported for certain SharePoint 2019 and SharePoint Server Subscription Edition connections.
For a remote object model (MEWS) connection (displays for the top node) for SharePoint 2019:
Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'. The request failed with the error message: -- <!DOCTYPE html> <html>
For a local object model (OM) connection (displays at the item level for SharePoint 2019 and SharePoint Server Subscription Edition):
The type initializer for 'Microsoft.SharePoint.ApplicationRuntime.SPRequestModule' threw an exception
In addition, errors will display in Browser View and Items View.
For SharePoint Server Subscription Edition, you can connect using a remote object model (MEWS) connection.
Question
Is it possible to change the configuration for multiple job files at one time in the Job List section of Content Matrix?
Answer
Yes, this is possible. Most users will only need to change the configuration of a single job in the Job List section, but it is possible to change the configuration for multiple jobs at one time.
In order to modify the configuration for multiple job files at one, select all of the jobs in the Job List section. Once all of the desired jobs are selected there are two methods that can be used to access the configuration dialog. The first is to click the Change Configuration button at the top of the Job List, and the second method is to open the context (right-click) menu, and select the Change configuration for selected jobs option.
The behavior for changing the configuration of multiple files at once changes slightly depending on the version of Content Matrix Console that is being used.
Behavior in Versions 6.1.00 and Later
When changing the configuration for multiple files that use the same type of action at once, only settings that are changed during the re-configuration will be pushed into all of the selected jobs. This means that even if all of the jobs contain different settings, they will all still contain these different settings after the configurations have been modified. Only the settings that were re-configured will be changed (to whatever setting they were changed to).
Let's look at the example of three "Paste Site" jobs that are previously configured, and each has a different Rename action applied to it as well as a few various other differences in selected options. When the Change Configuration is applied to all three at once, only the settings that were reconfigured will be affected. So if the web part options were changed, then those options will be applied to all three jobs, but each will still retain their original Rename setting, and any other settings that were configured even if there are differences.
Behavior in Versions 6.0.0201 and Earlier
When changing the configuration for multiple files that use the same type of action at once, all of the selected files will have the options for the first job in the Job List section pushed into them, regardless of any other setting the previously used. Basically, all of the jobs after the first select job in the Job List will be modified to use all of the settings from the Change Configuration dialog.
Let's look at the example of three "Paste Site" jobs that are previously configured, and each has a different Rename action applied to it as well as a few various other differences in selected options. When the Change Configuration is applied to all three at once, all of the configuration options that are set for the first of the selected jobs in the Job List will be pushed to the two remaining jobs. These two remaining jobs would then use all of the exact same configuration options as the first job, including the values for the rename options. Any of the previous settings for the two remaining jobs would be lost (because they are replaced with the first jobs configuration options).
Question
Does Content Matrix Console - File Share Edition support running multiple clients at the same time?
Answer
Content Matrix Console - File Share Edition does not currently support running multiple migration actions at one time through a single instance of the client. However, it is possible to open multiple copies of the client and have each one run a separate migration action. If multiple instances of the client are opened at the same time to run migrations, users will need to make sure that the source documents/folders are not being copied from the same location, and that the selected target is not the same SharePoint list/site. If the source and target location overlap for multiple concurrent migrations there is a possibility that the SharePoint APIs that are called by File Share Edition will conflict and they will try to overwrite one another. As a result the migrated content may not migrate correctly, and will have to be re-migrated at a later date.
Question
I was wondering what happens to files on the share drive after we migrate them to SharePoint? Are they marked or flagged on the share drive as having been migrated or are they deleted?
Answer
The files on the file system are left as is. Content Matrix Console - File Share Edition only performs read operations on source files.
Your Content Matrix Console - File Share Edition project is the best way to track what has been migrated. We do provide a facility to remove the files from the source location post-migration--if that is what you are looking for. Obviously, this is something to use carefully and we would be happy to discuss further whether this might be useful in your case. Please contact Quest Support for more information.
© ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center
