Quest Migration Manager 3.2

(1)

Quest

®

Migration Manager

3.2 for SharePoint

(2)

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 92656 e-mail: [email protected]

(3)

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

http://www.quest.com/legal/trademark-information.aspx. Other trademarks and registered trademarks used in this guide are property of their respective owners. Third Party Contributions

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

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

Updated – March, 2011 Software version – 3.2

(4)

1 About Quest Software, Inc. 1

Contacting Quest Software . . . 1

Contacting Quest Support . . . 1

2 General Information 3 About Quest Migration Manager for SharePoint 3.2 . . . 3

Major Features . . . 5 General Features . . . 5 SharePoint 2010-2010 . . . 5 SharePoint 2007-2010 . . . 5 SharePoint 2007-2007/2010-2010 . . . 6 SharePoint 2003-2007/2003-2010 . . . 6

Supported SharePoint Features . . . 6

SharePoint 2003 to 2007/2003 to 2010 Migration . . . 6

SharePoint 2007 to 2007 (SharePoint 2010 to 2010) Migration 8 SharePoint 2007 to 2010 Migration . . . 9

3 How Migration Manager for SharePoint Works 11 Web Console . . . 12 Services Involved . . . 12 Architecture . . . 12 Required Permissions . . . 13 Logs . . . 14 SharePoint 2003 to 2007/ 2003 to 2010 Migration . . . 15

Base Content Migration . . . 15

Services Involved . . . 15

Architecture . . . 15

Required Permissions . . . 17

(5)

Services and Scheduled Tasks Involved . . . 18 Architecture . . . 18 Required Permissions . . . 18 Logs . . . 19 SharePoint 2007 to 2007/ 2010 to 2010 Migration . . . 20 Services Involved . . . 20 Architecture . . . 20 Required Permissions . . . 22 Logs . . . 23 SharePoint 2007 to 2010 Migration . . . 24 Services Involved . . . 24 Architecture . . . 24 Required Permissions . . . 25 Logs . . . 26

4 Deploying Migration Manager 27 System Requirements . . . 27

SharePoint 2003 Server . . . 27

Migration Manager Host Server . . . 28

Required Permissions . . . 29

Permissions Matrix . . . 29

Permissions in Detail . . . 30

Services Responsible for Migration Manager User Inter-face Workability . . . 31

Services Responsible for 2003 to 2007/2003 to 2010 Mi-gration . . . 31

Services Responsible for 2007 to 2007/ 2010 to 2010 Mi-gration . . . 34

Services Responsible for 2007 to 2010 Migration . . . 35

Additional Services and Scheduled Tasks . . . 36

Pre-installation Steps . . . 37

Installing Message Queuing on Windows Server 2003 . . . 37

Installing Message Queuing on Windows Server 2008 . . . 37

Starting the Task Scheduler Service . . . 38

(6)

Single Agent Deployment . . . 40

Two Agent Deployment . . . 41

Deploying Migration Manager for SharePoint 2007-2007/2010-2010 Migration . . . 42

Installing Migration Manager on SharePoint 2007/2010 Farms . 42 Deploying Migration Manager for SharePoint 2007-2010 Migration . 43 Installing Migration Manager on SharePoint 2007 Farm . . . 44

Installing Migration Manager Extension Web Service . . . 44

Deploying Service Using MSI Package: . . . 45

Deploying Service Using PowerShell Scripts: . . . 46

PowerShell Execution Policy . . . 47

Deploying Service Using Native SharePoint 2010 Tools: . 48 Upgrading Extension Service . . . 49

Installing Migration Manager on SharePoint Server . . . 49

Installing Quest Management Console for SharePoint . . . 50

Installing Migration Manager for SharePoint . . . 50

Installing to a Pre-Created Database . . . 52

Adding SharePoint Farms . . . 54

Upgrading Migration Manager . . . 56

Upgrading Web Console . . . 56

Upgrade for 2003-2007/2003-2010 Migration . . . 56

Upgrade for 2007-2007 Migration . . . 57

Installing Update . . . 58

Upgrade for 2007-2010 Migration . . . 58

Managing Licenses . . . 59

Viewing Con guration . . . 59

5 Working with Migration Manager for SharePoint 61 Getting Started . . . 61

Delegating Access to Web Console . . . 62

Migrating SharePoint 2003 to 2007/2003 to 2010 . . . 63

Choosing Between Migration Job Options . . . 63

Creating Migration Jobs . . . 63

Creating Job for Site Migration . . . 64

Creating Job for List Migration . . . 72

Migration Job Details . . . 77

Managing Migration Jobs . . . 80

Managing a Job . . . 80

(7)

State Report . . . 83

Issue Report . . . 85

Agents Report . . . 86

Web Part Migration . . . 88

Con guring Stored Credentials . . . 90

Migration Jobs Views . . . 90

Migration Job Lifecycle . . . 92

Con guring Migration Hours . . . 94

Target Version Selection . . . 95

Synchronizing Content . . . 96

SharePoint Portal Site and Areas Migration . . . 97

Migrate SharePoint 2003 Portal Site to a New Site Collection 97 Migrate Portal Site/Sub-area to a Site . . . 97

Migrate Sub-area to a New Site Collection . . . 97

Permission Migration for Custom Portal Template . . . 98

SharePoint Site Template Mapping . . . 99

Transforming a Custom SharePoint 2003 Site into a Stan-dard SharePoint 2007/2010 Site . . . 100

Transforming a Standard SharePoint 2003 Site into a Cus-tom SharePoint 2007/2010 Site . . . 101

How Site Template Mapping Works . . . 102

SharePoint List Template Mapping . . . 107

Setting Mapping Rules . . . 108

Mapping of Domains and Users . . . 109

User Mapping . . . 110

Domain Mapping . . . 110

Firewall Con guration . . . 111

Single Agent Deployment . . . 112

Two Agents Deployment . . . 112

Migrating SharePoint 2007 to 2007/2010 to 2010 . . . 114

(8)

Agents Report . . . 138

Synchronizing Content . . . 142

Full Resync . . . 143

Incremental Sync . . . 143

Exclude feature from migration (2007-2007 or 2010-2010) . . 143

Migrating SharePoint 2007 to 2010 . . . 145

Managing a Job . . . 161

Managing Multiple Jobs . . . 163

Monitoring Migration Jobs . . . 164

Con guring Migration Hours . . . 171

Migration Extensions for SharePoint 2010 . . . 172

Audit Metadata . . . 173

Site Regional Settings . . . 173

Site Theme . . . 173 Site Logo . . . 173 Features Activation . . . 173 Alerts Migration . . . 174 Taxonomy Mapping . . . 174 Synchronizing Content . . . 175 Mapping 2007 to 2010 Templates . . . 175

Site Template Mapping . . . 176

List Template Mapping . . . 176

Allowed Trasformation of List Templates . . . 177

(9)

Domain Mapping . . . 179

Disable Features Activation . . . 179

Taxonomy Mapping . . . 180

6 Appendices 181 Appendix A: Importing Jobs from CSV Files . . . 181

CSV File Format . . . 181

Importing Jobs . . . 183

Appendix B: Permission Migration . . . 184

SharePoint 2003 Permission Migration . . . 184

Site Permission Migration . . . 184

List Permission Migration . . . 184

Mapping the Source SharePoint 2003 Permissions to the Target SharePoint 2007/2010 Permissions . . . . 185

Permission Migration Disabled . . . 186

SharePoint 2007 to 2007/2010 to 2010 Permission Migration . 186 Site Permission Migration . . . 186

List Permission Migration . . . 186

SharePoint 2007 to 2010 Permission Migration . . . 187

Permission Levels . . . 187

Users and Groups . . . 188

Permissions . . . 189

Appendix C: Checking Database Connection with ODBC . . . 190

Appendix D: Log Files Location . . . 194

Appendix E: Setting Required Permissions . . . 196

Granting the Log on As a Service Right . . . 196

Granting Local Administrator Rights . . . 197

Setting Permissions on SQL Databases . . . 198

Adding User to the Farm Administrators . . . 201

SharePoint 2007 . . . 201

Adding User to Site Collection Administrators . . . 203

Appendix F: Discovery Issues . . . 205

Lack of Permissions . . . 205

Firewall Blocks SharePoint Server . . . 206

(10)

Now more than ever, organizations need to work smart and improve ef -ciency. Quest Software creates and supports smart systems management products-helping our customers solve everyday IT challenges faster and eas-ier. Visithttp://www.quest.comfor more information.

Contacting Quest Software

E-mail: [email protected]

Mail: Quest Software, Inc. World Headquarters 5 Polaris Way

Aliso Viejo, CA 92656 USA

Web site: http://www.quest.com

Refer to our Web site for regional and international of ce 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 mainte-nance contract. Quest Support provides unlimited 24x7 access to Support-Link, our self-service portal. Visit SupportLink athttp://support.quest.com.

(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 pro-grams, online services, contact information, policies, and procedures. The guide is available at: http://support.quest.com.

(12)

About Quest Migration Manager for SharePoint 3.2

Quest Migration Manager for SharePoint provides a reliable solution to reor-ganize, 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 instal-lations to a central managed location.

ˆ Consolidate SharePoint content from scattered SharePoint Foundation 2010 or SharePoint Server 2010 installations to a central managed lo-cation.

ˆ Minimize impact on the production systems and end users by scheduling resource-intensive migration tasks for off-peak hours.

(13)

ˆ Con gure and monitor content migration tasks remotely in a web browser (all major browsers are supported).

(14)

Major Features

General Features

ˆ Facilitates migration project management with pre-migration assess-ment, migration job controls, real-time progress reporting and schedul-ing

ˆ Supports the following versions of Microsoft SharePoint: Windows SharePoint Services 2.0 and 3.0, SharePoint Portal Server 2003, Of ce 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 de nitions stored in a CSV (comma-separated values) le.

SharePoint 2010-2010

ˆ 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 2007-2010

ˆ Migrate SharePoint 2007 sites including content, metadata and security settings to the new platform

ˆ Preserve the look and feel settings of the SharePoint 2007 sites ˆ Migrate web part pages including layout and web parts

(15)

SharePoint 2007-2007/2010-2010

ˆ 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 speci c content databases to optimize site storage

ˆ Transfer SharePoint content within a single server and between Share-Point farms.

SharePoint 2003-2007/2003-2010

ˆ Migrate SharePoint 2003 sites including content and security settings to the new platform

ˆ 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

(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

con-guration. 6. Folders

7. Authorship (Created By/Modi ed By) for content 8. Lists

ˆ Generic lists (Contacts, Tasks, Events, Custom List, etc.) ˆ Document libraries

ˆ Issues lists

ˆ Discussion boards ˆ Surveys

ˆ Custom list de nitions

Note: To migrate lists based on custom list templates/de nitions you

might need to adjust list template mapping in the product con gura-tion.

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

(17)

ˆ Document workspaces ˆ Meeting workspaces ˆ Custom site templates

Note: To migrate sites based on custom site templates/de nitions you

might need to adjust web template mapping in the product con gura-tion.

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. Work ow state and tasks

(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

Man-ager Extension Web Service. 4. Users and security permissions:

ˆ Users

(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/Modi ed 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. E-mail alerts

(20)

SharePoint Works

This section contains complete information about Migration Manager for SharePoint (MMSP). Here you will nd 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 con guration 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

(2003-2007/2003-2010, 2007-2007/2010-2010, and 2007-2010), different services are responsible for them. Let's look at each part in more detail.

(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 web-console workability. All users' requests from the web-web-console to the repository database are performed under the Web Access service ac-count.

ˆ Quest.MM4SP.SPBrowserAgent and Quest.MM4SP.SPBrowserBroker

are Windows services. They request con guration and content

databases of the source and target SharePoint for information about the server farm.

Architecture

During installation, MMSP de nes 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 http://MMSPhost:port 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 con gure 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 infor-mation about the existing SharePoint structure (web applications, site collec-tions, 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 permis-sions to access both farms. If a two-agent deployment is used, the Agents

(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 con guration 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.

(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 les 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

(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.

ˆ Quest.MM4SP.SourceService is a Windows service. It extracts con-tent from source SharePoint 2003 servers using SQL calls to the corre-sponding SharePoint content databases.

ˆ Quest.MM4SP.TargetService is a Windows service. It uploads con-tent 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 st 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.

(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 de-ployment scenarios:

Single agent deployment should be used if you have a single

Share-Point administrative account to access both the source and target ShareShare-Point 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.

(26)

Source service account:

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:

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 col-lections (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 les into the following location on the corre-sponding 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 followingsectionfor more details.

During base content migrations, web parts for home page and web

part pages from document libraries are not migrated. They are

mi-grated in a separate web part migration job. Starting from

Migra-tion Manager v3.0 web part migraMigra-tion 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 doc-ument 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 CustomPageMi-grator 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.

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.

(28)

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 con gured. Refer to the Con guring 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 le

on the target MMSP host: {MMSP installation

direc-tory}\Logs\2003\CustomPageMigratorSrv.log

ˆ During the job processing the migration log is written into the corre-sponding 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.

(29)

SharePoint 2007 to 2007/ 2010 to 2010 Migration

SharePoint 2007 to 2007/ 2010-2010 migration has different migration mechanism and all content is migrated simultaneously.

ˆ 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 2007-2007/2010-2010 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 st job has been exported.

(30)

Temporary Storage of Exported Content

Each time the 2k7Source service is started, it creates the

qmmsp-ex-port$ 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 migra-tion agent is installed.

2. Open the ExportFolderPath.py le located in {MMSP

instal-lation folder}\Web Interface\Migration 2007. The original

folder path and the instructions on how to modify it are in the le. 3. Make your changes, save the le and restart the 2k7Source service. By default, the folder is created with the Read/Write access to Every-one. 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.

(31)

The following diagram displays architecture of 2007-2007/2010-2010 migra-tion for intra-farm migramigra-tion:

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.

2k7Source service account:

1. The db_owner role for the Quest repository database.

3. The Site Collection Administrator permissions in the source site col-lections (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.

3. Member of the Farm Administrators group in the SharePoint 2007 farm.

(32)

Logs

ˆ 2007-2007/ 2010-2010 migration writes log les into the following lo-cation 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.

(33)

SharePoint 2007 to 2010 Migration

SharePoint 2007 to 2010 migration uses new Client Object Model of Share-Point 2010. Migration Manager accesses target ShareShare-Point 2010 remotely, that means it should be installed on the source farm. Refer to the

Deploy-ing Migration Manager for SharePoint 2007-2010 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.

ˆ 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.

(34)

The following diagram displays architecture of 2007-2010 migration:

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 tar-get 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.

(35)

Logs

ˆ 2007-2010 migration writes log les into the following location on the source SharePoint 2007 server:

(36)

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

Mi-gration Manager. The prescan tool can be downloaded at:

http://www.microsoft.com/downloads/details.aspx.

Migration Manager supports the following SharePoint versions: ˆ Microsoft Of ce SharePoint Server 2007

ˆ Windows SharePoint Services 3.0

(37)

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 ShareShare-Point 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 2007-2007/2010-2010 migration) ˆ Workstation service (for 2007-2007/2010-2010 migration)

4. Access to an instance of Microsoft SQL Server to host a repository database for Migration Manager:

ˆ Microsoft SQL Server 2005 SP1 or later SPs ˆ Microsoft SQL Server 2008

5. Other:

ˆ Microsoft .Net 3.0 Framework

(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 Migra-tion 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

collec-tion administrator rights for all site colleccollec-tions within a web applicacollec-tion. For detailed information, please refer to the Permissions in Detail section.

(39)

Permissions in Detail

The user installing the product (Installation User) must have the following permissions:

ˆ 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

OR

ˆ 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 speci ed 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 con guration le. For more information, please refer to Delegating Access to Web Console.

(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.

MM4SP.WebAccess) The Log On As Service righton the MMSP host Member of the Local

Admin-istrators group on the MMSP

host

The db_owner role for the Quest repository database

The target (one

agent

deploy-ment) OR

The source and the target (two

agent deploy-ment) 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

Admin-istrators 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 con guration and content databases

The target (one

agent

deploy-ment) OR

The source and the target (two

agent

deploy-ment)

Services Responsible for 2003 to 2007/2003 to 2010 Migration

The following permissions are required for services:

(41)

Source Service

(Quest.MM4SP.Source Service)

host

The db_owner role for the Quest repository database The db_datareader role for the SharePoint 2003 content databases

The target (one

agent deploy-ment) OR The source 2003 server (two agent deploy-ment) Target Service (Quest.

MM4SP.TargetService) The Log On As Service righton the MMSP host Member of the Local

host

The db_owner role for the Quest repository database The db_owner role for the

target SharePoint content

databases

Member of the Farm

Admin-istrators group in the target

SharePoint farm

The Site Collection

Adminis-trator permissions in the

tar-get site collections (per site collection) OR Full Control granted via the Policy for

Web application (for all site

collections within the web appli-cation)

(42)

Quest Custom Page

Migrator (Quest.

MM4SP.CustomPage Migrator)

host

The db_owner role for the

target SharePoint content

databases

Member of the Administrator site group on the source Share-Point 2003 sites

The target

(43)

Services Responsible for 2007 to 2007/ 2010 to 2010 Migration

2k7 Source (Quest.

MM4SP.2k7Source) The db_owner role for theQuest repository database Member of the Local

host

Admin-istrator permissions in the

source site collections (per site collection) OR Full Control granted via the Policy for

collections within the web appli-cation).

The source

2k7 Target (Quest.

MM4SP.2k7Target) The db_owner role for theQuest repository database Member of the Local

host

Admin-istrators group in the target

SharePoint farm

(44)

Services Responsible for 2007 to 2010 Migration

Migration 2010

(Quest.MM4SP.

Mi-gration2010)

Adminis-trators group

The db_owner role for the Quest repository database The db_owner role for the

source SharePoint content

databases

Admin-istrators group in the source

and target SharePoint farm The Site Collection

Admin-istrator permissions in the

source and target site collec-tions (per site collection) OR

Full Control granted via the Policy for Web application

(for all site collections within the web application).

The source

(45)

Additional Services and Scheduled Tasks

Service Monitor

(Quest.MM4SP.Service Member of the Local Admin-istrators group on the MMSP

host

The source and the target

The following permissions are required for scheduled tasks:

SCHEDULED TASK REQUIRED PERMISSIONS RUNNING ON

Quest Compress Old

Logs Member of the Local Admin-istrators group on the MMSP

host

The source and the target

Quest SharePoint

Proxy The account used to run thisscheduled task must have the same permissions as the Target Service

The source and the target.

(46)

Pre-installation Steps

Before installing Migration Manager for SharePoint, install Microsoft Message Queuing (required for 2003-2007/2003-2010 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, per-form 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

Queu-ing on Windows Server 2003, please follow the link:

http://technet.microsoft.com/en-us/library/cc756973.aspx.

Installing Message Queuing on Windows Server 2008

To install Microsoft Message Queuing Service on Windows Server 2008, per-form 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.

(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

Queu-ing on Windows Server 2008, please follow the link:

http://technet.microsoft.com/en-us/library/cc730960.aspx.

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

(48)

Deployment Matrix

To perform different migration scenarios, Migration Manager requires differ-ent deploymdiffer-ents. The deploymdiffer-ent 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 2003 source (optional) See more >> Install MM on 2007 tar-get Install MM on 2003 source (optional) See more >> SHAREPOINT 2007 Install MM on 2007 source

Install Extension service on 2010 target

See more >>

Install MM on 2007 source

Install MM on 2007 target (use the same repository database)

See more >>

SHAREPOINT 2010 Install MM on 2010 source

Install MM on 2010 target (use the same repository database)

See more >>

Not Supported

(49)

Deploying Migration Manager for SharePoint

2003-2007/2003-2010 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 compo-nents 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 instruc-tions 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 ad-ministrative 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

(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 instruc-tions 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

re-quired 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 in-structions 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 speci ed 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

re-quired for the farm. It is recommended to use the existing Share-Point farm administrator account.

3. Grant the accounts speci ed in step 1 and 2 the db_owner rights to the repository database created in step 1.

(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

2007-2007/2010-2010 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 pre-requisite components are installed on the servers where you will install Mi-gration Manager for SharePoint. Refer to the System Requirements section for more detailed information.

Installing Migration Manager on SharePoint 2007/2010 Farms

Install and con gure 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 rst SharePoint farm and specify this database for all other Migration Manager installations on additional farms.

(52)

Note: For multi-agent installation of Migration Manager you should use the same repository database.

ˆ Migration Manager Service account - specify the SharePoint ad-ministrative 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 1.

3. 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 informa-tion, refer to the Adding SharePoint Farms section).

Deploying Migration Manager for SharePoint 2007-2010

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 Man-ager 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 compo-nents are installed on the servers where you will install Migration Manager for SharePoint. Refer to the System Requirements section for more detailed information.

(53)

Installing Migration Manager on SharePoint 2007 Farm

Install and con gure 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 instruc-tions 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 rst SharePoint 2007 farm and specify this database for all other Migration Manager in-stallations on additional farms.

ˆ Migration Manager Service account - specify the SharePoint ad-ministrative 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 Mi-gration Manager service account you used to install MiMi-gration Manager in Step 1.

3. Install the Migration Manager Extension Web Service on the target SharePoint 2010 server farm. Follow instructions in the Installing

Mi-gration Manager Extension Web Service section.

4. To allow Migration Manager to migrate content, your source and tar-get SharePoint farms should be added to Migration Manager. The local SharePoint 2007 farm is automatically added to Migration Manager dur-ing 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.

(54)

To install the service, you should deploy the Quest.MMExtension.wsp so-lution 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 2010.

ˆ 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.

(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 > ShareShare-Point 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

fail-ure. Refer to the PowerShell Execution Policy section for more de-tails.

E.g. The MMExtension folder is copied to the C: drive. You should run the following:

PS C:\Users\administrator.KARELIA> &"C:\MMExtension\install-mmextension.ps1" "C:\MMExtension\quest.mmextension.wsp" 4. Wait for the script results.

To remove Migration Manager Extension Web service using PowerShell scripts:

(56)

1. Run SharePoint 2010 Management Shell under the farm administrator account on the target server by selecting Start > Microsoft

Share-Point 2010 Products > ShareShare-Point 2010 Management Shell.

2. In the PowerShell console, type the following:

&"{PathToMMExtensionFolder}\uninstall-mmextension.ps1"

E.g.

PS C:\Users\administrator.KARELIA> &"C:\MMExtension\uninstall-mmextension.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.

(57)

When the AllSigned policy is set, you will be asked if you trust Quest Soft-ware certi cate:

When you accept the certi cate, 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

(58)

Remove-SPSolution -Identity Quest.MMExtension.wsp -Confirm:$false

ˆ STSADM

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 auto-matically. If you install the extension serice using the script or native tools, uninstall (delet) the existing solution package, and then install the new ver-sion.

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 le

The Quest Management Console Setup wizard starts, which installs the com-mon components and con guration for Quest SharePoint products.

(59)

Installing Quest Management Console for SharePoint

Perform the following steps:

1. On the Welcome screen, click Next.

2. On the Con guration Database page, specify the database to be used to store the Migration Manager data (Quest Repository Database).

For your rst installation of Migration Manager specify to create a

new database. When installing additional Migration Manager instances, which will share the same con guration, specify the database created during the installation of the rst 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

reposi-tory 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.

(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.