Quest® Migration Manager for SharePoint
Version 2.1
November 5, 2009
Welcome to Quest Migration Manager for SharePoint
Resolved Issues and Enhancements
Migration Manager helps you migrate and consolidate your accumulated SharePoint data assets from SharePoint 2003 servers to a new installation of SharePoint 2007.
After migration to the SharePoint 2007 platform is completed, Migration Manager can be used to deploy and restructure SharePoint content within and across SharePoint 2007 server farms.
More Robust, Scalable SharePoint 2007 Migration - Migration Manager 2.1 breaks site migration into multiple migration tasks internally. Each task is handling an individual site or list. Should an error occur, only the affected task fails and migration of other sites and lists proceeds. With native tools, a slightest error during export or import causes the entire migration to fail. Migration Manager makes a few retries on the failed task automatically before giving up and reporting an error. You can review the error message, fix the issue and retry that particular task individually, without restarting the whole migration job or cleaning up after the failed migration.
Granular SharePoint 2007 Re-Sync - You can perform full resynchronization of SharePoint 2007 to 2007 migration jobs. Job resynchronization will apply new and updated content, modified settings and security permissions to the target sites and lists. You can re-sync either the whole migration job at once or any specific pair of sites or lists within the scope of the job.
Migration Exclusions - When configuring a site migration job, you have an option to exclude specific child sites, lists and libraries so that only the content you need is carried over to the new location. This saves bandwidth for unwanted data transfers and/or relieves you from extra clean-up work.
Batched List Migration - You can migrate multiple SharePoint lists and libraries with a single migration job. A job can include lists from one or more sites. This minimizes the number of migration jobs to configure and monitor when consolidating content across multiple sites.
More State-Based Job Views - Migration job tracking has been significantly improved in this version. New views have been added to provide a better insight into the migration process.
Enhanced Migration Job Properties - The following job properties enhancements are implemented in Migration Manager for SharePoint 2.1:
Migration pairs - get insight into which sites and lists your migration job is comprised of, what your source sites and lists are mapped to in the target; and see the completion status of or restart any individual migration task (for SharePoint 2007 to 2007 migrations only).
Last modified - Migration Manager now provides the time metric for SharePoint 2003 to 2007 migration jobs that shows when the most recent modification (edit, add, delete) to the source content (list items, documents, lists, libraries and sites) was detected in the scope of the migration job. This metric helps you understand when it is safe to pull the plug on the migrated sites.
Web part migration view - tThe web part migration tool now provides a more detailed view of web part migration jobs. For each job, it displays a list of SharePoint 2003 pages and document libraries to be processed as well as their target counterparts in SharePoint 2007.
Info Portal Bundled - Site Administrator’s Information Portal that comes with Migration Manager 2.1 free of charge is a web-based dashboard portal that aggregates data across all SharePoint farms and presents it on the Enterprise level, allowing to drill down to specific sites and sub-sites. This tool complements the built-in reports in Migration Manager and can be used for pre-migration and post-migration analysis of your SharePoint environment.
|
Feature |
Enhancement |
Change Request |
|
SharePoint 2003 - SharePoint 2007 |
If the relative URL of the migrated site contains two or more entries of the site collection relative URL, the content of this site is migrated successfully. | CR#63245 |
| If the job name contains "/" symbol, web part migration works properly. | CR#62332 | |
|
If a job contains several sites from different content databases, post-migration synchronization runs successfully. |
CR#00000 | |
| Sites with deleted owners are migrated successfully. | CR#00000 |
The following is a list of issues known to exist at the time of Quest Migration Manager for SharePoint 2.1 release.
|
Feature |
Known Issue |
Change Request |
|
SharePoint 2003 - SharePoint 2007 |
||
| Private views for Lists and Document Libraries are not migrated. | CR#63590 | |
| Migration Manager does not support migration of area document libraries based on specific portal template. | CR#63521 | |
| Forms Libraries are excluded from migration by default. To workaround the issue, take the steps described in the article available at http://sharepointforall.com/forums/p/276/418.aspx. | CR#51994 | |
| URLs in the link fields are not processed during migration. For more information, please see http://sharepointforall.com/forums/p/587/993.aspx. | CR#55982 | |
| Changes to the settings and permissions of sites, lists and document libraries are not synchronized during post-migration synch. | CR#62607 | |
| Alerts migration is not supported. | CR#48865 | |
| When starting the Migration Manager for the first time, the browser security dialogue might be displayed. Сlick the Add button to add the web site to the trusted zone, and then click Add again. If the browser displays an error message, click Yes to continue until the browser accepts the modified security settings. | CR#00000 | |
| If you use Internet Explorer to work with the web console, it might take up to 30 seconds to open the Set schedule dialogue when the Migration Hours option is selected. | CR#00000 | |
| If you checked the On radio button in the Start job options, and then selected to view the Pre-migration analysis report, the On option will be disabled when returning to the main page. As a workaround, select one of the other two options, and then try On again. | CR#00000 | |
|
When migrating a source site based on custom site definition, the migration job gets stuck in a starting state.
For instructions on how to migrate sites based on custom site definitions, please refer to the
Appendix D in Quest Migration Manager for SharePoint User Guide. |
CR#00000 | |
| If a source web part contains a custom view, this view might be migrated incorrectly. | CR#00000 | |
| Site themes are not preserved during migration. | CR#00000 | |
| Web part migration is not supported for Portal sites and areas. | CR#00000 | |
| Migration Manager unable to update the information in the Microsoft Office document if it was created by third-part tool. | CR#00000 | |
| If the source site is incomplete, the error message "Unable to locate the source site template STS#-1 in the mapping rules" will be written to the source Log file. | CR#00000 | |
| If the target site/list/document library already exists, the content will be migrated to the existing site/list/document library. | CR#00000 | |
| When migrating content or portal site, the list/document library is not migrated if the target site contains list/document library with the same relative URL but different title. As a workaround, rename the target list/document library or delete it, and then re-migrate. | CR#59123 | |
| If a discussion board to be migrated contains a view that has been modified, this view will not work on the target. As a workaround, delete this view and create a new one. | CR#00000 | |
| Migration performance may drop significantly for migration jobs that include document libraries with lots of document versions. | CR#00000 | |
| The values in the Issue ID fields are automatically set on the target and might differ from the source values. | CR#00000 | |
| Synchronization of new sites does not work for portal site migration jobs. | CR#00000 | |
| If document or list items were deleted on the target, their modifications are not synchronized. | CR#00000 | |
| When migrating a meeting workspace with meetings previously deleted from calendar or scheduling tool, these meetings will not be migrated. | CR#00000 | |
| Some views in the lists and document libraries might be migrated incorrectly. As a workaround, delete the view on the target, and then recreate it. | CR#52798 | |
| If a Survey list contains responses from the users whose accounts cannot be resolved (e.g. local user accounts) on the target and the Allow multiple responses option is set to "no", by default these responses as well as the responses from legitimate users will not be replicated to the target Survey list. Contact Quest Support to adjust this option behavior during migration. | CR#53724 | |
| When migrating a meeting workspace for a recurrent event, all event occurrences will be recreated on the target even if some of them were deleted or changed on the source workspace. | CR#00000 | |
| Migration Manager for SharePoint requires that the Quest repository database is on a SQL server running Microsoft SQL Server 2005 (including Express Edition). The product may not work if the database is stored on SQL 2000. | CR#00000 | |
| A meeting workspace linked to an event list in a parent web site is not migrated properly if migrated separately from the parent site. | CR#00000 | |
| For the Help to be displayed correctly, make sure the cursor is in the right pane. | CR#00000 | |
| When an SPS 2003 portal site is migrated to MOSS, the target site navigation contains sites for all the source areas, including those hidden from the portal site navigation in the source site. | CR#00000 | |
| SharePoint 2007 - SharePoint 2007 | All scheduled migration jobs are displayed in the Running jobs view. | CR#00000 |
| For SharePoint 2007 to 2007 migration, Migration Manager uses Microsoft Content Migration API and does not preserve the content this API cannot export/import: alerts, audit trail, change log history, check in/check out state, recycle bin items, recycle bin state, security state, workflow tasks, and workflow state. | CR#00000 | |
| Publishing sites (web sites with Microsoft Office Server Publishing features enabled) may not work properly after migration due to broken layout references. You can use SharePoint Designer to fix references. | CR#00000 | |
| Migration fails if there are mail-enabled lists and libraries in the scope. | CR#00000 | |
| Japanese SharePoint Support | When migrating sites with the permission migration option enabled, Migration Manager will use English names for the standard permission levels (e.g. Reader, Designer etc) instead of Japanese names. To use standard Japanese permission levels, replace the WSS3Levels.xml file in the Migration Manager root directory with the WSS3Levels.xml file from the %installdir%\JP directory, and restart the Migration Manager services. | CR#00000 |
| When migrating Contact type lists, the City and State fields might switch places. To avoid the issue, replace the Migrators.xml file in the %installdir%\SpringConfigs directory with the Migrators.xml file from the %installdir%\JP directory, and restart the Migration Manager services. | CR#00000 |
This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.
This release is Unicode-enabled and supports any character set. It supports simultaneous operation with multilingual data. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan.
Before installing Quest Migration Manager for SharePoint, ensure your system meets the following minimum hardware and software requirements:
Migration Manager supports migration from one of the following SharePoint version:
Note: The prescan.exe utility must be run on the source SharePoint 2003 server before proceeding with content migration using Migration Manager. The prescan tool can be downloaded at http://www.microsoft.com/downloads/details.aspx?FamilyID=e8a00b1f-6f45-42cd-8e56-e62c20feb2f1&DisplayLang=enn.
Migration Manager supports the following SharePoint versions:
Microsoft Office SharePoint Server 2007
Windows SharePoint Services 3.0
The SharePoint server must meet the following system requirements to run Migration Manager:
The Migration Manager for SharePoint CD contains the following:
For installation instructions, refer to Quest Migration Manager for SharePoint User Guide.
| info@quest.com | |
| Quest Software, Inc. World Headquarters Aliso Viejo, CA 92656 USA | |
| Web |
Refer to our Web site for regional and international office information.
Quest Support is available to customers who have a trial version of a Quest
product or who have purchased a commercial version and have a valid maintenance
contract.
Quest Support provides around the clock coverage with SupportLink,
our web self-service. Visit SupportLink at http://support.quest.com/.
From SupportLink, you can do the following:
View the Global Support Guide for a detailed explanation of support programs,
online services, contact information, and policy and procedures.
The guide
is available at: http://support.quest.com/pdfs/Global%20Support%20Guide.pdf.
You can contact the development office by e-mail: SharePointFeedback@quest.com
This document contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc.
© 2009 Quest Software, Inc. ALL RIGHTS RESERVED.
Quest, Quest Software, the Quest Software logo, Aelita, AppAssure, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk, Foglight, Funnel Web, I/Watch, Imceda, InLook, IntelliProfile, Internet Weather Report, InTrust, IT Dad, JClass, Jint, JProbe, LeccoTech, LiteSpeed, LiveReorg, NBSpool, NetBase, Npulse, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex, Sitraka, SmartAlarm, Spotlight, SQL LiteSpeed, SQL Navigator, SQLab, SQL Watch, Stat, Stat!, StealthCollect, Tag and Follow, Toad, T.O.A.D., Vintela, Virtual DBA, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.
This product includes software developed by Python Software Foundation.
© 2001-2006 Python Software Foundation. All rights reserved.
This product includes software developed by Corporation for National Research Initiatives.
© 1995-2001 Corporation for National Research Initiatives. All rights reserved.
This product includes software developed by Stichting Mathematisch Centrum Amsterdam, The Netherlands.
© 1991-1995 Stichting Mathematisch Centrum Amsterdam, The Netherlands. All rights reserved.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
© 2004-2008 The Apache Software Foundation. All rights reserved.
If you have any questions regarding your potential use of this material, contact:
| Quest
Software World Headquarters LEGAL Dept 5 Polaris Way Aliso Viejo, CA 92656 Email: legal@quest.com |
The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.