I am having issues migrating MySites, more specifically the User Profiles that are associated with MySites. What could be causing this issue, and is there a solution for it?
In most cases Metalogix Content Matrix can migrate MySites along with the User Profile data, however, there are cases in which this data may have trouble migrating across.
MySites can use one of four possible naming conventions in the MySite host, and these naming conventions can affect how MySite and User Profile data can be returned. These naming conventions are:
·Domain_Username - This naming convention requires that the MySite name needs to be specified as the same name for the user who it belongs to. The Domain_Username format is used to name the MySite. For example if user John_Doe had a MySite, the MySite would be named John_Doe.
·Unknown - The naming convention for this type is an unknown format. As a result all Metalogix Content Matrix can return is the information we get from the SharePoint Object Model (OM). This format is returned if end users have modified the naming convention to a custom format. This is usually the naming convention that causes the most issues.
·Username_CollisionsDomain - This naming convention uses a User name format (and not a Domain_Username format). When migrating MySites, Metalogix Content Matrix will use the Domain_Username format if a MySite with the User name (under the User name format) already exists.
·Username_CollisionError - This naming convention will be used if the Username_CollisionsDomain format is being used and an exception is thrown because a site with the same user name already exists.
In the case of the Unknown naming format, Metalogix Content Matrix may not be able to preserve the naming convention, in which case the migration of the MySite should fail.
In this type of situation there is a workaround method that users can use. Instead of migrating the MySite as a MySite, you can migrate it as a regular SharePoint site collection (to any target location). Once this is done you can then manually link the User Profile to the appropriate site collection or site.
What is the optimal setup for best performance for Metalogix Content Matrix?
The optimal setup for performance with Metalogix Content Matrix is to have the application itself installed on the target server, and the Metalogix Extensions Web Service installed on the source server. Then use a SharePoint Database (DB) connection to connect to the source. The Metalogix Extensions Web Service would not need to be installed on the target since the application itself would be installed, allowing for a direct connection to the SharePoint Object Model (OM).
There are a few trade-offs for using the DB connection for the source. In these cases you will be limited with: no write access, no server level connections or actions, and the potential to run into issues when dealing with custom site templates. If these are trade-offs that you are not willing to deal with then it is recommended to connect to the source using a Metalogix Extensions Web Service connection.
The main issue that can cause slowdown with the Metalogix Content Matrix Console is copying file structure. If the content that is being migrated contains a large file structure the migration will go slower because Metalogix Content Matrix will try to recreate this structure.
For example, if we have two sites that contain the same amount of data, Site A and Site B, and Site A uses a more complex file structure than Site B, the migration of Site A will run slower then the migration of Site B. Even though these sites contain the same amount of data Metalogix Content Matrix will require more time to recreate the complicated structure of Site A, resulting in Site B finishing it's migration first.
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 am having trouble installing the Metalogix Extensions Web Service. Are there any steps I can take to troubleshoot?
Yes, there are some steps you can take to troubleshoot installation issues for the Metalogix Extensions Web Service.
The first thing that you want to check is that the account that is being used to install the Metalogix Extensions Web Service has all the necessary permissions. This user account needs to be able to run the STSADM commands on the installing system, and also needs the following permissions:
·SharePoint Site Collection Administrator
·Read/Write access to the Content Database (DB)
·Administrator on the installing system
In some cases users can receive a message saying "Could not deploy SharePoint solution: Cannot open SPAdminV4 service on computer." when they try to install the Metalogix Extensions Web Service. There are two possible methods for working around this issue.
1.Navigate to the folder containing the Metalogix Extensions Web Service installation EXE file. Right-click on this file and choose Run as Administrator. The Web Service should now be able to install. Some instances of Windows will automatically block services from being registered fully. In these cases, running as administrator should get around this issue.
2.In some cases, users are not able to use the Run as Administrator command, or this does not solve the issue, then there is a second workaround method that can be used. The alternate solution is to turn off the User Access Control (UAC) and reboot the server. This should allow the installing account to correctly install and deploy the Metalogix Extensions Web Service. Once installed and deployed you can re-enable UAC.
After the Web Service has been installed, there is a check that can be made to see if the Web Service can be detected on any given machine. For more information on running this check please see the After Installing the Metalogix Extensions Web Service section of the Installing the Metalogix Extensions Web Service page.