You can disable Self-Service workstations from running migrations without actually deleting the workstations from the Self-Service configuration.
NOTE: Currently, this option will disable job execution for all Self-Service workstations. Any Self-Service jobs currently queued for execution will still run.
To disable Self-Service job execution:
From the Manage Manage Workstations dialog, choose Disable Job Execution.
Values in the Job Execution Allowed column for all workstations will change from Yes to No.
When workstations are disabled and a Self-Service user attempt to run a migration, a pop-pup message will display informing the user that the job cannot be run.
This section answers some of the most frequently asked questions about using Metalogix Content Matrix.
Are read and write permissions to the SharePoint content database sufficient for the Metalogix Extensions Web Service to perform migration?
As you may know, the Metalogix Extensions Web Service requires read and write permissions to the Content Database, according to a Microsoft KB article (http://support.microsoft.com/kb/935751. However, this is only a solution if you have encountered the message "Unhandled Exception: system.IO.FileNotFoundException" when using the SharePoint object model. We have found that few users have reported this issue, since the Web Service account is usually granted the sysadmin server role, which has complete control over all database functions.
After some internal testing we have determined that the Web Service installing account requires more than read and write permissions to function without database errors.
1."db_owner" rights to the SharePoint Content Database is required.
If the Web Service account does not have the db_owner right to the SharePoint Content Database, Metalogix Content Matrix will not be able to migrate list items using the Web Service, and may receive one of the following errors:
4/19/2010 7:13:53 PM Error copying list item: 1/1 (id: 1, title: Get Started with Windows SharePoint Services!): Service Error: [MLSPService could not add items: MLSPServiceMethods.AddListItems() Failed: Cannot open database "WSS_Content" requested by the login. The login failed.
4/20/2010 10:21:01 AM Error copying list item: 1/2 (id: 1, title: Get Started with Windows SharePoint Services!): Service Error: [MLSPService could not add items: MLSPServiceMethods.AddListItems() Failed: Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT))
2."db_owner" or "WSS_Content_Application_Pools" rights to the SharePoint Admin Content Database is required.
If the Web Service installing account does not have db_owner or WSS_Content_Application_Pools rights to the SharePoint_AdminContent, Metalogix Content Matrix will not be able to create/paste site collections, and will receive an error.
With these cases in mind we have determined that the Metalogix Extensions Web Service account should be granter the db_owner permission rights, at a minimum, to allow Metalogix Content Matrix to correctly migrate content to the target SharePoint instance.
I am using the Fabulous 40 Templates that were released by Microsoft in my SharePoint Sites. Am I able to migrate the content that uses these templates with Metalogix Content Matrix Console?
Unfortunately Metalogix Content Matrix does not support the Fabulous 40 Templates that were released by Microsoft. These templates contain a number of customizations, and these customizations cause some problems for Metalogix Content Matrix when we try to migrate and map content. Metalogix Content Matrix is able to migrate some of the content, however, because of some of the customizations that have been made to the template, we can run into problems that prevent us from migrating other parts of the content correctly, or prevent us from migrating the pages at all.
While not able to migrate using the Fabulous 40 Templates, it is possible to create Site Collections using the .WSP-based templates, from the Fabulous 40, as long as these templates are deployed on the server beforehand. It is not possible for Metalogix Content Matrix to create any Site Collections using the .STP templates, since it is not possible to create Site Collections using these templates through the Web UI.
SharePoint 2010 does not support the Fabulous 40 Templates.