Chat now with support
Chat with Support

Metalogix Content Matrix 8.8 - Public Folder Editon User Guide

Introduction Entering the License Key Content Matrix Console End User Interface Installing the Email Viewer Webpart Connecting to Public Folders Connecting to SharePoint Preparing for Your Migration Configuring Copying Options Saving or Running a Migration Action Log Files Using PowerShell with Content Matrix Modifying Content Matrix Configuration and Settings Frequently Asked Questions About Us

Using Proxies, Load Balancing or Alternate Access Mappings

Question

How does Metalogix Content Matrix deal with environments that use proxies, load balancing and/or alternate access mappings (AAM)?

Answer

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.

Troubleshooting the Extensions Web Service

Question

I am having trouble installing the Metalogix Extensions Web Service. Are there any steps I can take to troubleshoot?

Answer

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

·Farm 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.

Installing the Extensions Web Service on Specific Systems

Question

I want to have more control over installing the Metalogix Extensions Web Service, and only install it on some systems. Is this possible?

Answer

Yes this is possible, however, the method for this will change slightly depending on the version of the Metalogix Extensions Web Service you are trying to install. The Metalogix Extensions Web Service installation file contains and deploys a WSP solution file throughout a SharePoint farm.

If you are trying to install version 5.1.0.0 or later:

1.Open a Command Prompt window, and set the directory to the same directory that the EXE installer file is located in.

2.Enter the name of the EXE installer file followed by /v and /a. For example, Metalogix Extensions Web Service Setup v.5.1.X.X /v /a (replacing the "X" with the version number). It is important to make sure there is a space between the "/v" and "/a" values.

NOTE: A "/?" value can be entered after the name of the EXE file to see a list of the command line parameters.

3.This will open the InstallShield, but will not actually install the Metalogix SharePoint Extensions Web Service. Instead it will allow you to select a desired extraction location and it will extract the WSP file and the MSI file.

If you are trying to install a version before v.5.1.0.0 you can (extracting from the WSP file):

1.Open a Command Prompt window, and set the directory to the same directory that the EXE installer file is located in.

2.Then enter the command: msiexec /a "Metalogix SharePoint Extensions Web Service - vX.X.XX.XX.msi" (replacing the "X" with the version number).

3.This will open the Install wizard, but will not actually install the Metalogix Extensions Web Service. Instead it will allow you to select a desired extraction location and it will extract the WSP file to that location.

After the files are extracted users can install the files as they choose.

Changing a Job Configuration for Multiple Files

Question

Is it possible to change the configuration for multiple job files at one time in the Job List section of Metalogix Content Matrix?

Answer

Yes, this is possible. Most users will only need to change the configuration of a single job in the Job List section, but it is possible to change the configuration for multiple jobs at one time.

In order to modify the configuration for multiple job files at one, select all of the jobs in the Job List section. Once all of the desired jobs are selected there are two methods that can be used to access the configuration dialog. The first is to click the Change Configuration button at the top of the Job List, and the second method is to open the context (right-click) menu, and select the Change configuration for selected jobs option.

The behavior for changing the configuration of multiple files at once changes slightly depending on the version of Metalogix Content Matrix Console that is being used.

Behavior in Versions 6.1.00 and Later

When changing the configuration for multiple files that use the same type of action at once, only settings that are changed during the re-configuration will be pushed into all of the selected jobs. This means that even if all of the jobs contain different settings, they will all still contain these different settings after the configurations have been modified. Only the settings that were re-configured will be changed (to whatever setting they were changed to).

Let's look at the example of three "Paste Site" jobs that are previously configured, and each has a different Rename action applied to it as well as a few various other differences in selected options. When the Change Configuration is applied to all three at once, only the settings that were reconfigured will be affected. So if the web part options were changed, then those options will be applied to all three jobs, but each will still retain their original Rename setting, and any other settings that were configured even if there are differences.

Behavior in Versions 6.0.0201 and Earlier

When changing the configuration for multiple files that use the same type of action at once, all of the selected files will have the options for the first job in the Job List section pushed into them, regardless of any other setting the previously used. Basically, all of the jobs after the first select job in the Job List will be modified to use all of the settings from the Change Configuration dialog.

Let's look at the example of three "Paste Site" jobs that are previously configured, and each has a different Rename action applied to it as well as a few various other differences in selected options. When the Change Configuration is applied to all three at once, all of the configuration options that are set for the first of the selected jobs in the Job List will be pushed to the two remaining jobs. These two remaining jobs would then use all of the exact same configuration options as the first job, including the values for the rename options. Any of the previous settings for the two remaining jobs would be lost (because they are replaced with the first jobs configuration options).

Related Documents