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.
Question
How does Content Matrix deal with environments that use proxies, load balancing and/or alternate access mappings (AAM)?
Answer
Content Matrix Console should not run into any issues with these three things. Content Matrix uses the Metalogix Extensions Web Service (MEWS), which deploys over a whole farm and functions identically to a regular SharePoint web service. SharePoint web service's get the benefits of IIS redirection, proxy pushing, and anything else that SharePoint can utilize, such as Alternate Access Mappings (AAM). Since the Metalogix Extensions Web Service acts the same as a SharePoint web service it also gets all of these benefits.
In the case for load balanced environments the Metalogix Extensions Web Service would need to be deployed through the target side SharePoint farm. When the Web Service is installed it automatically gets deployed to all the SharePoint instances within that farm, as a SharePoint solution. Once the Web Service is installed on the target server, then load balancing should no longer be an issue.
There are, however, some cases where proxy settings may not work correctly by default. In these cases it is possible to set some specific proxy settings for the specified connection. Please see the Configuring Proxy Settings page for more details.
Question
I have been trying to create a new site collection through Content Matrix but I have been encountering issues. Why is this happening? and what can I do about it?
Answer
Starting with SharePoint 2013, most web applications use claims authentication, but the Central Administration web application that manages the server level settings uses Classic authentication. When Content Matrix Console connects to a SharePoint server it has to authenticate through a web application. When connected to a SharePoint 2013 or later web application that uses Claims authentication, SharePoint itself can have trouble recognizing that the accessing User account has permissions in the web application areas that are managed by Classic authentication. This is also true if connected to a web application that uses Classic authentication, if trying to access an area managed by Claims authentication.
The permissions to create site collections is managed by Classic authentication, so if connected through a Claims authentication web application users will receive a "401 Unauthorized" error message when trying to create a new site collection. This happens even if the user account has all of the appropriate permissions. If connecting through a Classic authentication web application, users will receive permission errors when trying to set any settings on a site collection that uses a Claims authentication web application, after the site collection is created.
|
|
From internal testing, we have determined that SharePoint connections that use the Local Object Model will not run into this issue. This is because the Local OM connection type does not run authentication through IIS, which appears to be a trigger point for the authentication issues. From testing we have also determined that you are still able to create SharePoint site collections when using the Remote OM connection type, but in order to do this Content Matrix Console must elevate your permissions for the creation step. Before elevating any credentials, Content Matrix Console will run a preliminary check to ensure the migrating user has enough permissions initially to be able to use the elevated site collection creation. In order for these elevated permissions to be used, the migrating user account must explicitly (by name) have "Full Control" permissions on the Web Application that the site collection is being created on. In the Remote OM connection case users can also create a site collection within any web application if they are a member of the Farm Administrator group in SharePoint and they are connected to Central Administration as a farm connection. |
|---|
Possible Errors when Creating Site Collection in SharePoint
Below is a list of errors (and their explanations) that you might encounter when trying to create site collections in SharePoint through Content Matrix Console.
·Error Message 1 - Unable to obtain Web Application '<web application name>'.
Explanation/Resolution - Content Matrix is unable to find the web application. This should not occur unless a serious issue within SharePoint has occurred from the time the site collection configuration dialog was displayed, and the call to the Metalogix Extensions Web Service (for remote OM connections) was made to perform the site collection creation. Check your SharePoint environment, and resolve any issues. Then try again.
·Error Message2 - Migrating user '<migrating user>' requires explicit Full Control on the web application where the site collection is intented to be created. If the migrating user is a member of the Farm Administrators group then connect to the Central Administration site and try again.
Explanation/Resolution - The migrating user has read permissions on the web application (using a farm or web connection type) that they're connected to, but does not have full control on the web application that they are trying to create the site collection in. To resolve this, the migrating user account must be added explicitly (by name) with Full Control to the respective Web Application that they are trying to create the site collection in. They can also create a site collection within any web application if they are a member of the Farm Administrator group in SharePoint, and they are connected to Central Administration as a farm connection.
