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?
The files on the file system are left as is. Metalogix Content Matrix Console - File Share Edition only performs read operations on source files.
Your Metalogix 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.
How does Metalogix Content Matrix deal with environments that use proxies, load balancing and/or alternate access mappings (AAM)?
Metalogix Content Matrix Console should not run into any issues with these three things. Metalogix Content Matrix uses a Metalogix Extensions Web Service that 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.
Basically, if you can access the regular native web services with all of your network configurations active, then you should also be able to reach the Metalogix Extensions Web Service, and migrate your content.
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, or the Manually Configuring Proxy Settings page if the proxy settings need to be manually configured.
I want to manually edit an XML configuration file that was generated by Metalogix Content Matrix Console but can't find it. Where should I look for the XML files?
XML files generated by Metalogix Content Matrix Console can usually be found under one of the following locations:
Vista - C:\Users\[USER]\AppData\Roaming\Metalogix\Metalogix Content Matrix Console - File Share Edition
XP - C:\Documents and Settings\[USER]\Application Data\Metalogix Software Corp\Metalogix Content Matrix Console - File Share Edition
Whenever a feature that stores an XML configuration file is used for the first time, Metalogix Content Matrix Console will create the XML file. These XML files can be edited manually if desired. If users are looking for a specific XML file and can't find it in the specifiec location, it is possible that it is the first time the feature is being accessed, so the file has not generated yet. Metalogix Content Matrix Console will keep the XML data in memory until the application is closed, so after the client is closed, the XML file will be generated in the folder
If choosing to edit one of the XML files, be sure to close the Metalogix Content Matrix Console first. Then make the desired edit, and re-open Metalogix Content Matrix when ready. If the client is still running when the desired changes are made, those changes will be overwritten when the client is next closed.
A few examples of the more commonly used XML configuration files are:
I have been trying to create a new Site Collection in SharePoint 2013/2016 through Metalogix Content Matrix but I have been encountering issues. Why is this happening? and what can I do about it?
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 Metalogix Content Matrix Console connects to a SharePoint server it has to authenticate through a web application. When connected to a SharePoint 2013 or 2016 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.
In SharePoint 2013 and 2016, 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 2013 connections that use the Local Object Model connection 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 2013 Site Collections when using the Remote OM connection type, but in order to do this Metalogix Content Matrix Console must elevate your permissions for the creation step. Before elevating any credentials, Metalogix 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.
NOTE: All of the above is also true if you are migrating to a SharePoint 2010 environment that uses Claims authentication.
Possible Errors when Creating Site Collection in SharePoint 2013
Below is a list of errors (and their explanations) that you might encounter when trying to create Site Collections in SharePoint 2013 through Metalogix Content Matrix Console.
·Error Message 1 - Unable to create a site collection using Self Service Site Creation under the Administration Web Application.
Explanation/Resolution - The User is connected to the Central Administration web application (using a farm or web connection type) and is trying to create a Site Collection using Self Service mode. This is not allowed. You will need to use the Admin mode instead.
·Error Message 2 - Unable to obtain Web Application '<web application name>'.
Explanation/Resolution - Metalogix Content Matrix is unable to find the web application. This should not occur unless a serious issue within SharePoint has occured 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 Message 3 - 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.