Quest Migration Manager 3.2

Transcription

1 Quest Migration Manager 3.2 for SharePoint User Guide

2 2011 Quest Software, Inc. ALL RIGHTS RESERVED. This guide contains proprietary information, which is 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. 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. 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 legal@quest.com Refer to our Web site ( for regional and international office information.

3 TRADEMARKS 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. For a complete list of Quest Software s trademarks, please see Other trademarks and registered trademarks used in this guide are property of their respective owners. Third Party Contributions This product includes software developed by Python Software Foundation Python Software Foundation. All rights reserved. This product includes software developed by Corporation for National Research Initiatives Corporation for National Research Initiatives. All rights reserved. This product includes software developed by Stichting Mathematisch Centrum Amsterdam, The Netherlands Stichting Mathematisch Centrum Amsterdam, The Netherlands. All rights reserved. This product includes software developed by Apache Software Foundation ( The Apache Software Foundation. All rights reserved. Quest Migration Manager for SharePoint Updated March, 2011 Software version 3.2

4 Contents 1 About Quest Software, Inc. 1 Contacting Quest Software Contacting Quest Support General Information 3 About Quest Migration Manager for SharePoint Major Features General Features SharePoint SharePoint SharePoint / SharePoint / Supported SharePoint Features SharePoint 2003 to 2007/2003 to 2010 Migration SharePoint 2007 to 2007 (SharePoint 2010 to 2010) Migration 8 SharePoint 2007 to 2010 Migration How Migration Manager for SharePoint Works 11 Web Console Services Involved Architecture Required Permissions Logs SharePoint 2003 to 2007/ 2003 to 2010 Migration Base Content Migration Services Involved Architecture Required Permissions i

5 Logs Web Part Migration Services and Scheduled Tasks Involved Architecture Required Permissions Logs SharePoint 2007 to 2007/ 2010 to 2010 Migration Services Involved Architecture Required Permissions Logs SharePoint 2007 to 2010 Migration Services Involved Architecture Required Permissions Logs Deploying Migration Manager 27 System Requirements SharePoint 2003 Server SharePoint 2007 Server SharePoint 2010 Server Migration Manager Host Server Required Permissions Permissions Matrix Permissions in Detail Services Responsible for Migration Manager User Interface Workability Services Responsible for 2003 to 2007/2003 to 2010 Migration Services Responsible for 2007 to 2007/ 2010 to 2010 Migration Services Responsible for 2007 to 2010 Migration Additional Services and Scheduled Tasks Pre-installation Steps Installing Message Queuing on Windows Server Installing Message Queuing on Windows Server Starting the Task Scheduler Service Deployment Matrix ii

6 Deploying Migration Manager for SharePoint / Migration Single Agent Deployment Two Agent Deployment Deploying Migration Manager for SharePoint / Migration Installing Migration Manager on SharePoint 2007/2010 Farms. 42 Deploying Migration Manager for SharePoint Migration. 43 Installing Migration Manager on SharePoint 2007 Farm Installing Migration Manager Extension Web Service Deploying Service Using MSI Package: Deploying Service Using PowerShell Scripts: PowerShell Execution Policy Deploying Service Using Native SharePoint 2010 Tools:. 48 Upgrading Extension Service Installing Migration Manager on SharePoint Server Installing Quest Management Console for SharePoint Installing Migration Manager for SharePoint Installing to a Pre-Created Database Adding SharePoint Farms Upgrading Migration Manager Upgrading Web Console Upgrade for / Migration Upgrade for Migration Installing Update Upgrade for Migration Managing Licenses Viewing Configuration Working with Migration Manager for SharePoint 61 Getting Started Delegating Access to Web Console Migrating SharePoint 2003 to 2007/2003 to Choosing Between Migration Job Options Creating Migration Jobs Creating Job for Site Migration Creating Job for List Migration Migration Job Details Managing Migration Jobs Managing a Job iii

7 iv Managing Multiple Jobs Monitoring Migration Jobs State Report Issue Report Agents Report Web Part Migration Configuring Stored Credentials Migration Jobs Views Migration Job Lifecycle Configuring Migration Hours Target Version Selection Synchronizing Content SharePoint Portal Site and Areas Migration Migrate SharePoint 2003 Portal Site to a New Site Collection 97 Migrate Portal Site/Sub-area to a Site Migrate Sub-area to a New Site Collection Permission Migration for Custom Portal Template SharePoint Site Template Mapping Transforming a Custom SharePoint 2003 Site into a Standard SharePoint 2007/2010 Site Transforming a Standard SharePoint 2003 Site into a Custom SharePoint 2007/2010 Site How Site Template Mapping Works SharePoint List Template Mapping Setting Mapping Rules Mapping of Domains and Users User Mapping Domain Mapping Firewall Configuration Single Agent Deployment Two Agents Deployment Migrating SharePoint 2007 to 2007/2010 to Choosing Between Migration Job Options Creating Migration Jobs Creating Job for Site Migration Creating Job for List Migration Migration Job Details Managing Migration Jobs Managing a Job

8 Managing Multiple Jobs Monitoring Migration Jobs State Report Issue Report Agents Report Migration Jobs Views Migration Job Lifecycle Synchronizing Content Full Resync Incremental Sync Exclude feature from migration ( or ) Migrating SharePoint 2007 to Choosing Between Migration Job Options Creating Migration Jobs Creating Job for Site Migration Creating Job for List Migration Migration Job Details Managing Migration Jobs Managing a Job Managing Multiple Jobs Monitoring Migration Jobs State Report Issue Report Migration Jobs Views Migration Job Lifecycle Configuring Migration Hours Migration Extensions for SharePoint Audit Metadata Site Regional Settings Site Theme Site Logo Features Activation Alerts Migration Taxonomy Mapping Synchronizing Content Mapping 2007 to 2010 Templates Site Template Mapping List Template Mapping Allowed Trasformation of List Templates v

9 Mapping of Domains and Users User Mapping Domain Mapping Disable Features Activation Taxonomy Mapping Appendices 181 Appendix A: Importing Jobs from CSV Files CSV File Format Importing Jobs Appendix B: Permission Migration SharePoint 2003 Permission Migration Site Permission Migration List Permission Migration Mapping the Source SharePoint 2003 Permissions to the Target SharePoint 2007/2010 Permissions Permission Migration Disabled SharePoint 2007 to 2007/2010 to 2010 Permission Migration. 186 Site Permission Migration List Permission Migration SharePoint 2007 to 2010 Permission Migration Permission Levels Users and Groups Permissions Appendix C: Checking Database Connection with ODBC Appendix D: Log Files Location Appendix E: Setting Required Permissions Granting the Log on As a Service Right Granting Local Administrator Rights Setting Permissions on SQL Databases Adding User to the Farm Administrators SharePoint SharePoint Adding User to Site Collection Administrators SharePoint SharePoint Appendix F: Discovery Issues Lack of Permissions Firewall Blocks SharePoint Server Install QMC locally to add a farm vi

10 1.0 About Quest Software, Inc. Now more than ever, organizations need to work smart and improve efficiency. Quest Software creates and supports smart systems management products-helping our customers solve everyday IT challenges faster and easier. Visit for more information. Contacting Quest Software Mail: Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA USA Web site: Refer to our Web site for regional and international office information. 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 Support- Link, our self-service portal. Visit SupportLink at 1

11 From SupportLink, you can do the following: Retrieve thousands of solutions from our online Knowledgebase Download the latest releases and service packs Create, update and review Support cases View the Global Support Guide for a detailed explanation of support programs, online services, contact information, policies, and procedures. The guide is available at: 2 Chapter 1. About Quest Software, Inc.

12 2.0 General Information About Quest Migration Manager for SharePoint 3.2 Quest Migration Manager for SharePoint provides a reliable solution to reorganize, consolidate, upgrade and migrate SharePoint content. The tool helps organizations: Migrate and consolidate SharePoint 2003 content to SharePoint 2010 or SharePoint 2007 running on new hardware. Migrate SharePoint 2007 sites to a new SharePoint 2010 installation. Reorganize SharePoint 2007 and SharePoint 2010 site structure to streamline information access, optimize content storage and enhance recovery time objectives. Consolidate SharePoint content from scattered WSS 3.0 or MOSS installations to a central managed location. Consolidate SharePoint content from scattered SharePoint Foundation 2010 or SharePoint Server 2010 installations to a central managed location. Minimize impact on the production systems and end users by scheduling resource-intensive migration tasks for off-peak hours. 3

13 Configure and monitor content migration tasks remotely in a web browser (all major browsers are supported). 4 Chapter 2. General Information

14 Major Features General Features Facilitates migration project management with pre-migration assessment, migration job controls, real-time progress reporting and scheduling Supports the following versions of Microsoft SharePoint: Windows SharePoint Services 2.0 and 3.0, SharePoint Portal Server 2003, Office SharePoint Server 2007, SharePoint Foundation 2010 and SharePoint Server 2010 Provides a web-based console that can be accessed from any web browser Allows you to create migration jobs automatically by means of importing the job definitions stored in a CSV (comma-separated values) file. SharePoint Migrate SharePoint 2010 sites including content, metadata and security settings to the new platform Reorganize existing SharePoint 2010 site structure during migration Synchronize post-migration changes of the source SharePoint 2010 site content to the target sites SharePoint Migrate SharePoint 2007 sites including content, metadata and security settings to the new platform Reorganize existing SharePoint 2007 site structure during migration Synchronize post-migration changes of the source SharePoint 2007 site content to the target sites Preserve the look and feel settings of the SharePoint 2007 sites Migrate web part pages including layout and web parts Major Features 5

15 SharePoint / Copy SharePoint 2007/2010 sites including content, security settings and look and feel Synchronize changes made to the source SharePoint 2007/2010 sites, lists and document libraries after they have been migrated to a new location Reorganize existing site structure Target specific content databases to optimize site storage Transfer SharePoint content within a single server and between Share- Point farms. SharePoint / Migrate SharePoint 2003 sites including content and security settings to the new platform Reorganize existing SharePoint 2003 site structure during migration Synchronize post-migration changes of the source SharePoint 2003 site content to the target sites Migrate web part pages including layout and web parts. Supported SharePoint Features SharePoint 2003 to 2007/2003 to 2010 Migration SharePoint 2007 to 2007 (SharePoint 2010 to 2010) Migration SharePoint 2007 to 2010 Migration SharePoint 2003 to 2007/2003 to 2010 Migration Migration Manager preserves the following during migration: 1. List items with metadata 6 Chapter 2. General Information

16 2. Attachments 3. Discussion threads 4. Documents with metadata 5. Document versions Note: By default, all versions are transferred, but you can limit the maximum number of document versions migrated in the product configuration. 6. Folders 7. Authorship (Created By/Modified By) for content 8. Lists Generic lists (Contacts, Tasks, Events, Custom List, etc.) Document libraries Issues lists Discussion boards Surveys Custom list definitions Note: To migrate lists based on custom list templates/definitions you might need to adjust list template mapping in the product configuration. 9. List settings General settings (title, description, approval, versioning, Quick Launch) List columns (types, descriptions, etc.) List views Note: Only Shared views are migrated. 10. List permissions (unique/inherited) 11. Sites Team sites Supported SharePoint Features 7

17 Document workspaces Meeting workspaces Custom site templates Note: To migrate sites based on custom site templates/definitions you might need to adjust web template mapping in the product configuration. 12. Site settings General settings (title, description) 13. Site permissions Permission mode (unique/inherited) Site groups permissions and membership 14. Site users 15. SPS 2003 portal sites Portal site areas Area hierarchy Portal listings Area security permissions 16. Site collections Site collection administrators Cross-site groups SharePoint 2007 to 2007 (SharePoint 2010 to 2010) Migration Migration Manager preserves most of the content and settings of SharePoint 2007/2010 sites during migration, including content, list and site settings, site users and security permissions, site look and feel. However some information is lost during migration, including: 1. Workflow state and tasks 2. Alerts 8 Chapter 2. General Information

18 3. Check-out state 4. Recycle Bin content SharePoint 2007 to 2010 Migration Migration Manager preserves the following during migration: 1. Sites and site collections: Non-portal sites Portal sites 2. Site settings and metadata: Regional Settings (Local, Time zone) Content types Site columns Site home page Feature Activation Note: To preserve regional settings and activate features, it is required to install Migration Manager Extension Web Service. 3. Site look and feel: Visual mode Themes Images Navigation (top menu and Quick Launch) Master pages Customized pages (e.g. Quest Web Parts sample applications) Note: To preserve site theme, it is required to install Migration Manager Extension Web Service. 4. Users and security permissions: Users Supported SharePoint Features 9

19 SharePoint groups Site-, List- and Item-level permissions Permission levels (Roles) 5. Lists and libraries: List items Attachments Documents Folders Version history Audit metadata (Created/Modified By/At) List schema and views Note: To preserve audit metadata, it is required to install Migration Manager Extension Web Service. 6. Web parts Standard and 3rd Party (Quest Web Parts) Web Part Connections 7. alerts 8. SharePoint Designer workflows 10 Chapter 2. General Information

20 3.0 How Migration Manager for SharePoint Works This section contains complete information about Migration Manager for SharePoint (MMSP). Here you will find answers on what services are involved in the migration process, how they perform migration, and what permissions they require. Each service or scheduled task should be able to access the repository database and read or write the required data. Quest repository database (QMC_Repository by default) is the common storage for all migration jobs, their configuration and migration progress. At the moment there are the following parts in MMSP: Web Console SharePoint 2003 to 2007/ 2003 to 2010 Migration SharePoint 2007 to 2007/ 2010 to 2010 Migration SharePoint 2007 to 2010 Migration The Web console helps to create and manage migration jobs, view reports and job progress. MMSP has three types of migration jobs ( / , / , and ), different services are responsible for them. Let s look at each part in more detail. 11

21 Web Console The Web console is the administrative center of MMSP. You can open it in a remote browser and create and manage migration jobs. By default, all users who are Local Administrators on MMSP host can use the Web console. Refer to the Delegating Access to Web Console section for more details. Services Involved Quest.MM4SP.WebAccess is a Windows service. It supports webconsole workability. All users requests from the web-console to the repository database are performed under the Web Access service account. Quest.MM4SP.SPBrowserAgent and Quest.MM4SP.SPBrowserBroker are Windows services. They request configuration and content databases of the source and target SharePoint for information about the server farm. Architecture During installation, MMSP defines which port will be used by Web Access. Each MMSP host has the Web Access service which provides you with the web console having the URL. If MMSP instances use the same repository database, they display identical information and you can use any of them to create or manage migrations. The web console provides you with separate job wizards to create jobs for each type of migration. The job wizard helps to configure a migration job correctly. When a job is being created, the Select option displays the list of available URLs. To create this list, the Browser Broker service requests information about the existing SharePoint structure (web applications, site collections, sites and lists) on the source or target SharePoint from the Browser Agent service (Agent). If a single agent deployment is used, one Agent collects information on the structure of both the source and the target farms and should have permissions to access both farms. If a two-agent deployment is used, the Agents 12 Chapter 3. How Migration Manager for SharePoint Works

22 on the source and the target provide the information on their local farm structure, so each service should have access to the local farm. The SPBrowser services are also responsible for adding new farms to MMSP and retrieving counters required to generate the state report. Required Permissions Web Access service account: 1. Member of the Local Administrators group on the MMSP host. 2. The db_owner role for the Quest repository database. Account for SPBrowser services: 1. The Log On As Service right on the MMSP host. 2. Member of the Local Administrators group on the MMSP host. 3. The db_owner role for the Quest repository database. 4. The db_datareader role for the configuration and content databases of corresponding SharePoint farm. Note: If you have a single agent deployment, the SPBrowser services should have access to both the source and the target databases. But if you have a two-agent deployment, the source SPBrowser services should have access to the source databases, and the target services - to the target databases. Web Console 13

23 Logs Web Access service writes its logs into the following location on the corresponding MMSP host: {MMSP installation directory}\logs\web Access logs Note: If you have different instances of MMSP, log files are written to the host whose web console you are using. SPBrowser services write their logs into the following location on the corresponding MMSP host: {MMSP installation directory}\web Interface\SharePoint Browser\Logs Note: If you have a two-agent deployment of MMSP, SPBrowser logs are written to both the source and the target hosts. 14 Chapter 3. How Migration Manager for SharePoint Works

24 SharePoint 2003 to 2007/ 2003 to 2010 Migration During SharePoint 2003 to SharePoint 2007 or SharePoint 2010 migration (2003 migration), two separate actions should be performed: base content migration and web part migration. Base Content Migration During the base content migration, MMSP migrates all the content except web part pages and web parts. See Supported SharePoint Features section for more detailed information. Services Involved Quest.MM4SP.SourceService is a Windows service. It extracts content from source SharePoint 2003 servers using SQL calls to the corresponding SharePoint content databases. Quest.MM4SP.TargetService is a Windows service. It uploads content to the local SharePoint instance (2007 or 2010) using SharePoint API calls. Architecture When a migration job is created, the Source service reads content from a source SQL content database. The Source service processes one migration job at a time and starts to process a new job when all content of the fist job has been extracted. The Source and target services collaborate using MSMQ: the source service generates messages and sends them to the queue; the target service receives messages, generates SharePoint objects and uploads them using SharePoint Object Model. SharePoint 2003 to 2007/ 2003 to 2010 Migration 15

25 To perform 2003 migration, MMSP can be installed on target server only (single agent deployment) or on both servers (two-agent deployment). The following diagram displays architecture of 2003 migration for different deployment scenarios: Single agent deployment should be used if you have a single Share- Point administrative account to access both the source and target SharePoint farms. In this case MMSP is installed on the target server only and the source and target services work on the same host. The Source service extracts data from source content database remotely. You should add the source server to MMSP to perform migration. Two-agent deployment should be used if you do not have a single account to access both the source and target SharePoint farms. In this case MMSP is installed on the source and target SharePoint servers. However, all services are installed and started on every host, the source content is processed by the local Source service and the target content is uploaded by local Target service. 16 Chapter 3. How Migration Manager for SharePoint Works

26 Required Permissions Source service account: 1. The Log On As Service right on the MMSP host. 2. Member of the Local Administrators group on the MMSP host. 3. The db_owner role on Quest repository database. 4. The db_datareader role for the SharePoint 2003 content SQL databases. Target service account: 1. The Log On As Service right on the MMSP host. 2. Member of the Local Administrators group on the MMSP host. 3. The db_owner role on Quest repository database. 4. Member of the Farm Administrators group in the target SharePoint farm. 5. The db_owner permissions for the target SharePoint content databases. 6. The Site Collection Administrator permissions in the target site collections (per site collection) OR Full Control granted via the Policy for Web application (for all site collections within the web application). Logs 2003 migration writes log files into the following location on the corresponding MMSP host: {MMSP installation directory}\logs\2003\{job Name} Note: If you have a two-agent deployment, the source logs are on the source MMSP host, and the target logs are on the target host. Web Part Migration Starting from Migration Manager v3.0 the Quest.MM4SP.CustomPageMigrator service is responsible for the SharePoint 2003 to 2007/ 2003 to 2010 Migration 17

27 web part migration. Refer to the following section for more details. During base content migrations, web parts for home page and web part pages from document libraries are not migrated. They are migrated in a separate web part migration job. Starting from Migration Manager v3.0 web part migration is initiated automatically by the Quest.MM4SP.CustomPageMigrator service. Services and Scheduled Tasks Involved Quest.MM4SP.CustomPageMigrator is a Windows service. It tracks for a new jobs to process, generates migration pairs and runs migration script for the job. Architecture The Quest.MM4SP.CustomPageMigrator service works from the target host. It tracks if there is a job which completes initial migration and has not been processed yet by the service. If the job is found, the Custom- PageMigrator generates pairs for a web part migration and writes them to the Repository database. When all pairs are generated for all sites and document libraries, it runs a script to perform web part migration for the pairs. The script is running under the CustomPageMigrator user account. The script accesses source server remotely and reads web part pages and web parts using the web service and uploads them to target. Only one migration script is running at the moment, so only one job is processed. The CustomPageMigrator service tracks if the script execution is completed, sets the Completed state for the job and runs the script for a new job if needed. Required Permissions Custom Page Migrator account: 1. Member of the Local Administrators group on the MMSP host. 2. The db_owner permissions for the target SharePoint content databases. 18 Chapter 3. How Migration Manager for SharePoint Works

28 3. The Site Collection Administrator permissions in the target site collections (per site collection) OR Full Control granted via the Policy for Web application (for all site collections within the web application). 4. Member of the Administrator site group on the source SharePoint 2003 sites. To perform web part migration in two-agent deployment, stored credentials should be configured. Refer to the Configuring Stored Credentials section. Logs Custom Page Migrator writes logs into the following locations on MMSP host: The main service log is written to the following file on the target MMSP host: {MMSP installation directory}\logs\2003\custompagemigratorsrv.log During the job processing the migration log is written into the corresponding job folder on the target MMSP host: {MMSP installation directory}\logs\2003\{jobname}\webparts.log Note: Web part migration logs are always written to the target MMSP host. SharePoint 2003 to 2007/ 2003 to 2010 Migration 19

29 SharePoint 2007 to 2007/ 2010 to 2010 Migration SharePoint 2007 to 2007/ migration has different migration mechanism and all content is migrated simultaneously. Services Involved Quest.MM4SP.2k7Source is a Windows service running on the source MMSP host. It exports data to be migrated from source SharePoint 2007 using Content Migration API. Quest.MM4SP.2k7Target is a Windows service running on the target MMSP host. It imports content to the SharePoint 2007 server using Content Migration API and stsadm utility. Architecture To perform / migration, MMSP uses Content Migration API. When migration job is created, the 2k7Source service uses export command and stores exporting results in the qmmsp-export$ shared folder on the source MMSP host. The 2k7Source service processes one migration job at a time and starts to process a new job when all content of the fist job has been exported. 20 Chapter 3. How Migration Manager for SharePoint Works

30 Temporary Storage of Exported Content Each time the 2k7Source service is started, it creates the qmmsp-export$ shared folder. When a job is created and migration is started, the content intended for migration is exported to a subfolder of this shared folder. The subfolder is named after migration job. By default, the export folder is located in the {MMSP installation folder}\web Interface\Migration 2007\Export folder. To redirect the content to be exported, perform the following: 1. Go to the source front-end host where the source 2007/2010 migration agent is installed. 2. Open the ExportFolderPath.py file located in {MMSP installation folder}\web Interface\Migration The original folder path and the instructions on how to modify it are in the file. 3. Make your changes, save the file and restart the 2k7Source service. By default, the folder is created with the Read/Write access to Everyone. You can restrict permissions to the service accounts if you wish using the Sharing and Security options from the Folder properties. Note: When the job is completed, the exported content stays on the disk. This content is automatically removed from the disk on the source server when the job is deleted. When export completes, the 2k7Target service reads data from the shared folder, processes manifest.xml and imports content to target. If you perform a farm re-organization, the source and the target services work on the same server. SharePoint 2007 to 2007/ 2010 to 2010 Migration 21

31 The following diagram displays architecture of / migration for intra-farm migration: Note: If you need to migrate content from one farm to another, MMSP should be installed to a WFE on each farm. Both instances of MMSP should use the same Repository database. Required Permissions 2k7Source service account: 1. The db_owner role for the Quest repository database. 2. Member of the Local Administrators group on the MMSP host. 3. The Site Collection Administrator permissions in the source site collections (per site collection) OR Full Control granted via the Policy for Web application (for all site collections within the web application) 2k7Target service account: 1. The db_owner role for the Quest repository database. 2. Member of the Local Administrators group on the MMSP host. 3. Member of the Farm Administrators group in the SharePoint 2007 farm. 4. The Site Collection Administrator permissions in the target site collections (per site collection) OR Full Control granted via the Policy for Web application (for all site collections within the web application) 22 Chapter 3. How Migration Manager for SharePoint Works

32 Logs / migration writes log files into the following location on the corresponding MMSP host: {MMSP installation directory}\logs\2007\{job Name} Note: If you have a two-agent deployment, the source logs are on the source MMSP host and the target logs are on the target host. SharePoint 2007 to 2007/ 2010 to 2010 Migration 23

33 SharePoint 2007 to 2010 Migration SharePoint 2007 to 2010 migration uses new Client Object Model of Share- Point Migration Manager accesses target SharePoint 2010 remotely, that means it should be installed on the source farm. Refer to the Deploying Migration Manager for SharePoint Migration section for more detailed information. However, an extension service should be installed on target to be able to migrate all versions of documents and items correctly. Services Involved Quest.MM4SP.Migration2010 is a Windows service running on the source MMSP host. It extracts data to be migrated from source Share- Point 2007 using Content Migration API. Migration Manager Extension Web Service is a custom web service running on the target MMSP host. It facilitates migration of certain types of content and metadata (e.g. document versions with full audit metadata). Architecture When processing a migration job, Migration Manager iterates through the selected sites and lists, reads each source SharePoint object. Then the object is copied to a new location on the target SharePoint 2010 server using a combination of remote calls to the native SharePoint 2010 APIs (Client Object Model and SharePoint Web Services) and the Migration Manager Extension Web Service. 24 Chapter 3. How Migration Manager for SharePoint Works

34 The following diagram displays architecture of migration: Required Permissions Quest.MM4SP.Migration2010 account: 1. The Log On As Service right on the MMSP host 2. The db_owner role for the Quest repository database. 3. The db_owner role for the source SharePoint content databases 4. Member of the Local Administrators group on the MMSP host. 5. Member of the Farm Administrators group in the source and target SharePoint farm. 6. The Site Collection Administrator permissions in the source and target site collections (per site collection) OR Full Control granted via the Policy for Web application (for all site collections within the web application). Migration Manager Extension Web Service is deployed as a solution by a target farm administrator and running in SharePoint context. SharePoint 2007 to 2010 Migration 25

35 Logs migration writes log files into the following location on the source SharePoint 2007 server: {MMSP installation directory}\logs\2010\{job Name} 26 Chapter 3. How Migration Manager for SharePoint Works

36 4.0 Deploying Migration Manager System Requirements Before installing Migration Manager for SharePoint make sure the following system requirements are met: SharePoint 2003 Server 1. Migration Manager supports migration from one of the following Share- Point version: Microsoft Windows SharePoint Services 2.0 SP2 or later SharePoint Portal Server 2003 SP2 or later 2. 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: SharePoint 2007 Server Migration Manager supports the following SharePoint versions: Microsoft Office SharePoint Server 2007 Windows SharePoint Services

37 SharePoint 2010 Server Migration Manager supports the following SharePoint versions: Microsoft SharePoint Server 2010 SharePoint Foundation 2010 Migration Manager Host Server Migration Manager for SharePoint needs to be installed on a member Share- Point server in each SharePoint server farm to migrate content to or from. The SharePoint server must meet the following system requirements to run Migration Manager: 1. Platform: Intel x86 or x64 (recommended) 2. Operating system: Microsoft Windows Server 2003 SP2 or later Windows Server 2008 Windows Server 2008 R2 3. The following Microsoft services should be installed and running: Microsoft Message Queuing Service Task Scheduler service Server service (for / migration) Workstation service (for / migration) 4. Access to an instance of Microsoft SQL Server to host a repository database for Migration Manager: 5. Other: Microsoft SQL Server 2005 SP1 or later SPs Microsoft SQL Server 2008 Microsoft.Net 3.0 Framework Microsoft.Net 3.5 Framework (for migration) 28 Chapter 4. Deploying Migration Manager

38 Required Permissions Permissions Matrix Depending on the migration scenario, different services and scheduled tasks will be involved in the migration job processing. The permissions matrix helps you to understand what permissions are required to work with Migration Manager. Note: Farm Administrators can create and manage site collections but cannot administer individual sites or site content unless they take ownership of the site. Site Collection Administrators can perform all administration tasks for sites within the site collection but cannot create site collections. Full Access via Policy for Web Application - account has the Site collection administrator rights for all site collections within a web application. For detailed information, please refer to the Permissions in Detail section. Required Permissions 29

39 Permissions in Detail The user installing the product (Installation User) must have the following permissions: OR Member of the Local Administrators group on the computer where Migration Manager for SharePoint is installed (MMSP host) dbcreator role on the SQL server where the Quest repository database will be created db_owner role for the existing database to be used as Quest repository database. Depending on the migration scenario, different services and scheduled tasks will be involved in the migration job processing. By default, all the services and scheduled tasks are run under the account specified during the product setup. If you need to use an alternative account to perform migration, please refer to the detailed information on permissions for each Migration Manager component. Refer to the Appendix E: Setting Required Permissions for detailed information on how to set the permissions. By default, only local administrators of the server are allowed to access the Migration Manager console. To grant other users and groups access to the console, you can adjust a configuration file. For more information, please refer to Delegating Access to Web Console. 30 Chapter 4. Deploying Migration Manager

40 Services Responsible for Migration Manager User Interface Workability The following permissions are required for UI services: SERVICE REQUIRED PERMISSIONS RUNNING ON Web Access (Quest. The Log On As Service right The target (one MM4SP.WebAccess) on the MMSP host agent deployment) Member of the Local Administrators group on the MMSP OR host The source and The db_owner role for the the target (two Quest repository database agent deploy- Browser Agent (Quest.MM4SP.SP BrowserAgent), Browser Broker (Quest.MM4SP.SP BrowserBroker) The Log On As Service right on the MMSP host Member of the Local Administrators group on SharePoint servers involved in migration The db_owner role for the Quest repository database The db_datareader role for the source and/or the target SharePoint configuration and content databases ment) The target (one agent deployment) OR The source and the target (two deploy- agent ment) Services Responsible for 2003 to 2007/2003 to 2010 Migration The following permissions are required for services: Required Permissions 31

41 Target Service (Quest. MM4SP.TargetService) The Log On As Service right on the MMSP host Member of the Local Administrators group on the MMSP host The db_owner role for the Quest repository database The db_datareader role for the SharePoint 2003 content databases The Log On As Service right on the MMSP host Member of the Local Administrators group on the MMSP host The db_owner role for the Quest repository database The db_owner role for the target SharePoint content databases Member of the Farm Administrators group in the target SharePoint farm The Site Collection Administrator permissions in the target site collections (per site collection) OR Full Control granted via the Policy for Web application (for all site collections within the web application) SERVICE REQUIRED PERMISSIONS RUNNING ON Source Service The target (one (Quest.MM4SP.Source Service) agent deployment) OR The source 2003 (two deploy- server agent ment) The target 32 Chapter 4. Deploying Migration Manager

42 SERVICE REQUIRED PERMISSIONS RUNNING ON Quest Custom Page Member of the Local Administrators The target Migrator (Quest. group on the MMSP MM4SP.CustomPage Migrator) host The db_owner role for the target SharePoint content databases The Site Collection Administrator permissions in the target site collections (per site collection) OR Full Control granted via the Policy for Web application (for all site collections within the web application) Member of the Administrator site group on the source Share- Point 2003 sites Required Permissions 33

43 Services Responsible for 2007 to 2007/ 2010 to 2010 Migration The following permissions are required for services: SERVICE REQUIRED PERMISSIONS RUNNING ON 2k7 Source (Quest. The db_owner role for the The source MM4SP.2k7Source) Quest repository database Member of the Local Administrators group on the MMSP host The Site Collection Administrator permissions in the source site collections (per site collection) OR Full Control granted via the Policy for Web application (for all site collections within the web appli- 2k7 Target (Quest. MM4SP.2k7Target) cation). The db_owner role for the Quest repository database Member of the Local Administrators group on the MMSP host Member of the Farm Administrators group in the target SharePoint farm The Site Collection Administrator permissions in the target site collections (per site collection) OR Full Control granted via the Policy for Web application (for all site collections within the web application) The target 34 Chapter 4. Deploying Migration Manager

44 Services Responsible for 2007 to 2010 Migration The following permissions are required for services: SERVICE REQUIRED PERMISSIONS RUNNING ON Migration 2010 The Log On As Service right The source (Quest.MM4SP. Migration2010) on the MMSP host Member of the Local Adminis- trators group The db_owner role for the Quest repository database The db_owner role for the source SharePoint content databases Member of the Farm Administrators group in the source and target SharePoint farm The Site Collection Administrator permissions in the source and target site collections (per site collection) OR Full Control granted via the Policy for Web application (for all site collections within the web application). Required Permissions 35

45 Additional Services and Scheduled Tasks The following permissions are required for services: SERVICE REQUIRED PERMISSIONS RUNNING ON Service Monitor Member of the Local Administrators The source and (Quest.MM4SP.Service group on the MMSP host the target The following permissions are required for scheduled tasks: SCHEDULED TASK REQUIRED PERMISSIONS RUNNING ON Quest Compress Old Member of the Local Administrators group on the MMSP the The source and Logs target Quest Proxy SharePoint host The account used to run this scheduled task must have the same permissions as the Target Service The source and the target. 36 Chapter 4. Deploying Migration Manager

46 Pre-installation Steps Before installing Migration Manager for SharePoint, install Microsoft Message Queuing (required for / migration only) and check the Task Scheduler service is running. Installing Message Queuing on Windows Server 2003 To install Microsoft Message Queuing Service on Windows Server 2003, perform the following steps: 1. In the Control Panel, double-click Add or Remove Programs. 2. Click Add/Remove Windows Components in the left pane. 3. In the Windows Components wizard, select Application Server, and then click Details. 4. Check Message Queuing, click OK, and then click Next to complete the installation. For more information on installing Microsoft Message Queuing on Windows Server 2003, please follow the link: Installing Message Queuing on Windows Server 2008 To install Microsoft Message Queuing Service on Windows Server 2008, perform the following steps: 1. Click Start, point to Programs, point to Administrative Tools, and then click Server Manager. 2. Click Add Features to start the Add Features Wizard. Pre-installation Steps 37

47 3. Expand Message Queuing, expand Message Queuing Services, and then select check the Message Queuing Server option. 4. Click Next, and then click Install. 5. If you are prompted to restart the computer, click OK to complete the installation. For more information on installing Microsoft Message Queuing on Windows Server 2008, please follow the link: Starting the Task Scheduler Service To make sure the Task Scheduler service is running, open the services snap-in from Start Control Pane Administrative Tools, or run the services.msc command. 38 Chapter 4. Deploying Migration Manager

48 Deployment Matrix To perform different migration scenarios, Migration Manager requires different deployments. The deployment matrix helps you to understand where to install Migration Manager for a particular scenario. SOURCE\TARGET SHAREPOINT 2010 SHAREPOINT 2007 SHAREPOINT 2003 Install MM on 2010 target Install MM on 2007 target Install MM on 2003 source (optional) Install MM on 2003 See more >> source (optional) SHAREPOINT 2007 Install MM on 2007 source Install Extension service on 2010 target See more >> SHAREPOINT 2010 Install MM on 2010 source Install MM on 2010 target (use the same repository database) See more >> See more >> Install MM on 2007 source Install MM on 2007 target (use the same repository database) See more >> Not Supported Deployment Matrix 39

49 Deploying Migration Manager for SharePoint / Migration This section describes how to deploy Quest Migration Manager for SharePoint to perform migration from SharePoint 2003 farm to a new SharePoint 2007 or SharePoint 2010 farm. Refer to Deployment Matrix if you want to perform different migration scenario. Basic deployment scenario includes installation of Migration Manager to a server on target SharePoint farm. Before installing Migration Manager, make sure the SharePoint servers meet the Migration Manager system requirements and all the prerequisite components are installed on the servers where you will install Migration Manager for SharePoint. Refer to the System Requirements and Pre-installation Steps sections for detailed information. Single Agent Deployment Single agent deployment can be used if you have a single administrative account to access both source and target SharePoint farms. 1. Install Migration Manager on the target SharePoint farm. Use instructions in the Installing Migration Manager on SharePoint Server section and provide the following information to the setup program: Repository Database - specify the SQL server (instance) to host the repository database and the database name to create (QSP_Repository by default) Migration Manager Service account - specify the SharePoint administrative account. Refer to the Permissions in Detail section to make sure the account has all permissions required for source and target services. 2. Grant the Migration Manager Service account the db_owner rights on the Quest Repository database. 3. The source and target SharePoint farms should be added to Migration Manager. Local SharePoint farm is automatically added to Migration Manager during installation. If the auto discover has failed by some reason or to add the source SharePoint farm, you can use the Add Farm 40 Chapter 4. Deploying Migration Manager

50 wizard (for more information, refer to the Adding SharePoint Farms section). Two Agent Deployment Two-agent deployment can be used if you do not have a single account to access both the source and target SharePoint farms or there are multiple SharePoint 2003 farms that you need to consolidate content from. 1. Install Migration Manager on the target SharePoint farm. Use instructions in the Installing Migration Manager on SharePoint Server section and provide the following information to the setup program: During the installation specify the following parameters: Repository Database - specify the SQL server (instance) to host the repository database and the database name to create (QSP_Repository by default) Migration Manager Service account - specify the administrative account for the local SharePoint farm. Refer to the Permissions in Detail section to make sure the account has all permissions required for the farm. It is recommended to use the existing Share- Point farm administrator account. 2. Install Migration Manager on the source SharePoint 2003 farm. Use instructions in Installing Migration Manager on SharePoint Server section and provide the following information to the setup program: Repository Database - specify the same repository database that you specified in Step 1 Note: Both installations of Migration Manager should use the same repository database Migration Manager Service account - specify the administrative account for the local SharePoint farm. Refer to the Permissions in Detail section to make sure the account has all permissions required for the farm. It is recommended to use the existing Share- Point farm administrator account. 3. Grant the accounts specified in step 1 and 2 the db_owner rights to the repository database created in step 1. Deploying Migration Manager for SharePoint / Migration 41

51 4. The source and target SharePoint farms should be added to Migration Manager. Local SharePoint farms are automatically added to Migration Manager during installation. In case the auto discover has failed by some reason, you can add source and target SharePoint farms manually (for more information, refer to the Adding SharePoint Farms section). Deploying Migration Manager for SharePoint / Migration This section describes how to deploy Quest Migration Manager for SharePoint to perform reorganization of your SharePoint 2007 or SharePoint 2010 farm or migrate to a new farm with the same version. Refer to Deployment Matrix if you want to perform different migration scenario. The deployment scenario includes installation of Migration Manager pointing to the same repository database to all SharePoint farms involved in migration. Before installing Migration Manager, make sure the SharePoint 2007/2010 servers meet the Migration Manager system requirements and all the prerequisite components are installed on the servers where you will install Migration Manager for SharePoint. Refer to the System Requirements section for more detailed information. Installing Migration Manager on SharePoint 2007/2010 Farms Install and configure Migration Manager for SharePoint on all SharePoint farms that you will migrate sites to or from. Perform the following steps: 1. Install Migration Manager on each SharePoint farm. Use instructions in Installing Migration Manager on SharePoint Server section and provide the following information to the setup program: Repository Database - specify the SQL server (instance) to host the repository database and the database name to create (QSP_Repository by default). Choose to create a new database when installing Migration Manager on the first SharePoint farm and specify this database for all other Migration Manager installations on additional farms. 42 Chapter 4. Deploying Migration Manager

52 Note: For multi-agent installation of Migration Manager you should use the same repository database. Migration Manager Service account - specify the SharePoint administrative account. Refer to the Permissions in Detail section to make sure the account has all permissions required for the local SharePoint 2007/2010 farm. 2. Grant the db_owner rights on the Quest Repository database to all the Migration Manager service accounts you used to install Migration Manager in Step To allow Migration Manager to migrate content, your source and target SharePoint farms should be added to Migration Manager. Local Share- Point farms are automatically added to Migration Manager during Quest Management Console installation. If the auto discover has failed by some reason, you can SharePoint farms manually (for more information, refer to the Adding SharePoint Farms section). Deploying Migration Manager for SharePoint Migration This section describes how to deploy Quest Migration Manager for SharePoint to perform migration from SharePoint 2007 farm to a new SharePoint 2010 farm. Refer to Deployment Matrix if you want to perform different migration scenario. This deployment scenario includes installation of Migration Manager to the source SharePoint 2007 farm and the Extension service to the target 2010 farm. Before installing Migration Manager, make sure the SharePoint servers meet the Migration Manager system requirements and all the prerequisite components are installed on the servers where you will install Migration Manager for SharePoint. Refer to the System Requirements section for more detailed information. Deploying Migration Manager for SharePoint Migration 43

53 Installing Migration Manager on SharePoint 2007 Farm Install and configure Migration Manager for SharePoint on the source Share- Point 2007 farm (any server with the Web Front End role). Perform the following steps: 1. Install Migration Manager on the source SharePoint farm. Use instructions in Installing Migration Manager on SharePoint Server section and provide the following information to the setup program: Repository Database - specify the SQL server (instance) to host the repository database and the database name to create (QSP_Repository by default). Choose to create a new database when installing Migration Manager on the first SharePoint 2007 farm and specify this database for all other Migration Manager installations on additional farms. Migration Manager Service account - specify the SharePoint administrative account. Refer to the Permissions in Detail section to make sure the account has all permissions required for the local SharePoint 2007 farm. 2. Grant the db_owner rights on the Quest Repository database to the Migration Manager service account you used to install Migration Manager in Step Install the Migration Manager Extension Web Service on the target SharePoint 2010 server farm. Follow instructions in the Installing Migration Manager Extension Web Service section. 4. To allow Migration Manager to migrate content, your source and target SharePoint farms should be added to Migration Manager. The local SharePoint 2007 farm is automatically added to Migration Manager during the installation. To add the target SharePoint 2010 server, refer to the Adding SharePoint Farms section. Installing Migration Manager Extension Web Service You can perform migration without installing the Extension service. In this case, some data and settings are not preserved during migration. Refer to the Migration Extensions for SharePoint 2010 section for more detailed information. 44 Chapter 4. Deploying Migration Manager

54 To install the service, you should deploy the Quest.MMExtension.wsp solution on the target SharePoint server. The service can be deployed using one of the following ways: Deploying Service Using MSI Package: Deploying Service Using PowerShell Scripts: Deploying Service Using Native SharePoint 2010 Tools: Deploying Service Using MSI Package: To deploy Migration Manager Extension Web service: 1. Locate the quest.mmextension.msi package in one of the following places: The Migration Manager for SharePoint installation CD: CD\Migration Manager for SharePoint\Extension Service for SharePoint The {MMSPInstallationFolder}\Scripts\MMExtension\ folder on the source server. 2. Run the msi as Administrator on the target SharePoint 2010 server and wait while it completes installation. Warning: PowerShell Execution Policy may cause installation failure. Refer to the PowerShell Execution Policy section for more details. Note: If the SharePoint 2010 Administration service is stopped, it is started during installation. To remove the Migration Manager Extension Web service installed via msi, uninstall Quest Migration Extensions for SharePoint 2010 product. To check if the solution is deployed, perform the following steps: 1. Run Central Administration. 2. Select System Settings > Farm Management > Manage farm. Deploying Migration Manager for SharePoint Migration 45

55 3. Make sure the quest.mmextension.wsp solution is in the list and its status is set to Deployed. Deploying Service Using PowerShell Scripts: To install Migration Manager Extension Web service: 1. Copy the MMExtension folder located in the {MMSPInstallation- Folder}\Scripts\ to the target farm. 2. Run SharePoint 2010 Management Shell under the farm administrator account on the target server by selecting Start > Microsoft Share- Point 2010 Products > SharePoint 2010 Management Shell. 3. In the PowerShell console, type the following: &"{PathToMMExtensionFolder}\install-mmextension.ps1" "{PathToMMExtensionFolder}\Quest.MMExtension.wsp" Warning: PowerShell Execution Policy may cause installation failure. Refer to the PowerShell Execution Policy section for more details. E.g. The MMExtension folder is copied to the C: drive. You should run the following: PS C:\Users\administrator.KARELIA> &"C:\MMExtension\installmmextension.ps1" "C:\MMExtension\quest.mmextension.wsp" 4. Wait for the script results. To remove Migration Manager Extension Web service using PowerShell scripts: 46 Chapter 4. Deploying Migration Manager

56 1. Run SharePoint 2010 Management Shell under the farm administrator account on the target server by selecting Start > Microsoft Share- Point 2010 Products > SharePoint 2010 Management Shell. 2. In the PowerShell console, type the following: &"{PathToMMExtensionFolder}\uninstall-mmextension.ps1" E.g. PS C:\Users\administrator.KARELIA> &"C:\MMExtension\uninstallmmextension.ps1" 3. Wait for the script results. PowerShell Execution Policy PowerShell Execution Policy may prevent Migration Manager Extension Web Service from deploying if you install it from the msi package or the Power- Shell scripts. If the policy is set to Restricted, the installation fails. At least the AllSigned policy should be set. Refer to the following article for detailed information on available policies. To change the policy, execute the following cmdlet in PowerShell or Share- Point 2010 Management Shell: Set-ExecutionPolicy AllSigned The following policies can be used: AllSigned, RemoteSigned, Unrestricted. Deploying Migration Manager for SharePoint Migration 47

57 When the AllSigned policy is set, you will be asked if you trust Quest Software certificate: When you accept the certificate, the installation continues. Deploying Service Using Native SharePoint 2010 Tools: The solution package (Quest.MMExtension.wsp) can be found in the following locations: on the Migration Manager for SharePoint installation CD - CD\Migration Manager for SharePoint\Extension Service for SharePoint 2010 in the {MMSPInstallationFolder}\Scripts\MMExtension folder on the server where Migration Manager is installed. SharePoint 2010 Management Shell (PowerShell console) Installation: Add-SPSolution -LiteralPath "{SolutionPath}\Quest.MMExtension.wsp" Install-SPSolution -Identity Quest.MMExtension.wsp -AllWebApplication -GACDeployment -force Uninstallation: Uninstall-SPSolution -Identity Quest.MMExtension.wsp -Confirm:$false -AllWebApplication 48 Chapter 4. Deploying Migration Manager

58 STSADM Remove-SPSolution -Identity Quest.MMExtension.wsp -Confirm:$false Installation: -o addsolution -filename "{SolutionPath}\Quest.MMExtension.wsp" -o deploysolution -name Quest.MMExtension.wsp -allcontenturls -immediate -allowgacdeployment Uninstallation: -o retractsolution -name Quest.MMExtension.wsp -allcontenturls -immediate -o deletesolution -name Quest.MMExtension.wsp Upgrading Extension Service You should update the service every time you update Migration Manager. In case you install the service using msi package, it will be updated automatically. If you install the extension serice using the script or native tools, uninstall (delet) the existing solution package, and then install the new version. Installing Migration Manager on SharePoint Server To install Migration Manager for SharePoint: 1. Log in as the Installation User to the selected SharePoint server. 2. Run installation from autorun.exe on the CD package. Note: If the installation from autorun does not work, run the Migration Manager for SharePoint\setup.exe file The Quest Management Console Setup wizard starts, which installs the common components and configuration for Quest SharePoint products. Installing Migration Manager on SharePoint Server 49

59 Installing Quest Management Console for SharePoint Perform the following steps: 1. On the Welcome screen, click Next. 2. On the Configuration Database page, specify the database to be used to store the Migration Manager data (Quest Repository Database). For your first installation of Migration Manager specify to create a new database. When installing additional Migration Manager instances, which will share the same configuration, specify the database created during the installation of the first Migration Manager instance. Note: If SQL Server is running on the local computer, specify the local computer name to be used as the Quest repository database. Note: If your DBA created a database to be used as the Quest repository database, please refer to the Installing to a Pre-Created Database section. 3. On the Ready to Install the Application page, click Next to begin installation. 4. Click Finish. After Quest Management Console is installed, Quest Migration Manager for SharePoint Setup wizard starts automatically. Installing Migration Manager for SharePoint Follow the Quest Migration Manager for SharePoint Setup wizard steps: 1. On the Welcome screen, click Next. 2. On the End-User License Agreement step, select the I accept the the terms in the License Agreement radio button and click Next. 3. On the Select Features screen, either accept the default installation path or click Browse to specify an alternate installation folder, and then click Next. 50 Chapter 4. Deploying Migration Manager

60 4. On the Service Account Credentials screen, specify the account to run Migration Manager services and tasks (Migration Manager Service account). Click Next. 5. Click Finish once the installation process is completed. 6. After Migration Manager for SharePoint Setup wizard completes, grant the db_datareader and db_datawriter roles on the Quest repository database to the target service account. Installing Migration Manager on SharePoint Server 51

61 Installing to a Pre-Created Database If you do not have permissions to create databases on the SQL Server, you may request an empty database from your database administrator. To use the database with Migration Manager, follow the instructions below when you install the first instance of Migration Manager (when you deploy additional instances of Migration Manager on other servers you will specify the database in the setup as usual): 1. Copy the Migration Manager installation folder to a hard drive (e.g. C:\MMSPInstall). 2. Go to the C:\MMSPInstall\Migration Manager for Share- Point\Install folder. 3. Open the Install.ini file, which will look as follows: [Setups] QMCSetup=/i qsmanagementconsole_{version_number}.msi /l*v qmc_setup.log RelatedSetup=/i qmm4sp.{version_number}.msi /l*v mmsp_setup.log 4. Append the following parameters to the QMCSetup command line, where YourServer and YourDatabase are the SQL server name and the pre-created database name: DB_SERVER.BFAA2442_7AA5_4890_A6C2_8E0CA5BC2ADC= YourServer DB_NAME.BFAA2442_7AA5_4890_A6C2_8E0CA5BC2ADC =YourDatabase /quiet [Setups] QMCSetup=/i qsmanagementconsole_{version_number}.msi /l*v qmc_setup.log DB_SERVER.BFAA2442_7AA5_4890 _A6C2_8E0CA5BC2ADC=YourServer DB_NAME.BFAA2442_7AA5_4890_A6C2 _8E0CA5BC2ADC=YourDatabase /quiet RelatedSetup=/i qmm4sp.3.x.x.xxx.msi /l*v mmsp_setup.log 5. Save the file and start the product setup. The QMC part of the setup will now complete in the background without asking for any input. 52 Chapter 4. Deploying Migration Manager

62 Note: Make sure you have db_owner permissions on the DBA-provisioned database. The QMC setup will fail otherwise. Installing Migration Manager on SharePoint Server 53

63 Adding SharePoint Farms For Migration Manager to be able to migrate content to or from a SharePoint farm, the farm must be added (registered) to the product. Normally SharePoint server farms are added automatically when Migration Manager is installed on a server in the farm. The list of known server farms is displayed in every site selection screen. The farm list shows front-end servers used to add each farm and is filtered by SharePoint version (e.g. only SharePoint 2003 server farms are shown in the Select Source Site screen of a SharePoint 2003 migration job): 54 Chapter 4. Deploying Migration Manager

64 You may need to add server farms manually in the following cases: Migrate SharePoint 2003 data remotely without installing Migration Manager on the source farm Install-time server discovery fails to add the local server farm A farm should be rediscovered if a new web application has been added to the farm. You can add a farm manually either during job creation or on the Settings page. To add a farm during job creation, perform the following steps: 1. When creating a migration job, click Select... in the Source URL/ Target URL field. The Select Source Site/ Select Target Site window appears. 2. Click the add link in the note below the list, and enter NETBIOS or DNS name or IP address of the SharePoint server in the appeared dialog box. 3. Click OK. Note: Appendix F: Discovery Issues contains information about troubleshooting when adding a farm. Adding SharePoint Farms 55

65 Upgrading Migration Manager Upgrading Web Console Upgrade for / Migration Upgrade for Migration Installing Update Starting from Migration Manager for SharePoint 3.1 during the new version installation, the old version is uninstalled automatically. None of customizations are preserved. Upgrading Web Console Starting from Migration Manager for SharePoint 3.0 the web console port is preserved during re-installation or upgrading. If you update a previous version of Migration Manager, you can prepare it to preserve port. Refer to How to Preserve Web Console Port for more information. Upgrade for / Migration If you are running Migration Manager for SharePoint or higher, you can upgrade to the new version and retain your existing migration jobs. To retain the jobs, do not reinstall Quest Management Console into a new database. To preserve migration progress of all jobs, perform the following: 1. Stop all running jobs. Note: To stop all running jobs at once: a) Open the command line and go to Quest Software\Migration Manager for SharePoint\Scripts\SupportTools folder. b) Run the pythonrun.bat StopAllJobs.py command. To start all jobs at once, run the pythonrun.bat StartAllJobs.py command. 2. Wait while the target service uploads all messages from the Migration Manager message queue. 56 Chapter 4. Deploying Migration Manager

66 Note: If you pass this step, all messages that have been sent to MSMQ will not be uploaded to the target site. You can check the message queue in Computer Management Services and Application Message queuing Private queues quest.mm4sp.queue Queue messages. 3. Copy all XML files that were modified (e.g., the mapping rules were adjusted or migration behavior for Surveys lists was changed). 4. When the message queue is purged, run installation of the newest version. The Quest Management Console will be upgraded automatically if needed. 5. Change XML files according to the previous version and restart the Migration Manager services. Note: It is not recommended to replace XML files while there may be changes in the new version. 6. Start all required jobs to continue your migration. If you are running an earlier version of Migration Manager (including Quest Management Console for SharePoint), you will need to complete your running migration jobs, then delete them and uninstall Migration Manager before installing the latest version. Upgrade for Migration Before upgrading for Migration Manager, make sure all jobs are completed. To retain all jobs, do not reinstall Quest Management Console into a new database. Migration Manager for SharePoint supports migration jobs created by 2.2 version and later. By default, after the new version installation the syncronization does not work for jobs created by 2.2 version. Refer to How to preserve synchronization for during upgrade from 2.2 for more information. Note: If you have any running jobs created by Migration Manager version 2.1 and earlier complete them before the new version installation. Create a new migration job after upgrading. Upgrading Migration Manager 57

67 Installing Update Before installing an update for Migration Manager, make sure all jobs are completed. SharePoint 2007 to 2007 migration jobs complete automatically. SharePoint 2003 to 2007 jobs continue post-migration synchronization. Stop all jobs in the post-migration sync state manually and make sure the target service uploads all messages from the Migration Manager message queue. Upgrade for Migration When you install the new version of Migration Manager all migration jobs will be retained. Do not reinstall Quest Management Console to a new database to retain the jobs. Note: If you have Extension Web Service installed on the target SharePoint 2010 server, you should update it with the newest version provided with the new version of Migration Manager. Refer to the Upgrading Extension Service section for detailed information. 58 Chapter 4. Deploying Migration Manager

68 Managing Licenses To view or update the current product license, click the License: <Type> link in the copyright notice line at the bottom of any Migration Manager Web Console page: This will open the Manage License screen where the current license information is displayed: When you install Migration Manager for the first time, a time-limited license is used. When your license or trial expires, a warning message appears when you try to create new migration jobs or restart the existing ones. You will not be able to create or restart jobs until you apply a new license. Viewing Configuration To view configuration of Migration Manager, click the Settings link in the top right corner in any job wizard: Managing Licenses 59

69 The Settings page is opened: On the page you can perform the following: View a name of the SQL server and the Repository database used for the current installation View a list of SharePoint farms added into Migration Manager View a version for each SharePoint farm View the name of Migration Manager host used for migration to/from a farm Add a new SharePoint farm Remove added SharePoint farm from Migration Manager. 60 Chapter 4. Deploying Migration Manager

70 5.0 Working with Migration Manager for SharePoint Getting Started Migration Manager for SharePoint provides a web-based console to create, manage and monitor migration jobs remotely in a browser. A start page opens up at the end of the product installation. Follow the links on the start page to access the required migration module: You can also access the web console on the Migration Manager server with a Start Menu shortcut: Programs Quest Software Migration Manager for SharePoint. 61

71 Note: Each instance of Migration Manager for SharePoint provides a web console. When you have all Migration Manager instances sharing the same configuration (repository database), you can use the web console on any server. The web console functions identically no matter which server you connect to. You may think of it as multiple Central Administration sites in a single SharePoint farm. Delegating Access to Web Console Web console allows you to manage migration jobs remotely by opening the console URL in your browser. By default, only local administrators of the server are allowed to access the Web console. You can adjust a configuration file to grant other users and groups access to the console. Open the {MMSPInstallationFolder}\Web Interface\Python25\conf\httpd.conf and add the desired group (e.g. your SharePoint farm administrators - YOURDOMAINSharePointAdmins) to the Require directive in the LocationMatch section: <LocationMatch /(2k3JobWizard 2k7JobWizard license make 7to10)/* > AuthName Please Enter Your Logon Details AuthType SSPI SSPIAuth On SSPIAuthoritative On require group BUILTIN\Administrators YOURDOMAIN\SharePointAdmins </LocationMatch> For more information on the Require directive, please see 62 Chapter 5. Working with Migration Manager for SharePoint

72 Migrating SharePoint 2003 to 2007/2003 to 2010 Choosing Between Migration Job Options There are three migration path options for migration jobs you can select in Migration Manager: Migrate to Site Collection - the selected site with its subsites will be migrated to a new site collection in the specified target SharePoint web application. This option allows you to promote a subsite to a separate site collection. Migrate to Site - the selected site with its subsites will be migrated as a new subsite of an existing target SharePoint site. This option can be used if you need to demote a site collection to a regular site. Migrate Lists to Site - the selected lists will be migrated to an existing target SharePoint site. Refer to the following diagram to view site logical architecture. Creating Migration Jobs This section describes how to create migration jobs for moving SharePoint 2003 content including metadata, security settings and look and feel to 2007 or 2010 sites. Note: During job creation you can select either of SharePoint 2007 or SharePoint 2010 versions as the target. Refer to the Target Version Selection section for more detailed information. Creating Job for Site Migration Creating Job for List Migration Migrating SharePoint 2003 to 2007/2003 to

73 Creating Job for Site Migration To create a migration job, perform the following steps: 1. Select the Migrate SharePoint 2003 link on the start page. By default, the Migrate to Site Collection wizard opens. 2. Select either Migrate to Site Collection or Migrate to Site. 3. Specify the job name and description. 64 Chapter 5. Working with Migration Manager for SharePoint

74 4. Type the source site URL in the Source URL field or click Select... to search for the source site by a part of its URL. Generating the initial list of sites may be time-consuming. To disable site enumeration, select the Skip initial site enumeration option. The initial site enumeration will be disabled when selecting the target site and in subsequent creation of migration jobs. Disabling the initial site enumeration affects list migration. In case the Skip initial site enumeration option is disabled for site migration, the initial list enumeration will be also disabled. Note: If the desired URL is not in the list, make sure the required SharePoint farm has been discovered and its front-end is listed as Share- Point Server. Click the add link to add new SharePoint farm. Migrating SharePoint 2003 to 2007/2003 to

75 5. You can exclude some objects from migration. In the Exclusions area, click Add..., and then select the desired site using the search option in the Exclude Sites and Lists window. The child objects of the selected site are displayed in the Lists on site section. By default, all objects are unchecked, i.e. included into migration. To exclude an object from migration, select it. Note: If you exclude a site from migration, all its subsites, document libraries and lists will not be migrated either. 66 Chapter 5. Working with Migration Manager for SharePoint

76 The objects excluded from migration are shown in the Exclusions table. If you want to include an object into migration again, remove the corresponding entry from the table. Warning: By default, the following list types are excluded from migration and not shown in User Interface: Site Template Gallery List Template Gallery Web Part Gallery 6. To see the amount of the content to be migrated and an estimation of the migration time, click the Info button. Refer to the Pre-Migration Analysis section for more information. Note: The migration time estimation is based on migration performance measured on a specific hardware and software configuration. It might not be accurate for different configurations and provided for reference only. Migrating SharePoint 2003 to 2007/2003 to

77 7. In the Target URL field, specify the following: a) For the Migrate to Site option, specify the target URL for the migrated site or click Select..., and then select the target parent site using URL search in the Select Target Site window. Generating the initial list of sites may be time-consuming. To disable site enumeration, select the Skip initial site enumeration option. The initial site enumeration will be disabled in subsequent creation of migration jobs. Disabling the initial site enumeration affects list migration. In case the Skip initial site enumeration option is disabled for site migration, the initial list enumeration will be also disabled. Note: If the Skip initial site enumeration option was enabled earlier, the initial enumeration of target sites returns no results. Note: If the desired URL is not in the list, make sure: the required SharePoint farm has been discovered and its front-end is listed as SharePoint Server. Click the add link to add new Share- 68 Chapter 5. Working with Migration Manager for SharePoint

78 Point farm. Refer to the Adding SharePoint Farms section for more information. a SharePoint farm is rediscovered after a new web application has been added. the appropriate target_version parameter is set as the target SharePoint version. Refer to Target version selection for more information. The target URL will be formed automatically by appending the source site URL name to the selected target site URL and displayed as Target URL. Migration Manager will create a new subsite with the specified target URL: To change the target site URL name during migration, delete the site URL name and specify the required name: Migrating SharePoint 2003 to 2007/2003 to

79 b) For the Migrate to Site Collection option, specify the target URL for the migrated site or click Select..., and then select the target Share- Point web application, managed path and new site collection URL name in the Select Target Site Collection window. Note: If the desired URL is not in the list, make sure: the required SharePoint farm has been discovered and its front-end is listed as SharePoint Server. Click the add link to add new Share- Point farm. Refer to the Adding SharePoint Farms section for more information. a SharePoint farm is rediscovered after a new web application has been added. the desired explicit managed path does not have site collection in it. the appropriate target_version parameter is set as the target SharePoint version. Refer to Target version selection for more information. 70 Chapter 5. Working with Migration Manager for SharePoint

80 Migration Manager will create a new site collection with the specified target URL: 8. Leave the Include Permissions option checked to migrate security permissions along with content or clear the check box to have target permissions inherited from the parent site. For more information, please refer to SharePoint 2003 Permission Migration section. 9. Check Start Now to start the migration job immediately after the job is created or leave it unchecked to start it manually at a convenient time. 10. By default, migration jobs are allowed to run always. If you want to allow the job to run during only specific hours during the week (e.g. nights and weekends), you can use the Migration Hours option to select when the job will be allowed to run. For more information, please refer to the Configuring Migration Hours section. 11. Click Create. After the migration job is created, you are redirected to the Job Details page. While on this page, you can manage the job, track its progress and health. Migrating SharePoint 2003 to 2007/2003 to

81 Creating Job for List Migration To create a migration job, perform the following steps: 1. Select the SharePoint 2003 link on the start page. 2. Select Migrate Lists to Site. 3. Specify the job name and description. 72 Chapter 5. Working with Migration Manager for SharePoint

82 4. Click Add... in the Source lists area. Select the desired site using site URL search from the Select lists for migration dialog, and then the lists you want to migrate in the Lists on site section. Note: If the Skip initial site enumeration option was enabled in site migration, the initial list enumeration returns no results. Note: By default, the lists are not ordered. Click Lists on site to sort the lists by title. Note: If the desired URL is not in the list, make sure the required SharePoint farm has been discovered and its front-end is listed as Share- Point Server. Click the add link to add new SharePoint farm. Refer to the Adding SharePoint Farms section for more information. Note: The lists with lookup fields to be associated should be migrated within one job. For more information, please refer to the Appendix B: Processing Lookup Fields in Lists Migrated from SharePoint 2003 section. Warning: By default, the following list types are excluded from migration and not shown in User Interface: Site Template Gallery List Template Gallery Web Part Gallery Migrating SharePoint 2003 to 2007/2003 to

83 The lists selected for migration are displayed in the Source Lists table. If you want to remove the selected list from migration, remove the corresponding entry from the table. 5. To see the amount of the content to be migrated and an estimation of the migration time for a list, click the View... link next to the list URL. To see information for the whole job, click the Info button. Refer to the Pre-Migration Analysis section for more information. Note: The migration time estimation is based on migration performance measured on a specific hardware and software configuration. It might not be accurate for different configurations and provided for reference only. 74 Chapter 5. Working with Migration Manager for SharePoint

84 6. In the Target Site URL field, specify the target URL of the site you want to migrate the lists to or click Select..., and then select the target parent site using URL search in the Select Target Site window. Generating the initial list of sites may be time-consuming. To disable site enumeration, select the Skip initial site enumeration option. The initial site enumeration will be disabled in subsequent creation of migration jobs. Note: If the Skip initial site enumeration option was enabled earlier, the initial enumeration of target sites returns no results. Note: If the desired URL is not in the list, make sure: the required SharePoint farm has been discovered and its front-end is listed as SharePoint Server. Click the add link to add new Share- Point farm. Refer to the Adding SharePoint Farms section for more information. a SharePoint farm is rediscovered after a new web application has been added. the appropriate target_version parameter is set as the target Migrating SharePoint 2003 to 2007/2003 to

85 SharePoint version. Refer to Target version selection for more information. Migration Manager will create new lists in the specified target site. Note: The Include Permissions option is disabled for lists migration. For more information, please refer to SharePoint 2003 Permission Migration section. 7. Check Start Now to start the migration job immediately after the job is created or leave it unchecked to start it manually at a convenient time. 8. By default, migration jobs are allowed to run always. If you want to allow the job to run during only specific hours during the week (e.g. nights and weekends), you can use the Migration Hours option to select when the job will be allowed to run. For more information, please refer to the Configuring Migration Hours section. 9. Click Create. After the migration job is created, you are redirected to the Job Details page. While on this page, you can manage the job, track its progress and health. 76 Chapter 5. Working with Migration Manager for SharePoint

86 Migration Job Details After SharePoint / migration job is created, you are redirected to the Job Details page. While on this page, you can view the job overview, manage the job and track its progress and health. The page contains the following tabs: 1. General - provides you with the following information for each job: Name - the job name. Description - the job description. Source URL - the path to the source site/site collection (not displayed for list migration jobs). Target URL - the path to the target site/site collection (not displayed for list migration jobs). Include Permissions - displays whether migration of permissions for the job is enabled. Running - displays whether initial migration or post-migration sync of the job is running. Migrating SharePoint 2003 to 2007/2003 to

87 Objects migrated/total - the number of the migrated objects/the total number of objects assigned for migration. The total number is counted level by level and can increase during migration. ETA - the estimated time of initial migration. Issues - the number of issues which occurred during migration. Started - the time when the job was started. Completed - the time when the job completed initial migration. Last Updated - the time when the source content (list items, documents, lists, libraries and sites) was last modified. When Initial migration has completed, numbers in the Objects migrated/total counter are equal, ETA is Migration completed and completion time is set to Completed. 2. Migration Pairs - contains pairs of objects (sites, lists, document libraries) included in the job. To view the state report for an individual object, click View... in the State field. 78 Chapter 5. Working with Migration Manager for SharePoint

88 3. Advanced - displays the advanced job properties. Migrating SharePoint 2003 to 2007/2003 to

89 Managing Migration Jobs Managing a Job You can perform a number of actions on a migration job using the Manage menu on the job details page. The following actions are available for SharePoint / migration jobs: Start Stop (Pause) View/change the job schedule Delete Starting Migration Job If the Start Now option was not selected during job creation, you can start the job at a later time. To start a pending migration job: 1. Locate the job using the Pending job view and click the job name to open the Job Details page. 2. Select Start from the Manage menu. 80 Chapter 5. Working with Migration Manager for SharePoint

90 Stopping Migration Job You can pause a migration job temporarily to reduce the load on the system. To pause a running migration job: 1. Locate the job using the Running job view and click on the job name to open the job details page. 2. Select Stop from the Manage menu. Viewing/Changing Job Schedule To view/change the allowed migration hours for SharePoint 2003 to 2007/2003 to 2010 migration job: 1. Locate the job using one of the job views and click the job name to open the job details page. 2. Select Schedule... from the Manage menu, and then modify the allowed migration hours in the Set schedule window. For more detailed information refer to the Configuring Migration Hours section. Migrating SharePoint 2003 to 2007/2003 to

91 Deleting Migration Job After migration has completed and you made sure that all the content has been migrated, you can delete the migration job. To delete a migration job 1. Locate the job using one of the job views and click the job name to open the job details page. 2. Select Delete from the Manage menu. Managing Multiple Jobs Migration Manager allows users to select multiple migration jobs to start, stop and delete them in a single click. To manage multiple jobs, perform the following: 1. Locate the jobs using one of the job views, and then check the boxes next to the required jobs names. 2. Click the Delete/Start/Stop button. 82 Chapter 5. Working with Migration Manager for SharePoint

92 Monitoring Migration Jobs Migration Manager for SharePoint provides reports allowing you to monitor Sharepoint / jobs, track the migration progress and ensure that migration is successful: State Report Migration Manager allows you to compare the source and target locations for a migration job with its State Report. The report displays the following live statistics for source and target locations side by side: the number of subsites the number of lists the number of document libraries the number of documents the number of document versions the number of list items the number of attachments the total size of documents the size of the largest document the number of documents by type (file extension) When exclusions have been configured for the migration job, these sites and lists are excluded from the report as well. Migrating SharePoint 2003 to 2007/2003 to

93 The Remaining time represents the current estimation of the time required to complete the migration job. It is based on the migration speed (Change Rate) for the current job. To view the report, select State from the Monitor menu. displayed. The report is Each time you open the State report or refresh the page, the counters are requested from the source and target SharePoint. The request process may take few minutes. 84 Chapter 5. Working with Migration Manager for SharePoint

94 Warning: It is not recommended to refresh the report very often during the migration process as it uses the service resources that perform migration and can harm them. When you open the report, click Refresh to initiate the counting process, wait few minutes and then click Refresh again to display the counters. Note: The number of objects may not match for source and target sites in certain cases even when Migration Manager reports that the migration job is completed. The discrepancy typically comes from default lists, libraries and documents that are provisioned automatically for a SharePoint site. For instance, a SharePoint 2007/2010 site comes with a master page library that has no equivalent in SharePoint Issue Report The Issue report displays the job errors for post-migration analysis and troubleshooting. To view the report, perform either of the following: Select Issues from the Monitor menu on the Job Details page. Click the link next to Issues on the Job Details page. Click the link in the Issues column on the page listing the jobs. Migrating SharePoint 2003 to 2007/2003 to

95 The Issue report displays the summary of migration job issues. By default, the report displays only first 20 errors. To adjust the scope, change the Show First filter. Use the Filter issues by URL filter if you want to view issues for a particular site or list. You can open all errors in Excel or save them in the.csv file. To do that, use the View all in Excel link. To view the detailed information pertaining to a specific issue, click the Show more... link. Agents Report The Agents report displays the state of the Migration Manager servers running the migration job. 86 Chapter 5. Working with Migration Manager for SharePoint

96 The server state includes: Migration Manager services Microsoft services that Migration Manager relies on (Message Queuing and Task Scheduler) Migration Manager scheduled tasks SharePoint permissions for the service account Free disk space Source and target SharePoint versions To view the Agents report, select Agents from the Monitor menu. Migrating SharePoint 2003 to 2007/2003 to

97 Web Part Migration For SharePoint / jobs web parts and web part pages are not migrated during base content migrations. Migration Manager provides a post-migration tool that automatically processes the sites in the scope of a migration job as follows: Replicates web parts for the home pages of migrated sites. Rebuilds custom web part pages in SharePoint 2003 document libraries, including their layout and web parts in SharePoint 2007/2010. Rebuilds global pages for multipage meeting workspaces. Note: Custom web parts are only migrated if their backing assemblies are installed on the target SharePoint 2007/2010 server. Starting from Migration Manager 3.0 site home pages and custom web part pages in SharePoint 2003 document libraries are migrated automatically. Web parts migration is initiated after a job completes initial migration. When a web parts migration is started, the job appears in the Web Part Migration view. Name - the name of the migration job. Running on - the server where the web part page migration tool runs. Status - the current status of the web parts migration job. Progress - the percentage of the web parts migration progress. Last Updated - the time when the status was last updated. Issues - the number of issues occurred during web part migration. 88 Chapter 5. Working with Migration Manager for SharePoint

98 The Web Part job details page contains pairs of object URLs (the default aspx, document libraries, meeting workspace pages) participating in migration and their processing state. By default, the first 100 errors are displayed. To adjust the scope, change the Show First filter. In order to facilitate management of URLs, there are filtering (Filter pairs by URL) and paging on the page. If any issues occur during web part pages migration, the link next to the Issues appears. Click the link to go to the detailed error report for the migration job. The Migartion Job field contains the job name linked to the Job Details page. When the job is completed, it can be restarted. To restart web part migration, select Restart from the Web parts pages menu on the Job Details page. Migrating SharePoint 2003 to 2007/2003 to

99 Configuring Stored Credentials To perform web part migration in two-agent deployment, configure the stored credentials on the target server: Note: To configure stored credentials, you have to be logged on under the Quest Custom Page Migrator service account. 1. Open Control Panel Stored User Name and Password. 2. Add user account and password for the source server. Note: added. If alias is used for server, the original name should also be 3. Restart the Quest.MM4SP.CustomPageMigrator service. 4. Repeat web part migration. Migration Jobs Views Migration Manager provides a number of job views based on the job state so that you can easily locate migration jobs you need. In the SharePoint 2003 module, the following views are available: All - displays all SharePoint 2003 to 2007/2003 to 2010 migration jobs. Running - displays all migration jobs that are currently in progress. 90 Chapter 5. Working with Migration Manager for SharePoint

100 Initial Migration - displays all migration jobs that are currently in the initial migration state. Post-migration Sync - displays the jobs that are currently performing post-migration synchronization. Waiting for Schedule - displays running jobs waiting for the scheduled time. Pending - displays all migration jobs in a stopped state. Pending Start - displays the jobs for which migration has not been started. Pending to Resume Migration - displays the stopped jobs that have not completed initial migration. Pending to Resume Sync - displays the jobs that were stopped during post-migration synchronization. Completed - displays the jobs that have been completed. Completed Successfully - displays the jobs that have been completed successfully. Completed with Issues - displays the jobs that have been completed with errors. Web Part Migration - displays all migration jobs in a stopped state. Pending - displays the Web Part Migration (WPM) jobs for which migration was not started. Preparing - displays the WPM jobs which are being analyzed. In Progress - displays the running WPM jobs. Completed - displays completed WPM jobs. Failed - displays the WPM jobs that have not been completed due to errors. With Issues - displays all migration jobs that have any kind of migration errors. Migrating SharePoint 2003 to 2007/2003 to

101 When you open a view, the list of jobs in the selected state is displayed. The following information for each job is displayed: Name - the job name. Description - the job description. Progress - the objects migrated/total counter. Displays the number of migrated objects/the total number of objects to be migrated. ETA - the estimatied time of initial migration. Last updated - the time when the source content (list items, documents, lists, libraries and sites) was last modified (during initail migration or post-migration sync). While on this page, you can select multiple migrtion jobs to start, delete or stop them. Migration Job Lifecycle SharePoint 2003 to 2007/2003 to 2010 migration job progresses through a number of states during its lifecycle. This section describes the possible states of migration jobs, transitions between them and how you can control the state of a job. 92 Chapter 5. Working with Migration Manager for SharePoint

102 You can create a migration job with or without the Run Now option selected. In the first case it will immediately proceed with the initial content migration. In the second case, it will stay inactive in the Stopped state. You can start the job then at a convenient time. A running migration job can be stopped at any time as well. To start or stop a migration job, use the Start or Stop command in the Manage menu on the job details page. After the initial migration is done, the job enters Post-Migration Sync. In this state it tracks changes in the source sites, lists and document libraries and synchronizes the changes to the target site. The job will stay in this state until you either stop or delete it using the job Manage menu. A running migration jobs (initial migration and post-migration sync) is put on hold automatically when the Migration Hour settings of the job do not permit it to run. You can delete a migration job at any time using the Delete command in the job Manage menu. Migrating SharePoint 2003 to 2007/2003 to

103 Configuring Migration Hours A SharePoint / migration job can be scheduled to run only during specific hours of the week. You can set the allowed migration hours when creating migration job: or after the job is created on the job details page: You can select one of the predefined schedule templates (Run always is the default), or you can customize the allowed hours for the migration job. During the hours in blue the migration process is allowed, during hours in white, migration is disallowed and the migration job idles. Click the individual hour slots or day and hour headers to allow/disallow migration. Hold down Ctrl to toggle individual hour slots or Shift to select blocks of adjacent hours slots. 94 Chapter 5. Working with Migration Manager for SharePoint

104 Click OK to apply the schedule. Note: The schedule sets time when the source service extracts content. If the off-scheduled time is reached, the source service stops to extract content. The target service uploads all content from the message queue, and then waits for new messages. Target Version Selection The same job wizard is used for creating SharePoint 2003 to 2007 and Share- Point 2003 to 2010 migration jobs. By default, SharePoint 2010 is used as the target if SharePoint servers with this version have been added to Migration Manager. Otherwise SharePoint 2007 is used as the target. You can change this behavior: 1. Open the {MM installation directory}\web Interface\Web Job Wizard\JobWizard.config file. 2. Specify the required version for target_version in the global section. One of the following values can be used: (set by default) to use SharePoint 2010 as the target to use SharePoint 2007 as the target. Note: If no SharePoint 2010 servers are discovered, the job wizard shows the discovered SharePoint 2007 URLs during the target selection, regardless of the target_version value. Once the target_version value has been changed, you see SharePoint Servers with the specified version and can use them during job creation. Note: This parameter affects / migration only. Migrating SharePoint 2003 to 2007/2003 to

105 Synchronizing Content SharePoint / migration jobs continue to synchronize content after initial migration is completed. Jobs in post-migration sync are located in the Post-migration Sync view. During post-migration synchronization the following content is synchronized: new sites new lists and document libraries new list items and documents changed items and documents deleted items and documents. The following content is NOT synchronized: changes in sites and lists permissions changes in lists and sites structure and properties (for example add/remove columns, change versioning settings, regional settings, etc.) deleted sites and lists changed and deleted items for Surveys, Issues lists and Discussion boards Note: If you change the list or document library title on the source or target, synchronization will fail. Note: Avoid changing both the source and the target objects at the same time if post-migration synchronization is running. 96 Chapter 5. Working with Migration Manager for SharePoint

106 SharePoint Portal Site and Areas Migration Migrate SharePoint 2003 Portal Site to a New Site Collection When migrating the whole portal site as a new site collection, no additional configuration is required. Migrate Portal Site/Sub-area to a Site SharePoint 2003 Portal site/area can be migrated to a site collection where the Office SharePoint Server Publishing Infrastructure feature has been activated. If the following message appears during migration: The Office SharePoint Server Publishing Infrastructure feature must be activated at the site collection level before the Publishing feature can be activated activate the feature for the target site collection in: Central Administration > Site Settings > Site Features > Office SharePoint Server Publishing Infrastructure, and then re-migrate. Migrate Sub-area to a New Site Collection The Migration Manager behavior depends on the source area template. In most cases migration completes without any errors. If any Publishing-related error occurs for this scenario, you can do one of the following: Adjust mapping rules to create target site collection based on a different site template, and then re-migrate. Migrate an area to the pre-created site collection: a) Create a target site collection with the desired URL and make sure the Publishing feature has been activated for the site collection. b) Migrate an area using the Migrate to Site Collection option. In the Target URL field, specify the URL of the target site collection created in the previous step. Migrating SharePoint 2003 to 2007/2003 to

107 Permission Migration for Custom Portal Template By default Migration Manager migrates permissions for any custom template as a non-portal permissions. This causes issues with permissions migration for custom portal site definitions. To migrate permissions correctly, you should add custom site to a list of portal sites as follows: 1. Open the Quest SoftwareMigration Manager for Share- PointSpringConfigsMigrators.xml file. 2. Locate the PortalTempatesMask property. 3. Add name of the custom site definition as a new value in the list: 4. Restart the Quest.MM4SP.SourceService service 5. Remigrate the site. 98 Chapter 5. Working with Migration Manager for SharePoint

108 SharePoint Site Template Mapping Transforming a Custom SharePoint 2003 Site into a Standard Share- Point 2007/2010 Site Transforming a Standard SharePoint 2003 Site into a Custom Share- Point 2007/2010 Site How Site Template Mapping Works By default, Migration Manager migrates sites based on standard site definitions and creates target sites based on the same site definitions. You can adjust mapping rules for Migration Manager to migrate custom corporate-branded site or transform a source team site into Collaboration Portal or new corporate-branded site. To adjust mapping rules, you need to modify the WebTemplateIds.xml and WebTemplates.xml files located in the Migration Manager installation directory. The default path is: <installdir>\springconfigs\. By default, the mapping contains the rules for migrating standard WSS 2.0 to standard WSS 3.0 templates. Note: For two agent installation the files from the target Migration Manager host should be modified. It is required to adjust mapping rules in the following cases: Transforming a custom SharePoint 2003 site into a standard SharePoint 2007/2010 site. Refer to Example 2 in the How Site Template Mapping Works section below. Transforming a standard SharePoint 2003 site into a custom SharePoint 2007/2010 site. Refer to Example 3 in the How Site Template Mapping Works section below. Modifying mapping rules for standard templates. Refer to Example 4 in the How Site Template Mapping Works section below. Transforming a custom SharePoint 2003 site into a custom SharePoint 2007/2010 site. Refer to Example 5 in the How Site Template Mapping Works section below. Warning: Site Template Mapping is a global setting for all migration jobs on the server. Migrating SharePoint 2003 to 2007/2003 to

109 Note: If created site is based on a custom template (.stp file), Migration Manager defines the original site definition and uses it for migration. Mapping for.stp files is not supported. Transforming a Custom SharePoint 2003 Site into a Standard SharePoint 2007/2010 Site By default, Migration Manager migrates sites based on the default SharePoint 2003 site templates. To migrate SharePoint 2003 sites based on a custom site definition, perform the following steps: 1. Find out the source template name, ID and configuration number. The required template ID is typed in the error message in the Source- Service.log file or Issue Report. The corresponding template name and configuration number can be found in one of the WEBTEMP*.XML files located in the SharePoint 2003 installation directory. The default path for English version is: C:\Program Files\Common Files\Microsoft Shared\web server extensions\60\template\1033\xml 2. Open the WebTemplateIds.xml file and add a new entry to the dictionary element as follows: 100 Chapter 5. Working with Migration Manager for SharePoint

110 3. Open the WebTemplates.xml file. Copy the mapping rule for STS#0 source site template, append it at the beginning of the mapping, and then change the entry key entity from STS#0 to your custom template name and configuration number: Note: The mapping rule will transfer the MYCORPSITE custom template to the Team site (STS#0) standard template. Note: For two agent installation modify the files on the target Migration Manager host. 4. Restart Migration Manager Services for the changes to take effect and create a job to migrate the site. Note: Site Template Mapping must contain the rules for all the source sites being migrated and the target templates specified by the mapping must be available on the target SharePoint server. If Migration Manager encounters a site which is to be migrated to a template unavailable on the target SharePoint server, the site (and its subsites) is not migrated and the error is logged to the Issues report. Transforming a Standard SharePoint 2003 Site into a Custom SharePoint 2007/2010 Site By default, Migration Manager creates target sites based on standard Share- Point 2007/2010 templates. To create SharePoint 2007/2010 sites based on the custom site definition, perform the following steps: 1. Find out the target template name and configuration number. The required template name and configuration number can be found in one of the WEBTEMP*.XML files located in the SharePoint 2007/2010 installation directory. The default path for English version is: Migrating SharePoint 2003 to 2007/2003 to

111 C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\1033\XML 2. Open the WebTemplates.xml file. Locate the mapping rule for STS#0 site template, and then change the value entity from STS#0 to your custom template name and configuration number: Note: The mapping rule will transfer the Team site (STS#0) template to the MYNEWCORPSITE template. Note: For two agent installation modify the file on the target Migration Manager host. How Site Template Mapping Works Migration Manager receives the source site from a database and gets the site template ID. It tries to locate the ID in the WebTemplateIds.xml configuration file to find the site name. If the required ID is not found, the job stays in a starting state and the following error is written to the SourceService.log file: Unable to find the mapping rule for a site in the {Job name} job. Error message: Unable to locate the {template ID} site definition in the site template mapping rules. If the required ID has been found in the WebTemplateIds.xml file, Migration Manager addresses to WebTemplates.xml file that contains mapping rules for site templates. You can change mapping rules in this file. For details, please refer to the examples given below. For detailed information about adjusting mapping rules, please refer to the Transforming a Custom SharePoint 2003 Site into a Standard SharePoint 2007/2010 Site and Transforming a Standard SharePoint 2003 Site into a Custom SharePoint 2007/2010 Site sections. 102 Chapter 5. Working with Migration Manager for SharePoint

112 Example 1 Default mapping rules in the WebTemplates.xml file Migrating SharePoint 2003 to 2007/2003 to

113 Example 2 Changes required to be made in the WebTemplateIds.xml and WebTemplates.xml files to transform a source corporate-branded site into a team site Changes in WebTemplateIds.xml: Changes in WebTemplates.xml: 104 Chapter 5. Working with Migration Manager for SharePoint

114 Example 3 Changes required to be made in the WebTemplates.xml file to transform a source portal site into a corporate-branded site Example 4 Changes required to be made in the WebTemplates.xml file to transform a source team site into collaboration portal site: Migrating SharePoint 2003 to 2007/2003 to

115 Example 5 Changes required to be made in the WebTemplateIds.xml and WebTemplates.xml files to transform a source corporate-branded site into a target corporate-branded site Changes in WebTemplateIds.xml: Changes in WebTemplates.xml: 106 Chapter 5. Working with Migration Manager for SharePoint

116 SharePoint List Template Mapping By default, Migration Manager can create SharePoint lists based on standard list definitions only. If a source list based on a custom list definition is being migrated, the following error message is displayed during the migration: The *** list template is not available on the target site. To be able to migrate the list, Migration Manager should know which list template feature to use on the target site. List Template Mapping sets the rules to map the source list definition to the target list definition. Note: files). Migration Manager does not support mapping for list templates (.stp List Template Mapping is to be used in the following cases: Creating a standard target list from a custom source list. Creating a custom target list from a custom source list. Creating a custom target list from a standard source list. In any of the above cases you will need to modify the ListTemplatesMapping.xml file located in the Migration Manager installation directory. Note: For two agent installation the file from the target Migration Manager host should be modified. To adjust the mapping rules correctly, take the following into consideration: SourceTemplate - a template name for a parent site of the source list. (The corresponding TemplateID value can be found in the manifest.xml of the source list.) TargetTemplate - a template name for a parent site of the target list. (The corresponding TemplateID value can be found in the manifest.xml of the target list.) SourceTemplateID - a type value for the source list. You see this value in the error message. (The TemplateType value in the manifest.xml of the source list.) Migrating SharePoint 2003 to 2007/2003 to

117 FeatureName - the feature name for the target list definition. (The corresponding FeatureID value can be found in the manifest.xml of the target list.) TargetTemplateID - a type value for the target list. (The Template- Type value in the manifest.xml of the target list.) The required information can be found in the source and the target list templates. 1. Save source list as the.stp template. Save the template locally. 2. Create a temporary target list with the required list definition and save it as the.stp template. Save the template locally. 3. Rename the templates to.cab. 4. Extract Manifest.xml from the cab files and open them. The source Manifest.xml has the following information: The TemplateID=10010 corresponds to a custom site definition The target Manifest.xml has the following information: The TemplateID=1 corresponds to the STS site definition Setting Mapping Rules When all the required information is available, you can set the mapping rules: 1. Open the ListTemplatesMapping.xml file. 108 Chapter 5. Working with Migration Manager for SharePoint

118 Note: For two agent installation open the file on the target Migration Manager host. 1. Add a mapping rule. For example: <SiteDef SourceTemplate="CustomSite" TargetTemplate="STS"> <ListTemplateMapping Desc="SrcList" SourceTemplateID="800" FeatureName="ListFeat" TargetTemplateID="10008"/> </SiteDef> 2. Save the file. 3. Restart the Quest.MM4SP.SourceService and Quest.MM4SP. TargetService services for the changes to take effect. 4. Create a new job to migrate the list. List fields Migration Manager creates a target list with a set of fields from the list definition and then creates additional fields which have been added manually to the source list. In addition, if a source field has been changed or saved, it is changed in the target list or added to the list if is not created from the list definition. It is recommended to create a target list definition with the same set of fields as the source list definition and use it for mapping. Mapping of Domains and Users By default, each SharePoint 2003 user is added as is (with original domain and user name) to the target SharePoint 2007/2010 site collection users list. You can adjust rules to map a domain and/or a user. Migrating SharePoint 2003 to 2007/2003 to

119 User Mapping To map a source user to a different target user during migration, perform the following steps: 1. Open the {MMSPInstallDir}\SpringConfigs\Migrators.xml file. 2. Locate the UserMapping property. 3. Add the required entry with the source (key) to target (value) user mapping. For example: Note: rule. If you need to add several mapping rules, add an entry for each 4. Restart the Quest.MM4SP.SourceService and Quest.MM4SP.TargetService services for the changes to take effect. 5. Create a new migration job. Note: User Mapping is a primary mapping rule. If a user is mapped according to the UserMapping rules, its domain is not mapped according to the UserDomainMapping rules. Domain Mapping To map a source domain to a different domain during migration, perform the following steps: 1. Open the {MMSPInstallDir}\SpringConfigs\Migrators.xml file. 2. Locate the UserDomainMapping property. 110 Chapter 5. Working with Migration Manager for SharePoint

120 3. Add the required entry with the source (key) to target (value) domain mapping. For example: Note: rule. If you need to add few mapping rules, add an entry for each 4. Restart the Quest.MM4SP.SourceService and Quest.MM4SP.TargetService services for the changes to take effect. 5. Create a new migration job. Firewall Configuration There are two sets of ports required for SharePoint / migration: Ports for adding a SharePoint farm. You can close the ports after adding the required farm. Ports for job creation and migration. Depending on the Migration Manager deployment scenario for SharePoint / migration, different firewall configurations are required. The configuration below describes the scenario when there is a firewall between SharePoint farms and outbound connections are allowed. If the firewall is between servers within a farm and outbound connections are not allowed, you may require additional configuration. Migrating SharePoint 2003 to 2007/2003 to

121 Single Agent Deployment In this scenario Migration Manager is installed on the target server and all services work with SharePoint 2003 remotely. Adding a SharePoint Farm The target farm is discovered by a local component and firewall configuration is not required. Discovery results are written into the Repository database. A server where the database is located should have SQL ports opened. The source SharePoint 2003 farms which content you want to migrate should be added to Migration Manager. Configure firewall and open SQL ports for the server and WMI/RPC ports. Refer to the Firewall Blocks SharePoint Server section for more detailed information on how to configure firewall on the source server. Job Creation and Migration The following ports should be opened: Migration Manager Web Console port. If you work with Migration Manager from a remote browser, the Web Console port should be opened. For Migration Manager 3.1 the default port is SQL ports. The target agent should have access to the source content and configuration SharePoint databases and to the Repository database. Configure the corresponding firewalls to open the requied ports. The default SQL instance uses 1433 TCP port. Refer to the following article for more details: Site ports. To migrate web parts, the Custom Page Migrator service should have access to the source sites via HTTP. Configure the source firewall to open ports of the source web applications. Two Agents Deployment In this scenario Migration Manager is installed on the source and target servers, so the source and target services communicate using the Message Queuing service. 112 Chapter 5. Working with Migration Manager for SharePoint

122 Note: It is recommended to use two agents deployment to perform migration from SharePoint Use it as the last solution. The configuration below describes the scenario when there is a firewall between SharePoint farms and outbound connections are allowed. If the firewall is between servers within a farm and outbound connections are not allowed, you may require additional configuration. Adding a SharePoint Farm Local farms are discovered by a local component during Migration Manager installation. Discovery results are written into the Repository database. A server where the database is located should have SQL ports opened. Job Creation and Migration The following ports should be opened: Migration Manager Web Console port. Both instances of Migration Manager have individual web consoles. You can work with any of them. If you work with the console from a remote browser, the Web Console port should be opened. For Migration Manager 3.1 the default port for Web Console is MSMQ. Migration Manager uses the Message Queuing service for communication between the source and target servers. Open 1801 TCP port on the target farm to receive messages from the source farm. Refer to the following article for more details: SQL ports. The source and target agents access configuration and content databases of the local SharePoint farm and firewall configuration is not required. However, both agents should access the Repository database. The default SQL instance uses port Refer to the following article for more details: Site ports. To migrate web parts, the Custom Page Migrator service should have access to the source sites via HTTP. Configure the source firewall to open ports of the source web applications Migrating SharePoint 2003 to 2007/2003 to

123 Migrating SharePoint 2007 to 2007/2010 to 2010 Choosing Between Migration Job Options There are three migration path options for migration jobs you can select in Migration Manager: Migrate to Site Collection - the selected site with its subsites will be migrated to a new site collection in the specified target SharePoint web application. This option allows you to promote a subsite to a separate site collection. Migrate to Site - the selected site with its subsites will be migrated as a new subsite of an existing target SharePoint site. This option can be used if you need to demote a site collection to a regular site. Migrate Lists to Site - the selected lists will be migrated to an existing target SharePoint site. Refer to the following diagram to view site logical architecture. 114 Chapter 5. Working with Migration Manager for SharePoint

124 Creating Migration Jobs This section describes how to create migration jobs for moving SharePoint 2007 or SharePoint 2010 content including security settings and look and feel within a single server or between SharePoint farms. Creating Job for Site Migration Creating Job for List Migration Creating Job for Site Migration To create a migration job, perform the following steps: 1. Select the Reorganize SharePoint 2007 and 2010 link on the start page. By default, the Migrate to Site Collection wizard opens. 2. Select either Migrate to Site Collection or Migrate to Site. 3. Select the desired job mode. SharePoint 2007 for SharePoint migration. SharePoint 2010 for SharePoint migration. 4. Specify the job name and description. Migrating SharePoint 2007 to 2007/2010 to

125 5. Type the source site URL in the Source URL field or click Select... to search for the source site by a part of its URL. Generating the initial list of sites may be time-consuming. To disable site enumeration, select the Skip initial site enumeration option. The initial site enumeration will be disabled when selecting the target site and in subsequent creation of migration jobs. Disabling the initial site enumeration affects list migration. In case the Skip initial site enumeration option is disabled for site migration, the initial list enumeration will be also disabled. Note: If the desired URL is not in the list, make sure the required SharePoint farm has been discovered and its front-end is listed as Share- Point Server. Click the add link to add new SharePoint farm. Refer to the Adding SharePoint Farms section for more information. 116 Chapter 5. Working with Migration Manager for SharePoint

126 6. You can exclude some objects from migration. In the Exclusions area, click Add, and then select the desired site using the search option in the Exlude Sites and Lists window. The child objects of the selected site are displayed in the Lists on site section. By default, all objects are unchecked, i.e. included into migration. To exclude an object from migration, select it. Note: If you exclude a site from migration, all its subsites, document libraries and lists will not be migrated either. Migrating SharePoint 2007 to 2007/2010 to

127 The objects excluded from migration are shown in the Exclusions table. If you want to include an object into migration again, remove the corresponding entry from the table. 7. To see the amount of the content to be migrated and an estimation of the migration time, click the Info button. Refer to the Pre-Migration Analysis section for more information. Note: The migration time estimation is based on migration performance measured on a specific hardware and software configuration. It might not be accurate for different configurations and provided for reference only. 118 Chapter 5. Working with Migration Manager for SharePoint

128 8. In the Target URL field, specify the following: a) For the Migrate to Site option, specify the target URL for the migrated site or click Select..., and then select the target parent site using URL search in the Select Target Site window. Generating the initial list of sites may be time-consuming. To disable site enumeration, select the Skip initial site enumeration option. The initial site enumeration will be disabled in subsequent creation of migration jobs. Disabling the initial site enumeration affects list migration. In case the Skip initial site enumeration option is disabled for site migration, the initial list enumeration will be also disabled. Note: If the Skip initial site enumeration option was enabled earlier, the initial enumeration of target sites returns no results. Note: If the desired URL is not in the list, make sure: the required SharePoint farm has been discovered and its front-end is listed as SharePoint Server. Click the add link to add new Share- Migrating SharePoint 2007 to 2007/2010 to

129 Point farm. Refer to the Adding SharePoint Farms section for more information. a SharePoint farm is rediscovered after a new web application has been added. The target URL will be formed automatically by appending the source site URL name to the selected site URL and displayed as Target URL. Migration Manager will create a new subsite with the specified target URL. To change the target site URL name during migration, delete the site URL name and specify the required name. 120 Chapter 5. Working with Migration Manager for SharePoint

130 b) For the Migrate to Site Collection option, specify the target URL for the migrated site or click Select..., and then select the target Share- Point web application, managed path and new site collection URL name in the Select Target Site Collection window. Note: If the desired URL is not in the list, make sure: the required SharePoint farm has been discovered and its front-end is listed as SharePoint Server. Click the add link to add new Share- Point farm. Refer to the Adding SharePoint Farms section for more information. a SharePoint farm is rediscovered after a new web application has been added. Migrating SharePoint 2007 to 2007/2010 to

131 You should provide the following information in the Site Collection Options section: In the Administrator area, specify the user login and the address. By default, Migration Manager will create the target site collection in a content database that SharePoint selects for it automatically. If you want to put the site collection in a new or specific existing content database, check the Create new or select existing option and specify or select the target content database. 122 Chapter 5. Working with Migration Manager for SharePoint

132 Migration Manager will create a new site collection with the specified target URL. 9. Leave the Include Permissions option checked to migrate security permissions along with content or clear the check box to have target permissions inherited from the parent site. For more information, please refer to the SharePoint 2007 to 2007/2010 to 2010 Permission Migration section. 10. Select when you want to start the migration job using the Start Job options. Note: For information about permission migration, please refer to the SharePoint 2007 to 2007/2010 to 2010 Permission Migration section. Migrating SharePoint 2007 to 2007/2010 to

133 11. Click Create. After the migration job is created, you are redirected to the Job Details page. While on this page, you can manage the job, track its progress and health. 124 Chapter 5. Working with Migration Manager for SharePoint

134 Creating Job for List Migration To create a migration job, perform the following steps: 1. Select the Reorganize SharePoint 2007 and 2010 link on the start page. 2. Select Migrate List to Site. 3. Select the desired job mode. SharePoint 2007 for SharePoint migration SharePoint 2010 for SharePoint migration 4. Specify the job name and description. Migrating SharePoint 2007 to 2007/2010 to

135 5. Click Add in the Source lists area. Select the desired site using site URL search from the Select lists for migration dialog, and then the lists you want to migrate in the Lists on site area. Note: If the Skip initial site enumeration option was enabled in site migration, the initial list enumeration returns no results. Note: By default, the lists are not ordered. Click Lists on site to sort the lists by title. The lists selected for migration are displayed in the Source Lists table. If you want to remove the selected list from migration, remove the corresponding list from the table. 126 Chapter 5. Working with Migration Manager for SharePoint

136 6. In the Target Site URL field, specify the target URL of the site you want to migrate the lists to or click Select, and then select the target parent site using URL search in the Select Target Site window. Generating the initial list of sites may be time-consuming. To disable site enumeration, select the Skip initial site enumeration option. The initial site enumeration will be disabled in subsequent creation of migration jobs. Note: If the Skip initial site enumeration option was enabled earlier, the initial enumeration of target sites returns no results. Note: If the desired URL is not in the list, make sure: the required SharePoint farm has been discovered and its front-end is listed as SharePoint Server. Click the add link to add new Share- Point farm. Refer to the Adding SharePoint Farms section for more information. a SharePoint farm is rediscovered after a new web application has been added. Migrating SharePoint 2007 to 2007/2010 to

137 Migration Manager will create new lists in the specified target site. Note: The Include Permissions option is disabled for lists migration. For more information, please refer to SharePoint 2007 to 2007/2010 to 2010 Permission Migration section. 7. Select when you want to start the migration job using the Start Job options. 8. Click Create. After the migration job is created, you are redirected to the Job Details page. While on this page, you can manage the job, track its progress and health. 128 Chapter 5. Working with Migration Manager for SharePoint

138 Migration Job Details After SharePoint 2007 (SharePoint 2010) migration job is created, you are redirected to the Job Details page. While on this page, you can view the job overview, manage the job and track its progress and health. The page contains the following tabs: 1. General - provides you the following information for each job: Name - the job name. Description - the job description. Source URL - the path to the source site/site collection (not displayed for list migration jobs). Target URL - the path to the target site/site collection (not displayed for list migration jobs). Running - displays whether initial migration or post-migration sync of the job is running. Status - the operation currently performed (e.g.: Pending, Exporting, Importing). Migrating SharePoint 2007 to 2007/2010 to

139 Progress - the progress for Export and Import operations. It displays Export completed during the manifest processing. Issues - the number of issues which occurred during migration. Created - the time when the job was created. Started - the time when the job was started or will be started for scheduled jobs. Last updated - the time when the job was last modified. When migration has completed, Status displays Completed and Progress displays Migration Completed. 2. Migration Pairs - contains pairs of lists/document libraries included in the list migration job. To view the state report for an individual list, click View... in the State field. 3. Advanced - displays the names of the source and target agents for the job. 130 Chapter 5. Working with Migration Manager for SharePoint

140 Managing Migration Jobs Managing a Job You can perform a number of actions on a migration job using the Manage menu on the Job Details page: The following actions are available for SharePoint (SharePoint ) migration jobs: Start Stop (Pause) Restart after a failure Synchronize Delete Starting Migration Job If the Start job option was set to Later (manually) during job creation, you can start the job at a later time. To start a pending migration job: 1. Locate the job using the Pending job view and click on the job name to open the job details page. 2. Select Start from the Manage menu. Stopping Migration Job To stop a migration job: Migrating SharePoint 2007 to 2007/2010 to

141 1. Locate the job using the Running job view and click on the job name to open the job details page. 2. Select Stop from the Manage menu. Note: The Stop command does not force a running job to stop its current operation (export or import). Restarting Failed Job You can retry a failed migration job after fixing the causing issue. When export fails, your only option is to restart the entire job (export and import). If the job failed during import, you have an additional option to retry import only using the exported data from the initial run. To restart a failed SharePoint 2007/2010 migration job: 1. Locate the job in the Completed/Failed job view and click on the job name to open the job details page. 2. Select either Restart or Retry Import from the Manage menu. 132 Chapter 5. Working with Migration Manager for SharePoint

142 Synchronizing Job Incremental synchronization runs automatically for site migration jobs without exclusions. Refer to the Synchronizing Content section for more information about synchronization. To perfrom full resync for list jobs and jobs with exclusions: 1. Locate the job using the Completed job view and click on the job name to open the job details page. 2. Select Full Resync from the Manage menu. For stopped site migration jobs without exclusions two options are available: Start - synchronizes only the items that have been added/modified since the initial job run (Incremental sync). Full Resync - exports all source items and overwrites the target content. Deleting Migration Job After migration has completed and you made sure that all the content has been migrated, you can delete the migration job. To delete a migration job, go to the page displaying the detailed job information, and then select Delete from the Manage menu. Note: SharePoint / migration jobs do not delete the exported content from disk on the source server when they complete. Deleting the job removes this content automatically. Migrating SharePoint 2007 to 2007/2010 to

143 Managing Multiple Jobs Migration Manager allows users to select multiple migration jobs to start, stop and delete them in a single click. To manage multiple jobs, perform the following: 1. Locate the jobs using one of the job views, and then check the boxes next to the required jobs names. 2. Click the Delete/Start/Stop button. 134 Chapter 5. Working with Migration Manager for SharePoint

144 Monitoring Migration Jobs Migration Manager for SharePoint provides reports allowing you to monitor the jobs, track the migration progress and to ensure that migration is successful: State Report Migration Manager allows you to compare the source and target locations for a migration job with its State Report. The report displays the following live statistics for source and target locations side by side: the number of subsites the number of lists the number of document libraries the number of documents the number of document versions the number of list items the number of attachments total size of documents the size of the largest document the number of documents by type (file extension) When exclusions have been configured for the migration job, these sites and lists are excluded from the report as well. Migrating SharePoint 2007 to 2007/2010 to

145 The Remaining time represents the current estimation of the time required to complete the migration job. It is based on the migration speed (Change Rate) for the current job. To view the report, select State from the Monitor menu. displayed. The report is Each time you open the State report or refresh the page, the counters are requested from the source and target SharePoint. The request process may take few minutes. The remaining migration time is based on the migration speed for the current job and calculated for each counter. 136 Chapter 5. Working with Migration Manager for SharePoint

146 Warning: It is not recommended to refresh the report very often during the migration process as it uses the service resources that perform migration and can harm them. When you open the report, click Refresh to initiate the counting process, wait few minutes and then click Refresh again to display the counters. Note: The number of objects may not match for source and target sites in certain cases even when Migration Manager reports that the migration job is completed. The discrepancy typically comes from default lists, libraries and documents that are provisioned automatically for a SharePoint site. For instance, there is a difference in numbers when migrating a subsite to a new site collection. The site collection comes with a few pre-defined galleries (list and site templates, web parts) that are counted for the target site but have no counterparts in the source site. Another example would be migrating a list with workflow tasks, that are not migrated to target. There can be significant difference between source and target items in the list. Issue Report The Issue report displays the job errors for troubleshooting. To view the Issue report, perform either of the following: Select Issues from the Monitor menu on the page displaying job details. Click the link next to the Issues in the Job Details page Click the link in the Issues column on the page listing the jobs. Migrating SharePoint 2007 to 2007/2010 to

147 The Issue report displays the summary of migration job issues. By default, the report displays only first 20 errors. To adjust the scope, change the Show First filter. Use the Filter issues by URL filter if you want to view issues for a particular site or list. You can open all errors in Excel or save them in the.csv file. To do that, use the View all in Excel link. To view the detailed information pertaining to a specific issue, click the Show more... link. Note: If an error occurs during site migration, the migration process is stopped. It is required to fix the issue before continuing migration. Agents Report The Agents report displays the state of the Migration Manager servers running the migration job. Note: The report may show the same server state in case of an intra-farm SharePoint 2007 migration job. The server state includes: Migration Manager services Microsoft services that Migration Manager relies on (Task Scheduler) Migration Manager scheduled tasks SharePoint and file system permissions for the service account Free disk space Source and target SharePoint versions 138 Chapter 5. Working with Migration Manager for SharePoint

148 To view the Agents report, select Agents from the Monitor menu. Migrating SharePoint 2007 to 2007/2010 to

149 Migration Jobs Views Migration Manager provides a number of job views based on the job state so that you can easily locate migration jobs you need. In the Reorganize SharePoint 2007/2010 module, the following views are available: All - displays all SharePoint / migration jobs. Running - displays all migration jobs that are currently in progress. Exporting - displays the jobs that are currently exporting the data from source location. Importing - displays the jobs that are currently importing the data to the target location. Queued - displays migration jobs waiting in the queue to be processed. Jobs waiting post-migration sync are displayed in the view. Completed - displays the jobs that have been completed. Succeeded - displays the jobs that have been completed successfully. Failed - displays the jobs that have been completed with issues. Pending - displays the jobs for which migration has not been started. Pending Manual Start - displays the jobs waiting to be run manually. 140 Chapter 5. Working with Migration Manager for SharePoint

150 Waiting for Schedule - displays the jobs waiting for the scheduled time. Interrupted - displays all migration jobs that have been interrupted. With Issues - displays all migration jobs that have any kind of migration errors. When you open a view, the list of jobs in the selected state is displayed. The following information for each job is displayed: Name - the job name. Description - the job description. Progress - the job progress. Issues - the number of issues which occurred during migration. While on this page, you can select multiple migrtion jobs to start, delete or stop them. Migration Job Lifecycle SharePoint 2007 to 2007/ 2010 to 2010 migration job progresses through a number of states during its lifecycle. This section describes the possible states of migration jobs, transitions between them and how you can control the state of a job. When you create a migration job, you can select to start it immediately or postpone starting it. Based on your choice the job will either proceed with Migrating SharePoint 2007 to 2007/2010 to

151 migration (start Exporting site content) or enter the Pending state. A pending job will either start automatically at the selected time or you can start it manually using the Start command in the Manage menu of the job details page. After export of the source content is completed, the migration job starts Importing it to the target location. You can stop or delete a migration job from the job Manage menu. After the job is completed, you can perform resynchronization of migration jobs. Job resynchronization will apply new and updated content, modified settings and security permissions to the target sites and lists. Site migration jobs without exclusions continue to synchronize changes automatically. Synchronizing Content The following synchronization types are available for SharePoint 2007/2010 migration migration jobs: Full Resync Incremental Sync Incremental sync is started automatically for site migration jobs without exclusions. 142 Chapter 5. Working with Migration Manager for SharePoint

152 Full Resync Full Resync allows you to repeat the whole migration. In this case, the export and import operations are repeated for all the objects below the migration root (sub-sites, document libraries, lists, documents and items). All objects and their properties will be remigrated. New objects will be added to the existing target hierarchy. The existing objects will not be duplicated, all properties will be reapplied. For a list migration job, you can synchronize a certain list pair: 1. Go to the Job Details page and switch to the Migration Pairs tab. 2. Check the required pair and click the Restart Selected button. Note: For list jobs and jobs with exclusion the Full Resync is the only available option. Incremental Sync Incremental sync is available for site migration jobs only. It allows you to migrate only new and modified SharePoint objects from the source. It also preserves permissions modifications. Note: Avoid changing both the source and the target objects at the same time if you plan to synchronize content. The following content is NOT synchronized: Deleted sub-sites, document libraries, lists, documents and items. If the unique permissions on the source are changed to inherited, the inheritance is not synchronized to the target. Exclude feature from migration ( or ) If you have activated features on the source site, but these features are not deployed on the target farm, you will get the error message similar to the following one: Could not find Feature Quest.ITSP.Monitor.Web There two ways to resolve the issue: 1. Deploy the feature on the target farm. Migrating SharePoint 2007 to 2007/2010 to

153 2. Exclude the feature from migration. To exclude the feature, follow the steps below: Open the Migration Manager for SharePoint\Web Interface\Migration 2007\Migration2007.config file. Specify features for the FeaturesToExclude parameter. For example: FeaturesToExclude = Quest.ITSP.Monitor.Web If you have several features to exclude, use ; as a delimiter: FeaturesToExclude = OffWFCommon;ReviewWorkflows Save the file. Run the Retry Import action from the job property page: Manage->Retry Import. Note: If a list is based on a feature, the feature exclusion does not exclude the list. 144 Chapter 5. Working with Migration Manager for SharePoint

154 Migrating SharePoint 2007 to 2010 Choosing Between Migration Job Options There are three migration path options for migration jobs you can select in Migration Manager: Migrate to Site Collection - the selected site with its subsites will be migrated to a new site collection in the specified target SharePoint web application. This option allows you to promote a subsite to a separate site collection. Migrate to Site - the selected site with its subsites will be migrated as a new subsite of an existing target SharePoint site. This option can be used if you need to demote a site collection to a regular site. Migrate Lists to Site - the selected lists will be migrated to an existing target SharePoint site. Refer to the following diagram to view site logical architecture. Migrating SharePoint 2007 to

155 Creating Migration Jobs This section describes how to create migration jobs for moving SharePoint 2007 content including metadata, security settings and look and feel to SharePoint 2010 sites. Creating Job for Site Migration Creating Job for List Migration Creating Job for Site Migration To create a migration job, perform the following steps: 1. Select the Migrate SharePoint 2007 link on the start page. 2. Select either Migrate to Site or Migrate to Site Collection. 3. Specify the job name and description. 146 Chapter 5. Working with Migration Manager for SharePoint

156 4. Type the source site URL in the Source URL field or click Select... to search for the source site by a part of its URL. Generating the initial list of sites may be time-consuming. To disable site enumeration, select the Skip initial site enumeration option. The initial site enumeration will be disabled when selecting the target site and in subsequent creation of migration jobs. Disabling the initial site enumeration affects list migration. In case the Skip initial site enumeration option is disabled for site migration, the initial list enumeration will be also disabled. Note: If the desired URL is not in the list make sure the required Share- Point farm has been discovered and its front-end is listed as SharePoint Server. Click the add link to add new SharePoint farm. Refer to the Adding SharePoint Farms section for more information. Migrating SharePoint 2007 to

157 5. You can exclude some objects from migration. In the Exclusions area, click Add, and then select the desired site using the search option in the Exclude Sites and Lists window. The child objects of the selected site are displayed in the Lists on site section. By default, all objects are unchecked, i.e. included into migration. To exclude an object from migration, select it. Note: If you exclude a site from migration, all its subsites, document libraries and lists will not be migrated either. The objects excluded from migration are shown in the Exclusions table. If you want to include an object into migration again, remove the corresponding entry from the table. 6. To see the amount of the content to be migrated and an estimation of the migration time, click the Info button. Refer to the Pre-Migration Analysis section for more information. 148 Chapter 5. Working with Migration Manager for SharePoint

158 7. In the Target URL field, specify the following: a) For the Migrate to Site option, specify the target URL for the migrated site or click Select..., and then select the target parent site using URL search in the Select Target Site window. Generating the initial list of sites may be time-consuming. To disable site enumeration, select the Skip initial site enumeration option. The initial site enumeration will be disabled in subsequent creation of migration jobs. Disabling the initial site enumeration affects list migration. In case the Skip initial site enumeration option is disabled for site migration, the initial list enumeration will be also disabled. Note: If the Skip initial site enumeration option was enabled earlier, the initial enumeration of target sites returns no results. Note: If the desired URL is not in the list, make sure: the required SharePoint farm has been discovered and its front-end is listed as SharePoint Server. Click the add link to add new Share- Migrating SharePoint 2007 to

159 Point farm. Refer to the Adding SharePoint Farms section for more information. a SharePoint farm is rediscovered after a new web application has been added. The target URL will be formed automatically by appending the source site URL name to the selected site URL and displayed as Target URL. Migration Manager will create a new subsite with the specified target URL. To change the target site URL name during migration, delete the site URL name and specify the required name. 150 Chapter 5. Working with Migration Manager for SharePoint

160 b) For the Migrate to Site Collection option, specify the target URL for the migrated site or click Select..., and then select the target Share- Point web application, managed path and new site collection URL name in the Select Target Site Collection window. Note: If the desired URL is not in the list make sure: the required SharePoint farm has been discovered and its front-end is listed as SharePoint Server. Click the add link to add new Share- Point farm. Refer to the Adding SharePoint Farms section for more information. the SharePoint farm has been rediscovered after a new web application has been added. Migration Manager will create a new site collection with the specified target URL. Migrating SharePoint 2007 to

161 8. Leave the Include Permissions option checked to migrate security permissions along with content or clear the check box to have target permissions inherited from the parent site. For more information, please refer to SharePoint 2007 to 2010 Permission Migration section. 9. Check Start Now to start the migration job immediately after the job is created or leave it unchecked to start it manually at a convenient time. 10. By default, user interface is not upgraded during migration. Select the required Site visual mode for the target site: Preserve SharePoint 2007 look and feel - User Interface will not be upgraded. All sites use the interface from SharePoint Upgrade to SharePoint 2010 user experience - User Interface will be upgraded. All sites use SharePoint 2010 interface. 11. By default, migration jobs are allowed to run always. If you want to allow the job to run during only specific hours during the week (e.g. nights and weekends), you can use the Migration Hours option to select when the job will be allowed to run. For more information, please refer to the Configuring Migration Hours section. 12. By default, all site content is included into migration. If you want to exclude old and large documents, files of forbidden types or excessive versions from migration, you can use the Filter content option. 13. Click Create. Note: If the target farm does not have Migration Manager Extension Web Service installed, the warning message may appear. Refer to the Migration Extensions for SharePoint 2010 for more 152 Chapter 5. Working with Migration Manager for SharePoint

162 detailed information. After the migration job is created, you are redirected to the Job Details page. While on this page, you can manage the job, track its progress and health. Migrating SharePoint 2007 to

163 Creating Job for List Migration To create a migration job, perform the following steps: 1. Select the Migrate SharePoint 2007 link on the start page. 2. Select Migrate Lists to Site. 3. Specify the job name and description. 4. Click Add in the Source lists area. Select the desired site using site URL search from the Select lists for migration dialog, and then the lists you want to migrate in the Lists on site section. 154 Chapter 5. Working with Migration Manager for SharePoint

164 Note: If the Skip initial site enumeration option is enabled in site migration, the initial list enumeration returns no results. Note: By default, the lists are not ordered. Click Lists on site to sort the lists by title. Note: If the desired URL is not in the list, make sure the required SharePoint farm has been discovered and its front-end is listed as Share- Point Server. Click the add link to add new SharePoint farm. Refer to the Adding SharePoint Farms section for more information. The lists selected for migration are displayed in the Source Lists table. If you want to remove the selected list from migration, remove the corresponding entry from the table. 5. To see the amount of the content to be migrated and an estimation of the migration time, click the Info button. Refer to the Pre-Migration Analysis section for more information. Migrating SharePoint 2007 to

165 6. In the Target Site URL field, specify the target URL of the site you want to migrate the lists to or click Select, and then select the target parent site using URL search in the Select Target Site window. Generating the initial list of sites may be time-consuming. To disable site enumeration, select the Skip initial site enumeration option. The initial site enumeration will be disabled in subsequent creation of migration jobs. Note: If the Skip initial site enumeration option was enabled earlier, the initial enumeration of target sites returns no results. Note: If the desired URL is not in the list, make sure the required SharePoint farm has been discovered and its front-end is listed as Share- Point Server. Click the add link to add new SharePoint farm. Refer to the Adding SharePoint Farms section for more information. 156 Chapter 5. Working with Migration Manager for SharePoint

166 Migration Manager will create new lists in the specified target site. Note: The Include Permissions option is disabled for lists migration. For more information, please refer to SharePoint 2007 to 2010 Permission Migration section. 7. Check Start Now to start the migration job immediately after the job is created or leave it unchecked to start it manually at a convenient time. 8. By default, migration jobs are allowed to run always. If you want to allow the job to run during only specific hours during the week (e.g. nights and weekends), you can use the Migration Hours option to select when the job will be allowed to run. For more information, please refer to the Configuring Migration Hours section. 9. By default, all site content is included into migration. If you want to exclude old and large documents, files of forbidden types or excessive versions from migration, you can use the Filter content option. 10. Click Create. Note: If Migration Manager Extension Web Service is not installed on the target farm, the warning message may appear. Refer to the Migration Extensions for SharePoint 2010 section for more detailed information. Migrating SharePoint 2007 to

167 After the migration job is created, you are redirected to the Job Details page. While on this page, you can manage the job, track its progress and health. Migration Job Details After SharePoint migration job is created, you are redirected to the Job Details page. While on this page, you can view the job overview, manage the job and track its progress and health. The page contains the following tabs: 1. General - provides you the following information for each job: Name - the job name. Description - the job description. Source URL - the path to the source site/site collection (is not displayed for list migration jobs). 158 Chapter 5. Working with Migration Manager for SharePoint

168 Target URL - the path to the target site/site collection (is not displayed for list migration jobs). Include Permissions - displays whether migration of permissions for the job is enabled. Running - displays whether initial migration or post-migration sync of the job is running. Issues - the number of issues which occurred during migration. Status - the current job state. When migrating objects, the number of migrated objects out of the total objects number is displayed. Created - the time when the job was started. Completed - the time when initial migration was completed. Last Updated - the time when the job was last modified. When Initial migration has completed, the Status field is set to Completed and completion time is set to Completed. 2. Migration Pairs - is displayed only for List migration jobs. It contains pairs of lists/document libraries included in the job. To view the state report for an individual object, click View... in the State field. Migrating SharePoint 2007 to

169 3. Advanced - displays the advanced job properties. 160 Chapter 5. Working with Migration Manager for SharePoint

170 Managing Migration Jobs Managing a Job You can perform a number of actions on a migration job using the Manage menu on the job details page. The following actions are available for SharePoint /2010 migration job: Start Stop (Pause) View/change the job schedule Delete Starting Migration Job If the Start Now option was not selected during job creation, you can start the job at a later time. To start a pending migration job: 1. Locate the job using the Pending job view and click on the job name to open the job details page. 2. Select Start from the Manage menu. Migrating SharePoint 2007 to

171 Stopping Migration Job You can pause a migration job temporarily to reduce the load on the system. To pause a running migration job: 1. Locate the job using the Running job view and click on the job name to open the job details page. 2. Select Stop from the Manage menu. Viewing/Changing Job Schedule To view/change the allowed migration hours for SharePoint 2007 to 2010 migration job: 1. Locate the job using one of the job views and click the job name to open the job details page. 2. Select Schedule... from the Manage menu, and then modify the allowed migration hours in the Set schedule window. For more detailed information refer to the Configuring Migration Hours section. 162 Chapter 5. Working with Migration Manager for SharePoint

172 Deleting Migration Job After migration has completed and you made sure that all the content has been migrated, you can delete the migration job. To delete a migration job 1. Locate the job using one of the job views and click the job name to open the job details page. 2. Select Delete from the Manage menu. Managing Multiple Jobs Migration Manager allows users to select multiple migration jobs to start, stop and delete them in a single click. To manage multiple jobs, perform the following: 1. Locate the jobs using one of the job views, and then check the boxes next to the required jobs names. 2. Click the Delete/Start/Stop button. Migrating SharePoint 2007 to

173 Monitoring Migration Jobs Migration Manager for SharePoint provides the following reports allowing you to monitor Sharepoint jobs, track the migration progress and ensure that migration is successful: State Report The most direct way to track migration progress is to compare the source and target locations side by side. This is what Migration Manager allows to do for a migration job with its State Report. The report displays the following live statistics for source and target locations side by side: the number of subsites the number of lists the number of document libraries the number of documents the number of document versions the number of list items the number of attachments the total size of documents the size of the largest document the number of documents by type (file extension) When exclusions have been configured for the migration job, these sites and lists are excluded from the report as well. The Remaining time represents the current estimation of the time required to complete the migration job. It is based on the migration speed (Change Rate) for the current job. 164 Chapter 5. Working with Migration Manager for SharePoint

174 To view the report, select State from the Monitor menu. displayed. The report is Each time you open the State report or refresh the page, the counters are requested from the source and target SharePoint. The request process may take few minutes. Warning: It is not recommended to refresh the report very often during the migration process as it uses the service recourses that perform migration and can harm them. Click Refresh when you open the page to initiate the counting process, wait few minutes and then click Refresh again to display the counters. Note: The number of objects may not match for source and target sites in certain cases even when Migration Manager reports that the migration job is completed. The discrepancy typically comes from default lists, libraries Migrating SharePoint 2007 to

175 and documents that are provisioned automatically for a SharePoint site. For instance, there is a difference in numbers when migrating a subsite to a new site collection. The site collection comes with a few pre-defined galleries (list and site templates, web parts) that are counted for the target site but have no counterparts in the source site. Issue Report The issue report displays the job errors for post-migration analysis and troubleshooting. To view the Issue report, do one of the following: Select Issues from the Monitor menu on the page displaying job details. Click the link next to the Issues in the Job Details page Click the link in the Issues column on the page listing the jobs. 166 Chapter 5. Working with Migration Manager for SharePoint

176 The issue report displays the summary of migration job issues. By default, the report displays only first 20 errors. To adjust the scope, change the Show First filter. Use the Filter issues by URL filter if you want to view issues for a particular site or list. You can open all errors in Excel or save them in the.csv file. To do that, use the View all in Excel link. To view the detailed information pertaining to a specific issue, click the Show more... link. Note: The Could not connect to the extension service warning message occurs for every migration job if the Migration Manager Extension Web Service was not installed. Refer to the following section for more detailed information. Migrating SharePoint 2007 to

177 Migration Jobs Views Migration Manager provides a number of job views based on the job state so that you can easily locate migration jobs you need. In the Migrate SharePoint 2007 to 2010 module, the following views are available: All - displays all SharePoint 2007 to 2010 migration jobs. Running - displays all migration jobs that are currently in progress. Initial Migration - displays all migration jobs that are currently in the initial migration state. Post-migration Sync - displays the jobs that are currently performing post-migration synchronization. Waiting for Schedule - displays running jobs waiting for the scheduled time. Pending - displays all migration jobs in a stopped state. Pending Start - displays the jobs for which migration has not been started. Pending to Resume Migration - displays the stopped jobs that have not completed initial migration. 168 Chapter 5. Working with Migration Manager for SharePoint

178 Pending to Resume Sync - displays the jobs that were stopped during post-migration synchronization. Completed - displays the jobs that have been completed. Completed Successfully - displays the jobs that have been completed successfully. Completed with Issues - displays the jobs that have been completed with errors. With Issues - displays all migration jobs that have any kind of migration errors. When you open a view, the list of jobs in the selected state is displayed. The following information for each job is displayed: Name - the job name. Description - the job description. Progress - the percentage of the job progress. Issues - the number of issues which occurred during migration. Last updated - the time when the job was last modified. While on this page, you can select multiple migrtion jobs to start, delete or stop them. Migrating SharePoint 2007 to

179 Migration Job Lifecycle SharePoint 2007 to 2010 migration job progresses through a number of states during its lifecycle. This section describes the possible states of migration jobs, transitions between them and how you can control the state of a job. You can create a migration job with or without the Run Now option selected. In the first case it will immediately proceed with the initial content migration. In the second case, it will stay inactive in the Stopped state. You can start the job then at a convenient time. A running migration job can be stopped at any time as well. To start or stop a migration job, use the Start or Stop command in the Manage menu on the job details page. After the initial migration is done, the job enters Post-Migration Sync. In this state it tracks changes in the source sites, lists and document libraries and synchronizes the changes to the target site. The job will stay in this state until you either stop or delete it using the job Manage menu. A running migration jobs (initial migration and post-migration sync) is put on hold automatically when the Migration Hour settings of the job do not permit it to run. You can delete a migration job at any time using the Delete command in the job Manage menu. 170 Chapter 5. Working with Migration Manager for SharePoint

180 Configuring Migration Hours A SharePoint migration job can be scheduled to run during only specific hours of the week. You can set the allowed migration hours when creating migration job: or after the job is created in the job details page: You can select one of the predefined schedule templates (Run always is the default), or you can customize the allowed hours for the migration job. During the hours in blue the migration process is allowed, during hours in white, migration is disallowed and the migration job idles. Click the individual hour slots or day and hour headers to allow/disallow migration. Hold down Ctrl to toggle individual hour slots or Shift to select blocks of adjacent hours slots. Click OK to apply the schedule. Migrating SharePoint 2007 to

181 Migration Extensions for SharePoint 2010 Extension Web Service preserves the following data and settings during SharePoint migration: Audit metadata (Created/Created by and Modified/Modified by) for document versions Site Regional settings (Locale, Time zone) Site theme Features activation Alerts migration Taxonomy mapping. If Extension Web Service is not installed on SharePoint 2010, a warning message describing the possible issues which can occur during migration is displayed, and two options are available: Proceed the job creation and Cancel the job creation. Migration Manager checks if the service exists on the target farm during migration job creation. The service is checked only once for each target farm and all the following jobs are created without the warning message being displayed. During the job initialization, Migration Manager checks the target farm for the Extension Web Service existence and issues a warning message if it is not installed. The following warning message appears in the Issue report: Warning. Could not connect to the extension service. Message: There was no endpoint listening at 172 Chapter 5. Working with Migration Manager for SharePoint

182 that could accept the message. This is often caused by an incorrect address or SOAP action. To preserve the data and settings, Migration Manager uses custom Share- Point web service - Quest Migration Manager Extension Web Service. It should be deployed on the target farm using the SharePoint solution package. Refer to the Installing Migration Manager Extension Web Service section for detailed information about installation. Audit Metadata If the service is not installed, audit metadata (Created/Created By and Modified/Modified By) for document versions are not migrated: all versions are created by the Migration Manager service account and modification time is set to migration time. Site Regional Settings If the service is not installed, regional settings are inherited from the parent object. Site Theme If the service is not installed, the default site theme is used. Note: Site themes are preserved if the Preserve SharePoint 2007 look and feel option is used for the job. Site Logo If the service is not installed, site logo is not preserved. Features Activation If the service is not installed, features are activated from the site definition. The Extension Web Service activates the site feature and the feature Migrating SharePoint 2007 to

183 it depends on, if the feature is available on the site. The service does not deactivate the feature on the site. Alerts Migration If the service is not installed, alerts are not migration. Taxonomy Mapping If the service is not installed, the Managed Metadata column is set to default value. Refer to the Taxonomy Mapping section for more detailed information. 174 Chapter 5. Working with Migration Manager for SharePoint

184 Synchronizing Content SharePoint migration jobs continue to synchronize content after initial migration is completed. Jobs in post-migration sync are located in the Post-migration Sync view. During post-migration synch the following content is synchronized: new sites new document libraries, lists, Surveys, Issues lists and Discussion boards new list items and documents changed items and documents changes in sites and lists permissions The following content is NOT synchronized: changes in lists and sites structure and properties (for example add/remove columns, change versioning settings, regional settings, etc) deleted sites and lists deleted items and documents Note: Avoid changing both the source and the target objects at the same time if post-migration synchronization is running. Mapping 2007 to 2010 Templates Migration Manager allows you to use mapping rules for sites and lists during SharePoint 2007 to 2010 migration. Note: Migration Manager supports mapping of site and list definitions. Mapping of.stp templates is not supported. Warning: Template Mapping is a global setting for all migration jobs on the Migration Manager host. Migrating SharePoint 2007 to

185 Site Template Mapping By default, Migration Manager creates target site based on the same site definitions as the source site. If the same site definition is not available on the target, the File not found error occurs for the site. You can adjust mapping rules to transform a source SharePoint 2007 site into one of the available SharePoint 2010 definitions during migration. To adjust mapping rules, you should modify the 2k7to2k10_Settings.xml files located in the Migration Manager installation directory: 1. Open the {MMSPInstallDir}\2k7to2k10_Settings.xml file. 2. Locate the WebTemplatesMapping property. 3. Add the required entry with mapping of a source site definition (key) to a target site definition (value). For example: Note: If you need to add few mapping rules, add an entry for each rule. 4. Restart the Quest.MM4SP.Migration2010 service. 5. Create a new migration job to perform migration. List Template Mapping By default, Migration Manager creates target list based on the same list definitions as the source list. If the same list definition is not available on the target, the Feature GUID for list template Id is not installed in this farm. error occurs for the list. You can deploy the list definition on the target site or can adjust mapping rules to transform a source SharePoint 2007 list into one of the available SharePoint 2010 definitions during migration. To adjust mapping rules, you should modify the 2k7to2k10_Settings.xml files located in the Migration Manager installation directory: 1. Open the {MMSPInstallDir}\2k7to2k10_Settings.xml file. 2. Locate the ListTemplatesMapping property. 176 Chapter 5. Working with Migration Manager for SharePoint

186 3. Add the required entry with mapping of a source list definition (key) to a target list definition (value). Note: When you map source custom list to a standard target list, target list definition is only required. For custom target list definition its feature ID should be specified in addition. The mapping should be specified as follows: Note: If you need to add few mapping rules, add an entry for each rule. 4. Restart the Quest.MM4SP.Migration2010 service. 5. Create a new migration job to perform migration. Allowed Trasformation of List Templates You may allow list template transformation for particular type of lists. For example, when you are migrating a portal site, the Images list on Share- Point 2010 is based on the Asset library (851) template. The source Images library has a Picture library (109) template. So, the 109 to 851 template transformation is allowed. You cannot use template mapping in this case, because it will transform every source Picture Library into an Asset Library. By default, Migration Manager allows to transform a Document library (template 101) and Picture Library (template 109) into a new Asset Library (template 851). 1. Open the {MMSPInstallDir}\2k7to2k10_Settings.xml file. 2. Locate the ExistingListTemplateMapping property. Migrating SharePoint 2007 to

187 3. Add the required entry with allowed mapping of a source list definition (key) to a target list definition (value) as follows: 4. Restart the Quest.MM4SP.Migration2010 service. 5. Create a new migration job to perform migration. Mapping of Domains and Users By default, each SharePoint 2007 user is added as is (with the original domain and user name) to the target SharePoint 2010 site collection users list. You can adjust rules to map a domain and/or a user. User Mapping To map a source user to a different target user during migration, perform the following steps: 1. Open the {MMSPInstallDir}\2k7to2k10_Settings.xml file. 2. Locate the UserMapping property. 3. Add the required entry with the source (key) to target (value) user mapping. For example: Note: If you need to add few mapping rules, add an entry for each rule. 4. Restart the Quest.MM4SP.Migration2010 service. 5. Create a new migration job to perform migration. 178 Chapter 5. Working with Migration Manager for SharePoint

188 Note: The User Mapping is a primary mapping rule. If a user is mapped according to the UserMapping rules, its domain is not mapped according to the UserDomainMapping rules. Domain Mapping To map a source domain to a different domain during migration, perform the following steps: 1. Open the {MMSPInstallDir}\2k7to2k10_Settings.xml file. 2. Locate the UserDomainMapping property. 3. Add the required entry with the source (key) to target (value) domain mapping. For example: Note: If you need to add few mapping rules, add an entry for each rule. 4. Restart the Quest.MM4SP.Migration2010 service. 5. Create a new migration job to perform migration. Disable Features Activation If the Extension Web Service is installed on the target SharePoint 2010 server, Migration Manager initiates features that were activated on the source site. If some features are not available on the target farm, the following error message appears: Feature FeatureName was not activated on the target web Reason: Feature with Id GUID is not installed in this farm, and cannot be added to this scope. To disable feature activation on the target, perform the following steps: 1. Open the {MMSPInstallDir}\2k7to2k10_Settings.xml file. 2. Locate the FeaturesToSkip property. Migrating SharePoint 2007 to

189 3. Add an entry with the GUID of the feature to be skipped. For example: Note: If you need to add few features, add an entry for each rule. 4. Restart the Quest.MM4SP.Migration2010 service. 5. Create a new migration job to perform migration. Taxonomy Mapping Taxonomy mapping allows you to consolidate unmanaged taxonomies in SharePoint 2007 (choice and text fields) to Managed Metadata in SharePoint You need to configure the Managed Metadata service (terms and term sets) and add a Managed Metadata column to target. Migration Manager will map matching choice and text site columns (by name) to it automatically. Depending on how your source column was created, Managed Metadata column should be added to target as follows: 1. The source column is a site column added to a list - add the Managed Metadata column either as Site Column to your target site or to a list. You can add the column either to a site/list definition or to a target pre-created site/list manually before migration. Make sure the source and target columns have the same internal name. 2. The source column is a usual column in a list - add the Managed Matadata column to a list. You can create the column from a list definition or add it to a pre-created target list manualy before migration. Make sure the source and target columns have the same internal name. 180 Chapter 5. Working with Migration Manager for SharePoint

190 6.0 Appendices Appendix A: Importing Jobs from CSV Files Migration Manager for SharePoint allows you to create a migration job automatically by means of importing the job definitions stored in a CSV (comma-separated values) file with a complementary script. The script is located in <installdir>\scripts\jobcreation. CSV File Format A CSV file should provide the following mandatory fields for every migration job you want to create. If either of these fields is not specified, the job import script will fail to create a migration job and report an error. 181

191 FIELD ORDER FIELD NAME DESCRIPTION 1 Name The migration job unique 2 Type (migration One of the following: path) SITE2K3MIGRATION - SharePoint 2003 site to a SharePoint 2007 or SharePoint 2010 site SITECOLLECTION2K3MIGRATION - SharePoint 2003 site/site collection to a SharePoint 2007 or SharePoint 2010 site collection LIST2K3MIGRATION - SharePoint 2003 list to a SharePoint 2007 site or SharePoint 2010 SITE2K7MIGRATION - SharePoint 2007 site to a SharePoint 2007 site or 2010 site to 2010 site SITECOLLECTION2K7MIGRATION * - SharePoint 2007 site/site collection to a SharePoint 2007 site collection or 2010 site/site collection to a new 2010 site collection LIST2K7MIGRATION - SharePoint 2007 list to a SharePoint 2007 site or 2010 list to 2010 site. SITE2010MIGRATION - Share- Point 2007 site to a SharePoint 2010 SITECOLLECTION2010MIGRATION - SharePoint 2007 site/site collection to a SharePoint 2010 site collection LIST2010MIGRATION - Share- Point 2007 list to a SharePoint 2010 site 3 Source URL The source site/list URL 4 Target URL The target site URL 5 Description The job description 182 Chapter 6. Appendices

192 Example: JobName,SITECOLLECTION2K3MIGRATION, Note: For SITECOLLECTION2K7MIGRATION you should set two more parameters: 6-Site Collection Owner 7-Site Collection Owner Example: JobName,SITECOLLECTION2K7MIGRATION, Note: Content database for the target site is automatically selected by SharePoint. If you need to select the database manually, create a job from the web console. By default, the script imports job definitions from the Jobs.csv file in the script folder. Importing Jobs Follow the instruction below to import jobs: 1. Log on to the SharePoint server running Migration Manager as a local administrator. 2. Navigate to <installdir>\scripts\jobcreation. 3. Populate the Jobs.csv file with job descriptions using the sample entry in the file as an example. 4. Run runwebjobcreatorscript.bat to import jobs. 5. Check the import log in JobScripts.log. 6. Start the imported migration jobs in the Migration Manager web console Note: Imported jobs are created in the Stopped state. Appendix A: Importing Jobs from CSV Files 183

193 Appendix B: Permission Migration SharePoint 2003 Permission Migration SharePoint 2007 to 2007/2010 to 2010 Permission Migration SharePoint 2007 to 2010 Permission Migration SharePoint 2003 Permission Migration Migration Manager for SharePoint provides an option of migrating permissions from the source SharePoint 2003 sites, portal site areas to the target SharePoint 2007/2010. By default, permission migration is enabled. Site Permission Migration When permission migration for a particular job is turned on, Migration Manager migrates permissions of the source SharePoint 2003 sites to the target SharePoint 2007/2010 sites as follows: Migrate site as a new site collection When the source site is migrated as a new site collection, Migration Manager configures the target site collection with the corresponding permissions. Permission inheritance for sub-sites is preserved. Migrate site as a sub-site When the source site is migrated as a sub-site, Migration Manager creates the target site with the corresponding unique permissions. The source site with inherited permissions will have unique permissions on the target SharePoint. List Permission Migration When permission migration for a particular job is turned on, Migration Manager translates the access permissions of the source SharePoint 2003 lists to the target SharePoint 2007/2010 lists as follows: Migrate list only 184 Chapter 6. Appendices

194 If a source list is migrated separately from its parent site, Migration Manager configures the target list to inherit permissions from its parent site. Migrate list with its parent site If a source list is migrated with its parent site, Migration Manager configures the target list with the corresponding permissions. Permission inheritance is preserved. Mapping the Source SharePoint 2003 Permissions to the Target SharePoint 2007/2010 Permissions Security model has been changed in SharePoint 2007/2010. SharePoint 2003 site group has specific rights granted directly to the group, while Share- Point 2007/2010 group is associated with the Permission level. Migration Manager creates a corresponding SharePoint 2007/2010 group with the same membership on the target site. The target group name is composed of the source site title and the source site group name (i.e. the Administrator site group on the Unique Permissions Site will be mapped to the Unique Permissions Site Administrator SharePoint 2007/2010 group). Migration Manager maps permissions of a source site group/user to a permission level, using built-in XML mapping as follows: Standard permission sets (Reader, Contributor, Web Designer etc.) are mapped to standard SharePoint 2007/2010 permission levels (Read, Contribute, Design etc.). Custom permission sets are mapped to a new custom permission level named Wss v2 Custom Permission Level <N> (the name of each created permission level contains a number which is incremented when creating a new custom permission level). Migration Manager maps each SharePoint 2003 right to one or more SharePoint 2007/2010 rights using the built-in mapping rules. Note: The mapping rules used by Migration Manager when migrating permissions are described in the WSS3Levels.xml file in the product installation folder (C:\Program Files\Quest Software\Migration Manager). The default mapping rules correspond to the mapping rules used by Microsoft when upgrading from SharePoint 2003 to SharePoint 2007/2010. Appendix B: Permission Migration 185

195 Permission Migration Disabled When permission migration for a particular job is turned off, Migration Manager does not modify the security settings of the target list and site. The target lists and sites created by the migration job inherit permissions from their parents. The target sites created by the migration job will have unique permissions. Permission inheritance for sub-sites is preserved. SharePoint 2007 to 2007/2010 to 2010 Permission Migration During SharePoint 2007 to 2007/2010 to 2010 migration permissions are migrated automatically. Note: Only permissions that have been set at the site and lower levels are migrated. Site Permission Migration Migration Manager migrates permissions of the source SharePoint 2007/2010 site to the target SharePoint 2007/2010 site as follows: When migrating the source root site, Migration Manager configures the target site with the corresponding permissions. When the source site with inherited permissions is migrated, the target site is configured to inherit permissions from its parent. Its subsites preserve the corresponding source permissions. When migrating the source site as a new site collection, the target site collection will have only permissions assigned by the web application policy. Migration Manager assignes the user specified during the job creation the Site Collection administrator rights on the target. List Permission Migration Migration Manager migrates permissions of the source SharePoint 2007/2010 lists to the target SharePoint 2007/2010 lists as follows: 186 Chapter 6. Appendices

196 If a source list / document library is migrated separately from its parent site, Migration Manager configures the target list/document library to inherit permissions from its parent site. If migration is performed between two SharePoint farms located in different AD forests with no trusts between them, the users of the source forest and their permissions are migrated to the target. Note: The users of the source forest will not be able to access the target SharePoint if no trusts between the source and target forests are created. When the trusts are set, all users will access the target SharePoint. You can also replace the source user accounts with the target ones using the STSADM -o migrateuser command. The target users will be configured with the corresponding source permissions (for more information, please refer to: SharePoint 2007 to 2010 Permission Migration Migration Manager allows users to preserve SharePoint security settings (users, groups, roles, permissions) during migration. A user can specify whether to migrate (by default) or skip permissions during job creation. Permission Levels Migration Manager migrates all permission levels (built-in and custom) from the source SharePoint 2007 site, regardless of whether permission levels are inherited or unique Migration Manager recreates all source permission levels, including their names, descriptions and rights mask on the target SharePoint 2010 site Source SharePoint 2007 permission levels are migrated to the nearest parent site with the unique permission level scope Note: SharePoint 2010 UI does not allow users to break permission level inheritance on subsites. See the Permissions for sub-webs section for details: Migration Manager does not break permission level inheritance and always Appendix B: Permission Migration 187

197 migrates SharePoint 2007 permission levels to the root site of the target site collection. If a site with unique permission levels already exists on the target (it is not created by MMSP), source permission levels are added to the existing scope. Permission level mapping and conflict resolution: If the incoming SharePoint 2007 permission level matches (name and rights mask) an existing SharePoint 2010 level, it is mapped to it If the incoming SharePoint 2007 permission level matches an existing 2010 level by name, but has a different rights mask, the incoming permission level is mapped to a new 2010 level named Original Name N (N=1,2,...). If the incoming SharePoint 2007 permission level does not match any existing 2010 level by name, it is created with its original name and rights mask. Users and Groups Migration Manager migrates all SharePoint users and groups which have any permissions for SharePoint objects (sites, document libraries, lists, folders, files and items) below the selected migration root: By default each SharePoint 2007 user is added as is (original user name and domain) to the target SharePoint 2010 site collection users list. A mapping rules can be used to map source user to a target user or source domain to a target domain. Refer to the Mapping of Domains and Users section for more detailed information. If a SharePoint group with the same name already exists in the target site collection (created manually by site admin), Migration Manager maps the incoming 2007 group to a new one named Original Group Name N (N=1,2,...); If the same SharePoint 2007 group is migrated to a target 2010 site collection multiple times (as part of multiple migration jobs), it is mapped to a single SharePoint 2010 group 188 Chapter 6. Appendices

198 If permission migration is not enabled for migration job, Migration Manager only migrates users who created or edited items and documents on the source site(s). Permissions Each uniquely secured SharePoint 2007 object (sites, document libraries, lists, folders, files and items) retains its ACL in SharePoint If a SharePoint 2007 object inherits permissions from its parent, it will inherit permissions in SharePoint 2010 as well. Note: If the root SharePoint object (site or list) of a migration job inherits permissions, Migration Manager makes it a uniquely secured object in SharePoint 2010 and sets the same effective permissions the object had in SharePoint If an object already exists on the target, the source permissions are added to the existing object s ACL. E.g. when a SharePoint 2007 site is migrated to an existing SharePoint 2010 site, the target site ACL will be a combination of migrated and pre-existing permissions. If an object with inherited permissions already exists on the target, permissions inheritance will be broken and current permissions will be extended with the source permissions during migration. Appendix B: Permission Migration 189

199 Appendix C: Checking Database Connection with ODBC To check if a particular database can be accessed, perform the following: 1. Run Start Administrative Tools Data Sources (ODBC) under Migration Manager service user. 2. In the ODBC Data Source Administrator window, click Add to add a new Data Source: 3. Select either SQL Server or SQL Native client drivers. Click Next. 190 Chapter 6. Appendices

200 4. In the Create a New Data Source to SQL Server window, specify Name for the new data source and specify SQL server you want to check: Note: The SQL database name should be the same as used by Migration Manager services. 5. Select With Integrated Windows authenttication radio button on the next window: Appendix C: Checking Database Connection with ODBC 191

201 6. Check the Change the default database to check box and specify the name of the database you want to connect to: 7. Click Finish. 8. The ODBC Microsoft SQL Server Setup is opened: 192 Chapter 6. Appendices

202 9. Click Test Data Source... and check the result: Appendix C: Checking Database Connection with ODBC 193

203 Appendix D: Log Files Location You can change the default log file location to save the disk space. There are the following log files in Migration Manager for SharePoint: Setup logs Migration Manager for SharePoint\Logs\Setup logs\setup.log. Web interface logs Migration Manager for SharePoint\Logs\Web Access logs\ WebAccess.log. To change the default location: 1. Open the Migration Manager for SharePoint\Web Interface\Web Job Wizard\logger.py file. 2. Locate the self.logs_dir = os.path.normpath(os.path.join(os. path.dirname( file ),../../Logs/Web Access logs )) string, and then specify the required value for the self.logs_dir parameter (e.g. self.logs_dir= C:\Logs ). 3. Restart the Quest.MM4SP.WebAccess service /2010 migration logs Migration Manager for SharePoint\Logs\2003\{job name}. Web part pages migration logs The main service log is written to the Migration Manager for Share- Point\Logs\2003\CustomPageMigratorSrv.log file. During the job processing the migration log is written into the corresponding job folder: Migration Manager for Share- Point\Logs\2003\{JobName}\WebParts.log. To change the default location of the CustomPageMigratorSrv.log file: 1. Open the Migration Manager for SharePoint\Web Interface\Custom Page Migrator\Serviceservice.config file. 2. Specify the new location in the logfolderpath parameter. 3. Restart the Quest.MM4SP.CustomPageMigrator service. 194 Chapter 6. Appendices

204 / migration logs Migration Manager for SharePoint\Logs\2007\{job name}. To change the default location: 1. Open the Migration Manager for SharePoint\Web Interface\Migration 2007\Migration2007.config file. 2. Specify the new location in the logfolderpath parameter. 3. Restart the Quest.MM4SP.2k7Source and Quest.MM4SP. 2k7Target services migration logs Migration Manager for SharePoint\Logs\2010\{job name} Appendix D: Log Files Location 195

205 Appendix E: Setting Required Permissions Granting the Log on As a Service Right Granting Local Administrator Rights Setting Permissions on SQL Databases Adding User to the Farm Administrators Adding User to Site Collection Administrators In case of the new installation of Migration Manager, you need to grant appropriate permissions for service accounts. Please refer to the Permissions in Detail section for detailed information on the permissions required for service accounts. Granting the Log on As a Service Right To run the service, the account must have the right to log on as a service on the local computer. Usually the right is automatically granted to the account during installation or when changing service account if it does not have the right: But in some cases you should grant the right manually. Perform the following steps: 1. Click Start > Control Panel > Administrative Tools. 2. Select Local Security Policy. The Local Security Settings snap-in appears. Note: You can run the secpol.msc command to open the Local Security Settings snap-in. 196 Chapter 6. Appendices

206 3. Select Security Settings> Local Policies > User Rights Assignments. 4. Double-click the Log on as a service policy in the right pane. 5. On the Log on as a service Properties dialog, click Add User or Group... and specify the required account. 6. To save the updated policy, click OK. Granting Local Administrator Rights On every computer where Migration Manager for SharePoint is installed, perform the following: 1. Right-click My Computer and select Manage from the short-cut menu. 2. Go to System Tools > Local Users and Groups > Groups if you use Windows 2003 or Server Manager > Configuration > Local Users and Groups > Groups if you use Windows Double-click Administrators in the right pane. Appendix E: Setting Required Permissions 197

207 4. On the Administrators Properties dialog, click Add and specify the required account. 5. To save changes, click OK. Setting Permissions on SQL Databases All service accounts should have permissions for the Quest repository database. For some actions, additional permissions for SharePoint databases are required. A user installing the product for the first time should be able to create the repository database or create required tables if the database already exists. Perform the following steps to grant the required permissions: Add the account to SQL logins: 1. Open MS SQL Server Manager Studio. 2. Expand your SQL instance node. 3. Open the Security node and select the Logins node. 198 Chapter 6. Appendices

208 4. Right-click the Logins and select the New Login option. In the new login window enter the user name in the domain\user format. 5. Click OK. The login appears in the list of the Logins node. Appendix E: Setting Required Permissions 199

209 Grant permissions for a database: 1. Locate the login in the Logins list, and then double-click it. The Login Properties page is displayed. 2. Open the User Mapping page in the left pane, select the Quest repository database and specify the db_owner role for the database. Note: Here you can add permissions for all required databases of the SQL instance. 3. To save your changes, click OK. Note: You can add the dbcreator role from the Server Roles page. Alternatively, you can set permissions for a database as follows: 1. Expand your SQL instance node. 2. Expand the Databases node. Locate the required database, and then expand the Security node. 3. Right-click the Users node and select New user In the Database User - New window, specify the login name. 200 Chapter 6. Appendices

210 5. Select the appropriate permission in the Database role membership pane. 6. To save your changes, click OK. Note: Repeat these steps to grant permissions to service accounts for the content and configuration SharePoint databases. Adding User to the Farm Administrators SharePoint Open Central Administration. 2. Select the Operations tab in the Central Administration window. 3. Open Update farm administrator s group in the the Security Configuration section. The People and Groups: Farm Administrators page appears. 4. Click New. The Add Users: Central Administration page appears. Appendix E: Setting Required Permissions 201

211 5. In the Users/Groups field, enter the name of the user you want to add to the farm administrators group. 6. To save your changes, click OK. The new account appears in the list. SharePoint Open Central Administration. 2. Open the Manage the farm administrators group link in the Security section. 3. Click New. The Grant Permissions page appears. 202 Chapter 6. Appendices

212 4. Specify the required user name and click OK. The new account appears in the list. Adding User to Site Collection Administrators Even if the service account has been added to the Farm Administrators, it still cannot upload content on the target site. You should add the account to Site Collection Administrators for an individual site collection or use Policy for Web Application to grant administrative rights for all site collections within a web application. SharePoint Open Central Administration. 2. Select the Application Management tab in the Central Administration window. 3. Open Policy for Web application in the Application Security section. The Policy for Web Application window appears. 4. Click Add Users. 5. Select the required web application from the drop-down list and click Next. Appendix E: Setting Required Permissions 203

213 6. In the Choose Users field, specify the user and select the Full Control check box in the Choose Permissions field. 7. Click Finish. The Policy for Web Application window displays the new user permissions. SharePoint Open Central Administration. 2. Go to the Security section. 3. Open the Specify web application user policy link. 4. Click Add Users. 5. Select the required web application from the drop-down list and click Next. 6. In the Choose Users field, specify the user and select the Full Control check box in the Choose Permissions field. 7. Click Finish. The Policy for Web Application window displays the new user permissions. 204 Chapter 6. Appendices

214 Appendix F: Discovery Issues Adding a SharePoint farm may fail by some reason. When you add a farm to Migration Manager, a QMC component called discover is started. Discovery logs are written into Quest Software\Management Console for Share- Point\Console\Logs\QsSPDiscovery.log or Quest Software\Site Administrator for SharePoint\Console\Logs\QsSPDiscovery.log if you have Quest Site Administrator installed. In the log file you can find the exact reason why the farm cannot be discovered. Lack of Permissions Farm discovery is started by the Quest.MM4SP.SPBrowserBroker service on a local server. It is running under the SPBrowserBroker user. Make sure the account has the follwowing permissions: Member of the Local Administrators group on the SharePoint server being discovered. The permission is required to read the registry on the server to get information about the installed SharePoint and read IIS metabase to get web application configuration. The db_datareader role for the configuration and content databases of the SharePoint farm being discovered. The permission is required to read SharePoint configuration in the databases. Note: When accessing a remote database, connection issues may occur. To check if the database could be successfully accessed by the service account from the discovering server, you could perform ODBC connection test. The db_owner role for the Quest Repository database. The permission is required to write SharePoint farm configuration into the Repository database. Appendix F: Discovery Issues 205

215 Firewall Blocks SharePoint Server Firewall may prevent discovery of the farm. While discovering a SharePoint farm, Migration Manager reads registry of the SharePoint server and IIS metabase using Windows Management Instrumentation (WMI), and configuration and content databases of the farm. The following ports should be opened for the farm located behind a firewall: SQL ports. The default instance of the Database Engine uses port Refer to the following article for more details: Configure a Firewall for SQL Server Access WMI/RPC ports. Services typically use 135 and 445 ports to communicate using Remote Procedure Calls (RPC) and Distributed Component Object Model (DCOM). In addition, RPC uses the port range of 1024 to 5000 for allocating ports for endpoints. You can configure custom port range. Refer to the following articles for detailed information: How to configure RPC to use certain ports and How to configure RPC dynamic port allocation to work with firewalls If you use Windows firewall, you may enable the Allow remote administration exception policy to allow WMI connection. Refer to the Connecting Through Windows Firewall article for detailed information. Once you have discovered the required farm, you can close WMI/RPC ports. Install QMC locally to add a farm If you do not want to open WMI/RPC ports, you can install QMC to a Share- Point server in the farm and perform the discovery process in the Quest Management Console. During discovery the farm is added to the Repository database and can be used in Migration Manager. Note: Open SQL ports in firewall to access the Repository database. Perform the following steps to add a farm: 1. Install QMC and specify already existing database of Migration Manager during installation: Installing Quest Management Console for Share- Point. 2. Click Cancel when Migration Manager Wizard opens. 206 Chapter 6. Appendices

216 3. Run Quest Management Console from {ProgramFiles- Folder}\Quest Software\Management Console for Share- Point\Console\qsSiteAdminForSharePoint.msc 4. Right-click the Enterprise SharePoint node and select Add Farm. 5. In the Welcome window, click Next. 6. In the Specify SharePoint Front-End server window, enter either NETBIOS, DNS name, or IP address of the SharePoint server and click Next. 7. Once discovery is complete, exit the wizard. Appendix F: Discovery Issues 207

217 Now you can see your farm under Enterprise SharePoint. 208 Chapter 6. Appendices