Question
Before I can install the Metalogix SharePoint Extensions Web Service I need to know specifically what files are installed, and where. Can this information be provided?
Answer
Yes, we can provide some information on what files are installed.
The Metalogix Extensions Web Service installs as a SharePoint solution (.WSP file) that is automatically deployed by the Web Service installer, and pushed out to all Web Front Ends (WFE's) in the farm. Inside the solution file are the necessary files for the Web Service. These files are:
·An ASMX file and two ASPX files, which are put in the SharePoint hive. These three files will be listed under a folder that is added for that specific version of the Web Service. For example, three files will be listed under: C:\Program Files\Common Files\Microsoft shared\Web Server Extensions\[hive_number]\ISAPI\ML\[version_number]
·A DLL file, which gets deployed to the Global Assembly Cache (GAC).
After installation the Metalogix Extensions Web Service sits idle on the server until requests are made to it, by the Content Matrix client. For more information about the Metalogix Extensions Web Service, please see the Installing the Metalogix Extensions Web Service in the Content Matrix Advanced Installation Guide.
Question
Can I use Content Matrix to migrate JavaScript content from my source to my target SharePoint server?
Answer
It is possible to migrate some JavaScript using Content Matrix, depending on the type of JavaScript being migrated. If the JavaScript from the source is embedded in a Content Editor Web Part, or embedded in a publishing page (in a pages library), it should be migrated the same as other SharePoint content. If the JavaScript is not embedded in either of these, then it will not be migrated with Content Matrix. JavaScript can only be migrated into SharePoint, in locations that SharePoint itself will allow JavaScript to be manually added (in web parts and publishing pages).
There are two things to keep in mind if migrating JavaScript that is embedded in web parts or publishing pages. The first is that any links in the JavaScript will not be corrected. This is because the links are also embedded in the content, so they would not be picked up as part of the link correction process. These links must be manually corrected. In order for Content Matrix to correct these links it would have to edit the actual contents of the web part or publishing page, and this is something we try to avoid.
The second thing to keep in mind is that if the Reattach Publishing Page Layouts check-box is selected any customizations for the page (including JavaScript and any other customizations) will be lost.
Question
Can Content Matrix migrate site variations?
Answer
Yes, Content Matrix does have the ability to migrate SharePoint site variations. In order for site variations to correctly migrate the Site Variation feature must be enabled on the target SharePoint environment before the migration. When the site content is migrated using Content Matrix, the content is copied into the target location, and it is actually the SharePoint API that creates the site variations.
If there are any special variation configurations on the source content, these configurations would need to be recreated on the target environment prior to migration.
Question
What is the difference between SharePoint 2007 document IDs, and the SharePoint 2010 and later Document ID feature? And what is the difference between the various ID preservation options that are available in the List Content Options tab in the Configure Copy Options dialog?
Answer
There are three types of ID's that can be preserved when migrating content in Content. Each of these ID types has its own check-box option on the List Content Options tab in the Configure Copy Options dialog. A breakdown of each of these ID types and their available migration options is below:
·SharePoint List Item IDs - These are IDs on SharePoint List items and folders. SharePoint lists can contain items and folders, and these items and folders are a collection of data that is strictly in SharePoint (meaning that there are no actual documents, such as DOC files, CSV files, etc.). The IDs for SharePoint List content are contained in an ID field in the list metadata, and these ID values are used by SharePoint to differentiate (as a unique identifier) all of the items and folders in the list. The values are incremented whenever a new item is added to the list.
These types of IDs can be preserved when migrating content, as long as there is an Object Model (OM) connection to the target (either through a Local connection, or the use of the Metalogix Extensions Web Service), and the Preserve IDs on items/folders in Lists option is selected.
·SharePoint Document Library Item IDs - These are IDs on SharePoint Document Library documents and folders. Document Libraries and folders use the document's filename (and path) as the unique identifier, however, there is still an ID value for each document. This ID value is instead used to help with document ordering in most cases, although it can be set up as a unique identifier as well. The values for this data are contained in an ID column, and the values will increment when a new document is added to the document library.
These types of IDs can be preserved using the Preserve IDs on items/folders in Document Libraries option, however, this action is not normally available, and requires some special configuration before it can be used. This option is mainly for use if performing incremental copies of document libraries. If this option is not used then SharePoint itself will automatically assign this value. For more information on how to enable this option, please contact Quest Support.
·Document ID Service - The use of these types of IDs started with SharePoint 2010, and are only available if the Document ID Service feature is enables at the Site Collection level. These ID values are a little different because these IDs can be directly linked to documents and document sets in SharePoint. The benefit of this is that it creates a URL for that specific document or document set, and that URL can always be used to directly access that document no matter where it is moved to within the Site Collection (because it uses the document ID in the URL instead of giving a file path). The values for this type of ID are contained in the Document ID column. For more information on the SharePoint Document ID feature please see the following MSDN article: http://msdn.microsoft.com/en-us/library/ee559302.aspx.
These types of IDs can be preserved by using the Preserve SharePoint Document IDs (Requires SharePoint Crawl) option. This option is only available when migrating from SharePoint 2010 or later sources into SharePoint or later target environments (any SharePoint connection adapters can be used). In order for the Preserve SharePoint Document IDs option to work the Document ID Service feature must be activated on the target Site Collection before migration.
When this option is used the migrated documents or document sets will use the same ID value on the target as they had on the source. However, because the ID value might not conform to the target Site Collection's Document ID standard, the URL for the document or document set will not immediately work on the target (the URL would still work on the source). In order for this URL value to work in the target environment users must run a SharePoint Crawl action on the target web application. After performing the crawl the Site Collection will be able to find the document or document set based on the URL using the ID value. Any old links that incorporate the ID value for the migrated document or document set will work, provided link correction has also been used.
NOTE: If content is migrated to the target, and this Document ID is preserved, but there are also documents that already exist within the Site Collection, and two or more of these documents or document sets use the same ID value, then when the the link is used SharePoint will open a Search results page, and display all of the documents or document sets that use this same ID. Users can then select the specific document or document sets they are trying to access.
If the Preserve SharePoint Document IDs (Requires SharePoint Crawl) option is not used, the migrated documents or document sets will automatically be assigned a new Document ID value by the target Site Collection, the same as if the document or document set has been manually uploaded. This means that the document or document set will get a new URL containing its new Document ID value, and the links for these Document IDs can be used immediately.
SPECIAL CASE: When documents or document sets are migrated into a SharePoint 2010 or later site collection with the Document ID Service feature disabled, some of the documents or document sets will still have their source Document ID value and Document ID URL. This happens when the documents or document sets that are being migrated contain some specific metadata that SharePoint will automatically push into these columns. This most often happens with certain file types, like DOCX files and other Microsoft file types. If connected to the target SharePoint 2010 or later environment using the Object Model (OM), via a Local connection or the Metalogix Extensions Web Service, then users can use the Disable SharePoint Document Parsing option (located in the List Content Options tab in the Configuration Copying Options dialog), and this should cause Content Matrix to no longer read these fields when migrating the documents or document sets.
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center
