2.0. Quick Start Guide

2.0 Quick Start Guide

Copyright Quest Software, Inc. 2007. 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. DISCLAIMER The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document. TRADEMARKS Quest Public Folder Migrator for SharePoint is a trademark of Quest Software, Inc. Other trademarks and registered trademarks used in this guide are property of their respective owners. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 www.quest.com e-mail: info@quest.com Please refer to our Web site for regional and international office information. Quest Public Folder Migrator for SharePoint Updated October, 2007 Software version 2.0

Contents ABOUT QUEST SOFTWARE, INC.... 3 CONTACTING QUEST SOFTWARE...3 CONTACTING QUEST SUPPORT...3 INTRODUCTION... 5 ABOUT THIS DOCUMENT...5 PRODUCT OVERVIEW...5 Key Features...5 Terminology...6 TEST LAB CONFIGURATION... 7 COMPUTERS...7 Exchange Server...7 SharePoint Server (WSS Server)...7 ACCOUNTS AND RIGHTS...8 Service Account...8 User Account...9 SETTING UP THE SOURCE AND TARGET...9 Creating a Source Folder Structure...9 Creating a Target Company Web Site... 10 INSTALLATION... 11 CASE STUDIES... 12 MIGRATING PUBLIC FOLDER TO LIST... 12 Permission Considerations... 12 Migration... 13 MIGRATING A PUBLIC FOLDER TREE TO A DOCUMENT LIBRARY... 15 Permission Considerations... 15 Migration... 15 MIGRATING A PUBLIC FOLDER TREE TO A SITE... 17 Migration... 18 SCHEDULING MIGRATION... 19 RESTARTING A MIGRATION JOB... 21 SUMMARY... 22 APPENDIX: SHAREPOINT 2007 MAPPING RULES... 23 i

About Quest Software, Inc. Quest Software, Inc. delivers innovative products that help organizations get more performance and productivity from their applications, databases and Windows infrastructure. Through a deep expertise in IT operations and a continued focus on what works best, Quest helps more than 18,000 customers worldwide meet higher expectations for enterprise IT. Quest s Windows Management solutions simplify, automate and secure Active Directory, Exchange and Windows, as well as integrate Unix and Linux into the managed environment. Quest Software can be found in offices around the globe and at www.quest.com. Contacting Quest Software Email Mail Web site info@quest.com Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA www.quest.com 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 commercial version and have a valid maintenance contract. Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at http://support.quest.com From SupportLink, you can do the following: Quickly find thousands of solutions (Knowledgebase articles/documents). Download patches and upgrades. Seek help from a Support engineer. Log and update your case, and check its status. View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures. The guide is available at: http://support.quest.com/pdfs/global Support Guide.pdf 3

Introduction About This Document This document explains how to deploy Quest Public Folder Migrator for SharePoint in a test lab, and provides instructions for typical migration jobs. Product Overview Public Folder Migrator for SharePoint helps you bring corporate information management and intra-org collaboration to a new level. Public Folder Migrator for SharePoint facilitates the migration of data stored in public folders on Exchange Server to SharePoint Server while preserving the folder hierarchy to ensure data consistency and availability. With your data assets moved to SharePoint Server, you can benefit from its advanced features to enhance information sharing and document collaboration, thereby increasing individual and team productivity. Key Features Integration with Site Administrator Automatic migration of public folder content from Exchange Server to SharePoint Server Migration of public folder content to a discussion board Importing job definitions stored in a CSV file to create a job automatically Easy-to-Use Migration Job Wizard Built-in migration paths Flexible scheduling options for the migration process Migration job monitoring Out-of-the-box mapping templates Permissions mapping Public Folder access revocation after migration Redirection of users to the target after the migration is complete Roll Back of folder switch SharePoint limitations overcome 5

Quest Public Folder Migrator for SharePoint Terminology This section describes Public Folder Migrator for SharePoint basic terms and concepts. Migration agent A service installed on a local computer (migration job processor) that runs one or more migration jobs. By default, this service is scheduled to always run and, therefore, it has to process all enabled migration jobs assigned to it. Migration job A job that allows you to configure the migration workflow by selecting the Exchange source, the SharePoint target, the structures to be created on target (list, document library, or Web site), and other settings. Migration path When you configure a migration job, you choose for the SharePoint target one of three types of object: list, document library, or Web site. This choice determines how the source public folder contents and hierarchy are migrated, or the migration path. Redirection After the migration process is complete, users who attempt to access source public folder content are redirected to the corresponding target object (list, document library, or Web site) on the SharePoint server. For example, a user who wants to access a public folder with mail and post items in Microsoft Outlook is taken to the corresponding discussion board on the SharePoint Web site (which is displayed in the right pane). You can redirect users automatically immediately after synchronization completes, or schedule the start of redirection. Source The Exchange Server where the public folders are originally stored. Synchronization A post-migration process that transfers data not transferred during the scheduled migration process, such as new content that appeared on source after the migration started. Target The SharePoint server where the content of the public folders will be stored after the migration. 6

Quick Start Guide Test Lab Configuration Computers For the case studies, we need a test lab with two computers configured as follows: Exchange Server REQUIREMENT NOTES Operating system: Microsoft Windows Server 2000 or later This computer must also be a domain controller for the test domain (LAB). One of the following messaging systems: Microsoft Exchange 2000 Server SP3 or later with latest updates installed Microsoft Exchange Server 2003 SP2 Microsoft Exchange Server 2007 SharePoint Server (WSS Server) REQUIREMENT NOTES Memory: 1 GB recommended Operating system: Microsoft Windows Server 2003 SP1 or later One of the following: Microsoft Office SharePoint Server 2007 Windows SharePoint Services 3.0 One of the following: Microsoft SQL Server 2000 SP4 (remote or local) Microsoft SQL Server 2005 (remote or local) 7

Quest Public Folder Migrator for SharePoint REQUIREMENT NOTES Microsoft Exchange Server MAPI and Collaboration Data Objects 1.2.1. For more information, see http://www.microsoft.com/downloads/details.a spx?familyid=e17e7f31-079a-43a9-bff2-0a110307611e&displaylang=en. Quest Site Administrator for SharePoint 1.6 Site Administrator for SharePoint should be installed and configured as explained in the Quest Site Administrator for SharePoint 1.6 User Guide. Accounts and Rights Service Account During setup, you will need to specify the service account under which the migration agent will run on the agent host. This account must be granted the following rights and permissions: Local Administrator permission on the agent host Log on as service permission on the agent host Owner permission for the Site Administrator configuration database Owner permission for the SharePoint back-end databases (to modify their configuration and content) Exchange View Only Administrator rights for the Exchange organization Full control and Send as/receive as permissions (explicitly granted) for the source Exchange server Administrator rights for Exchange 5.5 Administrative rights for the SharePoint front-end Web servers Site collection administrator rights to access the target site collections 8

Quick Start Guide User Account The user account under which you will run the Quest Site Administrator for SharePoint management console must be granted the following rights and permissions: Local Administrator permission on the computer where the Quest Site Administrator for SharePoint management console is installed Owner permission for the Site Administrator configuration database Owner permission for the SharePoint back-end databases (to modify their configuration and content) Exchange View Only Administrator rights for the Exchange organization Read and Administer Information Store rights for the source Exchange server Administrator rights for Exchange 5.5 Administrative rights for the SharePoint front-end Web servers Site collection administrator rights to access the target site collections Setting Up the Source and Target Creating a Source Folder Structure To perform the case studies described in this guide, you need to create the following public folder structure in your test Exchange organization: All Public Folders Departments Accounting... Executives... IS... Sales... Public Documents... Offices 9

Quest Public Folder Migrator for SharePoint You also need to supply sample public folder contents, keeping in mind the following: The Departments folder contains department-level information in public folders, one for each department. The Public Documents folder contains folders with mail and post items, including an Obsolete folder with out-of-date documents. The Offices folder contains information on contacts. Creating a Target Company Web Site 1. We assume that the target SharePoint server (WSS Server) has been configured in the sample LAB domain, and that it has been added to Site Administrator for SharePoint as described in the Quest Site Administrator for SharePoint Quick Start Guide. 2. LabAdmin account is a test account under which you run the Quest Public Folder Migrator setup; it must be a member of Local Administrators group on the SharePoint server (WSS Server). The procedure described below will help you create a new top-level SharePoint site named Company Web with the following address: http://wss-server/sites/companyweb. To create a site, run the Quest Site Administrator for SharePoint management console and take the following steps: 1. Run Enterprise SharePoint. 2. Right-click the WSS Server node and select Virtual Server Tasks from the shortcut menu. 3. Select the Create Top-Level Web Site option and specify the LabAdmin account credentials when prompted. The Create Site Collection page opens in the right pane. 4. In the Title and Description area, specify the title Company Web and an optional site description. 5. In the Web Site Address area, select sites and type companyweb in the URL field. 6. In the Template Selection area, select the Team Site template from the Select a template list. 7. In the Primary Site Collection Administrator area, specify LAB\LabAdmin in the User name field. 8. Click OK to create the site. Now you can see the new top-level site Company Web in the WSS Server node. 10

Quick Start Guide Installation When SharePoint 2007 (Microsoft Office SharePoint Server 2007 or Windows SharePoint Services 3.0) is installed in your environment, you can use the native SharePoint object model to upload the public folder content into the SQL database. To migrate public folder data using this mode, Public Folder Migrator must be installed locally on the SharePoint server computer. To install Public Folder Migrator, use the LabAdmin account to log on to the computer you have configured as the SharePoint server. Run the setup and complete the installation wizard, as follows: 1. On the Welcome screen, click Next. 2. On the License Agreement page, accept the license agreement and click Next. 3. On the User Information page, supply your name and your organization s name. Click the Licenses button and specify a valid product license. Click Next. 4. On the Select Features page, either accept the default installation path or click Browse to specify an alternate installation folder, and then click Next. 5. On the Migration Agent Account page, specify the user account under which the migration agent service will run on this computer. Click Next. If you plan to use the LabAdmin account, make sure it meets the requirements specified in the Accounts and Rights section above. 6. On the Ready to Install the Application page, click Next to begin the installation. 7. Click Finish once installation is completed. 11

Quest Public Folder Migrator for SharePoint Case Studies Our case studies begin with the three migration paths: Migrating Public Folder to a List Migrating a Public Folder Tree to a Document Library Migrating a Public Folder Tree to a Site It is assumed that the migration agent on the agent host is scheduled to Run Always (the default value), executing all enabled jobs assigned to this agent. To change the processing schedule, please refer to the Scheduling Migration section below. Migrating Public Folder to List The Migrating Public Folder to a List migration path transfers a single public folder to a list on a SharePoint Web site. When you configure the migration job, the custom list template will be offered to you, based on predefined mapping rules. For example, by default, a public folder containing mail and post items will be migrated to a discussion board. For more details about Quest custom list templates, refer to the Migrating Public Folder to a List section of the Quest Public Folder Migrator for SharePoint User Guide. Permission Considerations If you want permissions on target to be granted automatically using canned mapping rules, considering permissions on source, select the Migrate Permissions option when configuring the migration job. Permissions will be explicitly applied to the target list as described in the Appendix: SharePoint 2007 Mapping Rules. In addition, administrators can set necessary access permissions on the site level. Due to security model differences between Exchange Server and SharePoint Server, some excess permissions may be granted. 12

Quick Start Guide If the Migrate Permissions option is not selected, permissions on the target list are not modified. To examine how permissions are inherited on target after the migration, create a sample user account (for example, Test_User) and grant this account the Read Items right on the Offices public folder. On the Company Web SharePoint site, assign the Contribute permission level (role) to this account. Migration Take the following steps to migrate the content of the Offices public folder to a list on the Company Web site you prepared: 1. In the Quest Site Administrator for SharePoint management console, right-click the Public Folder Migrator node and select Create New Job from the shortcut menu to start the New Public Folder Migration Job Wizard. 2. On the New Public Folder Migration Job step, specify the following: a) In the Job Information area, supply the job's name (Offices to Company Web) and its description. b) In the Source Exchange Server area, accept the name of the default source Exchange server where the Offices folder resides. c) In the Migrate Permissions area, make sure the Migrate permissions check box is cleared to keep the permissions in the target list intact. d) Click Next. 3. On the Source and Target Selection step, specify the following: a) In the Source Public Folders pane (left side), select the Offices folder in the public folder tree. The description of the selected folder and target list type appears below the pane: You have selected the Offices public folder containing contacts. This public folder will be mapped to a contacts list on a SharePoint Web site. b) In the SharePoint Target pane (right side), select the Company Web site, click Create List, and specify a name for the new contacts list (Offices). This list will be created automatically on the target site in accordance with the custom list template. c) Click Next. 13

Quest Public Folder Migrator for SharePoint 4. On the Folder Mapping Preview step, you can view the following: a) In the Source Public Folders pane (left side), review the Offices folder in the source public folder tree displayed. b) In the SharePoint Target pane (right side), review the Offices contact list to be created for the Offices folder on the Company Web site. By default, matching objects are highlighted. c) Click Next. 5. On the Job Options step, specify the following: a) Skip the Email setting migration option. b) Select the Enable Outlook Redirection check box. c) In the Select Computer area, specify the local computer for migration job processing and select the Enable the job checkbox. 6. Click Finish to complete the wizard. 7. In the Quest Site Administrator for SharePoint management console tree, click the Offices to Company Web migration job node and watch the progress indicator (Processed bar) in the right pane. 8. When the job obtains the Migration completed state, run Microsoft Outlook, select the Offices public folder from the public folder tree, and make sure that you are taken to the Offices contact list on the Company Web SharePoint site (it must appear in the right pane). 9. On the SharePoint site, make sure the permissions on the Offices contact list for the Test_User account were inherited from the site (that is, this user was granted the Contribute permission level [role], which allows the user to view, add, update, and delete items). 14

Quick Start Guide Migrating a Public Folder Tree to a Document Library To migrate the content of the Public Documents public folder tree (a folder with several subfolders) to a document library on the Company Web site you prepared, take the steps below. Permission Considerations If you select the Migrate permissions option when configuring the migration job, permissions will be applied as follows: Permissions from the public folder will be applied to the target document library. Permissions from any of the source folder s subfolders will be applied to the corresponding subfolder of the target document library. Any subfolder that contains special items (Calendar, Contacts, etc.) is mapped to corresponding list on the parent site. Permissions for this subfolder will be applied to the target list as described in the Migrating a Public Folder to a List section above. If the Migrate Permissions option is not selected, permissions on the target document library are not modified. To examine how permissions are applied to the document library, you can grant the Test_User account the Read Items permission on the Public Documents source public folder. Migration To migrate the Public Documents folder, take the following steps: 1. In the Quest Site Administrator for SharePoint management console, right-click the Public Folder Migrator node and select Create New Job from the shortcut menu to start the New Public Folder Migration Job Wizard. 2. On the New Public Folder Migration Job step, specify the following: a) In the Job Information area, supply the job's name (Public Documents to Company Web) and an optional description. 15

Quest Public Folder Migrator for SharePoint 16 b) In the Source Exchange Server area, accept the name of the default source Exchange server or click Browse to specify the Exchange Server where the Public Documents folder resides. After you enter and check the Exchange server name in the Select Exchange Server dialog, click OK to close the dialog window. c) In the Migrate Permissions area, select the Migrate permissions check box. d) Click Next. 3. On the Source and Target Selection step, specify the following: a) In the Source Public Folders pane (left side), select the Public Documents folder in the source public folder tree displayed. The description of the selected folder appears below the pane. b) In the SharePoint Target pane (right side), select the Company Web site, click Create Document Library, and specify the name for the new document library (Public Documents). It will be created automatically on the target site. c) Click Next. 4. On the Folder Mapping Preview step, you can view the following: a) In the Source Public Folders pane (left side), view the Public Documents folder in the source public folder tree displayed. b) To prevent the migration of the Obsolete subfolder with outof-date documents, clear the check box next to the Obsolete subfolder. c) In the SharePoint Target pane (right side), view the Public Documents document library to be created for the Public Documents folder on the Company Web site with the Obsolete subfolder excluded. By default, matching objects are highlighted. d) Click Next. 5. On the Job Options step, specify the following: a) Skip the Email setting migration option. b) Select the Enable Outlook Redirection check box. c) In the Select Computer area, select the local computer for migration job processing. Keep the Enable the Job checkbox cleared. 6. Click Finish to complete the wizard. 7. In the Quest Site Administrator for SharePoint management console tree, click the Public Documents to Company Web migration job node. The job properties in the right pane will display the job's Job enabled status as "no" and Processed status as Disabled.

Quick Start Guide 8. Right-click the Public Documents to Company Web migration job node and select All Tasks Enable the shortcut menu to enable the job. 9. When the job obtains the Migration completed state, run Microsoft Outlook, select the Public Documents public folder, and make sure that you are taken to the Public Documents document library on the Company Web SharePoint site (it must appear in the right pane). Check that all subfolders are displayed properly, with the original hierarchy, and make sure the Obsolete folder does not appear in the document library. 10. On the Company Web SharePoint site, make sure the Test_User account was granted the Public Folder Migrator Read Items permission level [role] for the Public Documents document library. This user must have the View Application Pages, the View Items, the View Versions, the Open, and the View Pages rights on the target object. Migrating a Public Folder Tree to a Site In your test Exchange organization, the Departments folder contains the Accounting, Executives, IS, and Sales subfolders. Use the migration path described in this section to migrate the contents of the Departments public folder tree to the Company Web site, keeping the hierarchical folder structure by creating a site for each subfolder of the Departments folder. By default, the Migrate permissions option is not selected, and target sites are created using the parent site s security. If you select the Migrate permissions option, for every site created, permissions from the corresponding source folder will be applied as described in the Appendix: SharePoint 2007 Mapping Rules. With this migration path, you can select to create sites for folders down to the specified level in the hierarchy. Source items located below that level will be migrated to lists and document libraries (depending on the folder type). Permissions for such folders will be applied as described in the previous sections. 17

Quest Public Folder Migrator for SharePoint Migration To migrate the Departments public folder tree to a site, take the following steps: 1. In the Quest Site Administrator for SharePoint management console, right-click the Public Folder Migrator node and select Create New Job to start the New Public Folder Migration Job Wizard. 2. On the New Public Folder Migration Job step, specify the following: a) In the Job Information area, supply the job's name (Departments to Company Web) and an optional description. b) In the Source Exchange Server area, accept the name of the default source Exchange server or click Browse to specify the Exchange server where the Departments public folder resides. After you enter and check the Exchange server name in the Select Exchange Server dialog, click OK to close the dialog window. c) In the Migrate Permissions area, leave the Migrate Permissions check box cleared. d) Click Next. 3. On the Source and Target Selection step, specify the following: a) In the Source Public Folders pane (left side), select the Departments folder in the source public folder tree displayed. b) In the SharePoint Target pane (right side), select the Company Web site, click Create Site, and specify the name for the new site (Departments site) and the Blank site template for the new site, which will be created automatically. c) Click Next. 4. On the Folder Mapping Preview step, you can view and specify the following: a) In the Source Public Folders pane (left side), view the Departments folder containing the Accounting, Executives, IS, and Sales subfolders in the source public folder tree displayed. b) In the SharePoint Target pane (right side), under the Company Web site node, view the Departments site with the root document library to be created for the Departments folder. By default, matching objects are highlighted. c) Click Site Creation Options to configure the creation options for the child sites. 18

Quick Start Guide d) In the dialog that appears, select the Create child sites for subfolders option and set a value of 1 in Number of hierarchy levels to create sites, so that child sites will be created for the Accounting, Executives, IS, and Sales subfolders of the Departments folder. e) Choose the Blank site template to be used for child sites and click OK to close the dialog window. f) Click Next. 5. On the Job Options step, specify the following: a) Skip the Email setting migration option. b) Select the Enable Outlook Redirection check box. c) In the Select Computer area, specify the local computer for migration job processing and select the Enable the job checkbox. 6. Click Finish to complete the wizard. 7. In the Quest Site Administrator for SharePoint management console tree, click the Departments to Company Web migration job node and watch the progress indicator (Processed bar) in the right pane. 8. When the job obtains the Migration completed state, run Microsoft Outlook, select the Departments public folder in the public folder tree, and make sure you are taken to the Departments site (it must appear in the right pane). Check that all subfolders are displayed properly as child sites. Scheduling Migration When creating a migration job, you select the job processor (that is, the computer where the migration agent service runs) to execute the job. Each migration job is assigned a processing migration agent. By default, the agent service on a computer with Public Folder Migrator is scheduled to run always and therefore all enabled migration jobs assigned to this computer are executed immediately. You can modify the agent s schedule, for example, to perform migration during off-peak hours. To modify the agent s schedule, take the following steps: 1. Create a new migration job without enabling it. Select this job in the Quest Site Administrator for SharePoint console tree, and review the job properties in the right pane: Running on names the local computer you have specified. 19

Quest Public Folder Migrator for SharePoint Job enabled is set to no (which means the job's state is Disabled). Schedule is set to Run always. 2. Right-click the Public Folder Migrator node and select the Schedule Migration option from the shortcut menu. The Migration Scheduling Wizard runs. 3. On the Welcome page, click Next. 4. On the Select Job Processor step, select the computer hosting the migration agent. A list of jobs assigned to this computer is displayed for your convenience. Make sure your job is in the list and then click Next. Any changes you make to an agent s schedule will affect the execution of all enabled jobs assigned to the agent. 5. On the Specify Default Job Schedule step, you can either select a predefined schedule from the list or click Customize to specify a schedule of your own. Then click Next. 6. Click Finish to complete the wizard. 7. Right-click migration job node and select All Tasks Enable. 8. Review the job properties and make sure the Schedule status has changed to the one you have specified. 9. At the scheduled time, watch the job's progress indicator (Processed bar) in the right pane. Wait for the job to complete and verify the migration results as described in the sections above. Public Folder Migrator 2.0 provides enhanced job scheduling with the possibility to customize the schedule for a particular job. Unless the job schedule is specified, the job is executed according to the default job schedule. 20

Quick Start Guide Restarting a Migration Job You can restart any migration job you have configured by selecting All Tasks Restart from its shortcut menu. Restarting a migration job causes a re-migration with full resynchronization of the migrated content. When you restart a migration job that has already completed the migration of public folder content, this will effectively duplicate the source data on the target Web site, list, or document library. To resolve the naming conflicts, Public Folder Migrator uses numbers as suffixes for the names of duplicated items. To avoid the content duplication, you may delete the items previously created on target (except for the root site, document library, or list) before you restart the job. If you delete or create a root item, you will have to recreate the migration job. For the restart to take effect immediately, the job must be enabled and the migration agent must be running. To restart a job, take the following steps: 1. Stop the Quest Public Folder Migrator Service Monitor service on the agent host computer as described in the Quest Public Folder Migrator for SharePoint User Guide. 2. Delete the target items you want to be renewed, except the root item (top-level site, document library, or list). 3. In the Quest Site Administrator for SharePoint management console, right-click the desired job and select All Tasks Restart from its shortcut menu. Confirm the action. 4. Start the Quest Public Folder Migrator Service Monitor service. 5. Wait for the job to complete and make sure that all content has been migrated successfully. 21

Quest Public Folder Migrator for SharePoint Summary In this document, we set up a test environment and ran through a number of case studies that demonstrate the main features of Public Folder Migrator for SharePoint. The case studies include creating three different types of migration jobs, scheduling migration, and restarting jobs. 22

Quick Start Guide Appendix: SharePoint 2007 Mapping Rules In SharePoint 2003, source permissions are mapped to the set of SharePoint rights on target objects and groups on the target site as described in detail in the Quest Public Folder Migrator for SharePoint User Guide. Permissions are applied differently in SharePoint 2007 (Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0) to provide a more flexible and scalable security model. In SharePoint 2007, permission mapping is based on a number of permission levels; each permission level emulates the defined security right of the user or group on the source Exchange server and includes the set of predefined rights on the SharePoint target. Public Folder Migrator assigns the particular permission level to the user or group, according to the original permissions of the source Exchange server. As a result, each user or group instantly obtains the set of rights on the SharePoint target. The Migrate permissions option of a migration job controls how permissions on the source public folders are mapped to site and list permissions on the SharePoint target: If the Migrate permissions option is not selected, then permissions for any new target item (list, document library, or site) are inherited from its parent site. Permissions on existing list items stay intact. If the Migrate permissions option is selected, then: After a public folder is migrated to a list or a document library, the permission level on SharePoint target items is set for the user account in accordance with canned mapping rules as described in the table below: 23

Quest Public Folder Migrator for SharePoint PERMISSION ON SOURCE PERMISSION LEVEL ON TARGET PERMISSION LEVEL DESCRIPTION RIGHTS INCLUDED Create items Public Folder Migrator Create Items User can create items. Use this permission level to emulate the Create Items right on Exchange public folders. View Application Pages View Items Add Items View Pages Open Use Remote Interfaces Use Client Integration Features Folder owner Public Folder Migrator Owner User can manage content and security. Use this permission level to emulate the Owner right on Exchange public folders. View Application Pages View Items Delete Items Open Items View Versions Delete Versions View Pages Manage Lists Manage Permissions Manage Personal Views Create Groups Browse Directories Enumerate Permissions Browse User Information Open Edit Personal User Information Use Remote Interfaces Use Client Integration Features Create Alerts Create subfolders Public Folder Migrator Create Subfolders User can create subfolders. Use this permission level to emulate the Create subfolders right on Exchange public folders. View Application Pages View Items Add Items View Pages Open 24

Quick Start Guide PERMISSION ON SOURCE PERMISSION LEVEL ON TARGET PERMISSION LEVEL DESCRIPTION RIGHTS INCLUDED Edit items All Public Folder Migrator Edit All Items User can edit any item. Use this permission level to emulate the Edit All Items right on Exchange public folders. View Application Pages View Items Manage Lists Edit Items Open View Pages Manage Personal Views Use Remote Interfaces Use Client Integration Features Update Personal Web Parts Edit items Own Public Folder Migrator Edit Own Items User can edit own items. Use this permission level to emulate the Edit Own Items right on Exchange public folders. View Application Pages View Items Edit Items View Pages Open Manage Personal Views Use Remote Interfaces Use Client Integration Features Update Personal Web Parts Delete items All Public Folder Migrator Delete All Items User can delete any item. Use this permission level to emulate the Delete All Items right on Exchange public folders. View Application Pages View Items Delete Items View Versions Delete Versions Manage Lists View Pages Open Manage Personal Views Use remote Interfaces Use Client Integration Features 25

Quest Public Folder Migrator for SharePoint PERMISSION ON SOURCE PERMISSION LEVEL ON TARGET PERMISSION LEVEL DESCRIPTION RIGHTS INCLUDED Delete items Own Public Folder Migrator Delete Own Items User can delete own items. Use this permission level to emulate the Delete Own Items right on Exchange public folders. View Application Pages View Items Delete Items View Versions Delete Versions View Pages Open Manage Personal Views Use remote Interfaces Use Client Integration Features Read items Public Folder Migrator Read Items User can read items. Use this permission level to emulate the Read Items right on Exchange public folders. View Application Pages View Items View Versions Open View Pages 26