Chatta subito con l'assistenza
Chat con il supporto

Content Matrix 9.10 - File Share Edition

Introduction Activiating the License Key Selecting the SQL Database You Want to Connect to Content Matrix Console End User Interface Enabling Advanced Mode Enabling and Disabling Optimistic Mode Connecting to a File System Connecting to SharePoint Preparing for a Migration Initiating a Migration Configuring Copying Options Saving or Running a Migration Job Job 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 Content Matrix deal with environments that use proxies, load balancing and/or alternate access mappings (AAM)?

Answer

Content Matrix Console should not run into any issues with these three things. Content Matrix uses the Metalogix Extensions Web Service (MEWS), which 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.

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.

SharePoint Site Collection Creation Issue

Question

I have been trying to create a new site collection through Content Matrix but I have been encountering issues. Why is this happening? and what can I do about it?

Answer

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 Content Matrix Console connects to a SharePoint server it has to authenticate through a web application. When connected to a SharePoint 2013 or later 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.

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.

Connection icon

From internal testing, we have determined that SharePoint connections that use the Local Object Model 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 site collections when using the Remote OM connection type, but in order to do this Content Matrix Console must elevate your permissions for the creation step. Before elevating any credentials, 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.

Possible Errors when Creating Site Collection in SharePoint

Below is a list of errors (and their explanations) that you might encounter when trying to create site collections in SharePoint through Content Matrix Console.

·Error Message 1 - Unable to obtain Web Application '<web application name>'.
Explanation/Resolution - Content Matrix is unable to find the web application. This should not occur unless a serious issue within SharePoint has occurred 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 Message2 - 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.

Job List Database fails to Load After Upgrade

Question

I recently upgraded to Content Matrix Console version v.6.2.x.x and my Job List database is failing to load. What might be causing this issue? and how can I fix it?

Answer

This issue was likely caused by a recent upgrade to Content Matrix Console's security features. A security upgrade has been made in Content Matrix Console version 6.2.0.0 and later. This change has resulted in two potential issues that users can encounter. These issues and their resolutions are:

·Issue 1: The Job List database failing to load.
 
Resolution: When the Content Matrix Console client opens, an error message will prompt the user to open the Job List file again. Go down to the Job List section and click File > Open Job List. This will open a Browser window. Navigate to the location that contains the LST file for the Job List that was previously listed in the Job List section. Then select the LST file and click Open. The Job List will now be loaded and users can continue as normal.
 
Due to the security upgrades in version 6.2.0.0 and later, the security settings for the Job List need to be upgraded. Content Matrix Console cannot do this while the job is actively selected, but can apply the update to the existing Job List the next time it is loaded back to the Job List section of the client application.

·Issue 2: Any connections that have had the Save my credentials check box selected will no longer have their passwords saved.
 
Resolution: For any connections that had their credentials previously saved by using the Save my credentials option, you will need to connect or reconnect to that environment and enter the password in again, then complete the connection. The security upgrade has caused the encryption file for any saved passwords within Content Matrix Console to be upgraded, and to apply this upgrade to this file, any saved passwords must be re-entered.

Migrating Empty Folders

Question

Is it possible to migrate any empty folder within my File Share?

Answer

Yes, it is possible to migrate any empty folders into SharePoint. By default any empty folders that exist within the File Share folder structure will be migrated into the target SharePoint environment.

If the configuration options for the migration are set to determine the folder name (that each file should be migrated into) based on the data in a custom column, then any empty folders will still be migrated but they will ignore this setting and instead use the original empty folder name.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione