What is the appropriate way of importing metadata fields, that have multiple values, into SharePoint 2007 or SharePoint 1210? Is there a proper format or delimiter that is needed?
Yes, there is a proper delimiter that should be used. ;# is the delimiter for multiple items on a choice column. So if the desired result is "a;b" then users would enter ;#a;#b;# in the field, and then map the column when migrating.
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: