Quest Migration Manager for SharePoint 2.1.1 Release Notes

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.

New in This Release

Automatic Local Server Discovery - When installing Migration Manager on a SharePoint server, the SharePoint server farm the local server belongs to is automatically registered in Migration Manager. You can start migrating sites and content to and from the local farm right after completing the installation.

Server Discovery in the Web Console - The Migration Manager Web Console has been extended to enable adding SharePoint farms with a browser. You can add both the source and target SharePoint servers to Migration Manager as you configure your migration job. The sites and lists from a newly added SharePoint farm are instantly available for selection.

Windows Server 2008 R2 Support - Migration Manager for SharePoint 2.1.1 supports SharePoint servers running Windows Server 2008 R2.

Resolved Issues and Enhancements

Known Issues

The following is a list of issues known to exist at the time of Quest Migration Manager for SharePoint 2.1.1 release.

Feature	Known Issue	Change Request
SharePoint 2003 - SharePoint 2007
	Migration Manager is unable to update the document metadata if the following error occurs in SharePoint: "The document has been modified by SharePoint\System".	CR#65189
	When migrating a meeting workspace for a recurrent event, some event instances may be duplicated on the target. As a workaround, open the event and save it back.	CR#64495
	If an event is linked to a meeting workspace that was deleted on the source, you will get the following error messages: "There is no Web named "site_URL""; "Unable to set 'TimeZone' field"; "Unable to set 'EndDate'' field".	CR#65351
	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#60672
	Migration Manager is 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
	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
	By default, the web part migration does not support two-agent mode. To workaround, configure the stored credentials on the target server: Open Control Panel \| Stored User Name and Password. Add user account and password for the source server. Note: If you use alias for the server, the original name should also be added. Restart Custom Page Migrator scheduled task. Repeat web part migration. Note: To configure stored credentials, you have to be logged on under the Migration Manager scheduled task account.	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
	When migrating the Blog site, "the given key was not present in the dictionary" error may occur during the Posts list import operation. This error does not affect the Blog site functionality and can be ignored.	CR#00000
	You cannot migrate a site to a new site collection if the site language is different from the global server language.	CR#65188
	Site collections cannot be moved to a different database within the same web application and retain their URL at the same time (the target URL has to be different from the source one). Use the stsadm backup/restore or mergecontentdbs operations instead.	CR#65350
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
Japanese SharePoint Support	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

Global Operations

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.

System Requirements

Before installing Quest Migration Manager for SharePoint, ensure your system meets the following minimum hardware and software requirements:

SharePoint 2003 Server

Migration Manager supports migration from one of the following SharePoint version:

SharePoint 2007 Server

Migration Manager Host Server

The SharePoint server must meet the following system requirements to run Migration Manager:

Getting Started

Contents of the CD

Installation Instructions

For installation instructions, refer to Quest Migration Manager for SharePoint User Guide.

For More Information

Contacting Quest Software:

Contacting Quest Support:

Quest Support is available to customers who have a trial version of a Quest product or who have purchased a Quest product and have a valid maintenance contract. Quest Support provides unlimited 24x7 access to SupportLink, our self-service portal. Visit SupportLink at http://support.quest.com/.

View the Global Support Guide for a detailed explanation of support programs, online services, contact information, policies and procedures. The guide is available at: http://support.quest.com.

Contacting Development:

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.

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.

Third Part Contributions

This product includes software developed by Corporation for National Research Initiatives.

This product includes software developed by Stichting Mathematisch Centrum Amsterdam, The Netherlands.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/).

If you have any questions regarding your potential use of this material, contact:

Disclaimer

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.

Feature	Enhancement	Change Request
General	All Migration Manager log files are now stored in one location.	CR#00000
SharePoint 2003 - SharePoint 2007	When migrating a list with the modified field types, these field types will be migrated correctly.	CR#62669
SharePoint 2003 - SharePoint 2007	After the migration, the users have the appropriate permissions on the target list/site.	CR#64499
SharePoint 2007 - SharePoint 2007	A site containing a web part with an image from the document/picture library on the default.aspx page is migrated correctly.	CR#64654

Email	info@quest.com
Mail	Quest Software, Inc. World Headquarters Polaris Way Aliso Viejo, CA 92656 USA
Web	http://www.quest.com