Copyright Quest Software, Inc All rights reserved. DISCLAIMER TRADEMARKS

Transcription

1 4.0 User Guide

2 Copyright Quest Software, Inc All rights reserved. This guide contains proprietary information, which is protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser's personal use without the written permission of Quest Software, Inc. 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 Exchange Migration Wizard 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 info@quest.com Please refer to our Web site for regional and international office information. Quest Exchange Migration Wizard Updated February 19, 2007 Software version 4.0

3 Contents ABOUT THIS GUIDE... 7 OVERVIEW... 8 CONVENTIONS... 8 ABOUT QUEST SOFTWARE, INC... 9 CONTACTING QUEST SOFTWARE... 9 CONTACTING QUEST SUPPORT... 9 CHAPTER 1 INTRODUCTION MIGRATION PROCESS OVERVIEW...13 EXCHANGE MIGRATION WIZARD PROJECT MANAGER...14 PREREQUISITES...15 CHAPTER 2 DOMAIN AND EXCHANGE MIGRATION DOMAIN FIRST...18 EXCHANGE FIRST...19 PARALLEL MIGRATION...20 CHAPTER 3 REQUIRED PERMISSIONS CHAPTER 4 REGISTER EXCHANGE ORGANIZATIONS REFRESHING ORGANIZATION INFORMATION...24 EXCHANGE EXCHANGE 200X...25 REMOVING A SERVER FROM THE DATABASE...28 CHAPTER 5 DIRECTORY SYNCHRONIZATION SYNCHRONIZATION PROCESS...30 SYNCHRONIZING DIRECTORY OBJECTS...31 CREATING EXCHANGE 200X MAILBOXES...31 SETTING MAIL REDIRECTION...32 SYNCHRONIZING MAILBOX PERMISSIONS...33 FIRST DIRECTORY SYNCHRONIZATION SESSION...34 SETTING UP A DIRECTORY SYNCHRONIZATION JOB...34 STEP 1. DIRECTORY SYNCHRONIZATION AGENT...35 STEP 2. SELECT EXCHANGE 5.5 SERVER...35 STEP 3. SELECT ACTIVE DIRECTORY SERVER...36 STEP 4. SELECT EXCHANGE 200X SERVER...36 STEP 5. SELECT MAIL REDIRECTION TYPE...37 i

4 STEP 6. GENERAL SYNCHRONIZATION OPTIONS...37 STEP 7. EXCHANGE 5.5 TO ACTIVE DIRECTORY SYNCHRONIZATION...38 STEP 8. CREATE OPTIONS...39 STEP 9. SELECT DIRECTORY SYNCHRONIZATION MEMBERS...40 STEP 10. ACTIVE DIRECTORY TO EXCHANGE 5.5 SYNCHRONIZATION...42 STEP 11. CONFLICT RESOLUTION...42 STEP 12. OBJECT MATCHING...43 STEP 13. COMPLETING THE WIZARD...45 DIRECTORY SYNCHRONIZATION SETTINGS...46 DIRECTORY SYNCHRONIZATION JOB SETTINGS...46 DIRECTORY SYNCHRONIZATION AGENT S SETTINGS...50 DIRECTORY SYNCHRONIZATION AGENT PERFORMANCE COUNTERS...53 OBJECT ATTRIBUTES USED FOR DIRECTORY SYNCHRONIZATION...54 AUXILIARY INFORMATION...55 INDIVIDUAL OBJECT SYNCHRONIZATION OPTIONS...56 TARGET OBJECT S GUID...57 ROLLING MIGRATION ATTRIBUTE...58 SKIP ATTRIBUTES AUXILIARY INFORMATION ATTRIBUTE...58 CONSIDERATIONS FOR USING CUSTOM ATTRIBUTES...59 HOW TO IMPROVE DIRECTORY SYNCHRONIZATION PERFORMANCE...60 CHAPTER 6 PUBLIC FOLDER SYNCHRONIZATION SYNCHRONIZATION PROCESS...63 PUBLIC FOLDER COLLECTIONS...64 PUBLIC FOLDER SOURCE AGENT...64 TRANSMISSION AGENT...65 PUBLIC FOLDER TARGET AGENT...65 SYNCHRONIZATION OF DELETED PUBLIC FOLDERS...65 SETTING UP A NEW PUBLIC FOLDER SYNCHRONIZATION JOB...66 STEP 1. SELECT EXCHANGE SERVERS...67 STEP 2. SELECT PUBLIC FOLDERS...68 STEP 3. SPECIFY AGENT INSTALLATION PATH...70 STEP 4. COMPLETING THE WIZARD...70 STEP 5. COMMIT CHANGES...70 PUBLIC FOLDER SYNCHRONIZATION SETTINGS...70 ADD PUBLIC FOLDER COLLECTION...71 PUBLIC FOLDER SYNCHRONIZATION AGENTS SETTINGS...74 STARTING PUBLIC FOLDER SYNCHRONIZATION...78 STOPPING PUBLIC FOLDER SYNCHRONIZATION...78 ii

5 CHAPTER 7 MAILBOX SYNCHRONIZATION SYNCHRONIZATION PROCESS...80 MAILBOX COLLECTIONS...81 MAIL SOURCE AGENT...82 TRANSMISSION AGENT...83 MAIL TARGET AGENT...83 SETTING UP A NEW MAILBOX SYNCHRONIZATION JOB...84 STEP 1. SELECT EXCHANGE SERVERS...85 STEP 2. SELECT MAILBOX STORE...85 STEP 3. CREATE COLLECTIONS...86 STEP 4. POPULATE COLLECTIONS...87 STEP 5. SPECIFY AGENT INSTALLATION PATH...87 STEP 6. COMPLETE THE WIZARD...88 STEP 7. COMMIT CHANGES...88 MAILBOX SYNCHRONIZATION SETTINGS...88 ADD MAILBOX COLLECTION...88 POPULATE MAILBOX COLLECTION...91 MAILBOX COLLECTION SETTINGS...96 MAILBOX SYNCHRONIZATION AGENTS SETTINGS...97 STARTING MAILBOX SYNCHRONIZATION CHECKING MAILBOX SYNCHRONIZATION STATUS RUNNING COLLECTION ANALYZING UTILITY FROM PROJECT MANAGER RUNNING COLLECTION ANALYZING UTILITY FROM THE COMMAND LINE LIST OF ERROR CODES MAILBOX SWITCH MANUAL MAILBOX SWITCH UNDO MAILBOX SWITCH CLIENT PROFILE UPDATE CHAPTER 8 CALENDAR AND FREE/BUSY SYNCHRONIZATION PERSONAL CALENDARS SYNCHRONIZATION FREE/BUSY INFORMATION SYNCHRONIZATION SETTING UP A NEW CALENDAR SYNCHRONIZATION JOB STEP 1. SELECT EXCHANGE SERVERS STEP 2. CALENDAR SYNCHRONIZATION MEMBERS STEP 3. SELECT MAILBOXES FOR CALENDAR SYNCHRONIZATION. 116 STEP 4. SYNCHRONIZATION OPTIONS STEP 5. SPECIFY AGENT INSTALLATION PATH STEP 6. COMPLETE THE WIZARD AND COMMIT CHANGES iii

6 CALENDAR SYNCHRONIZATION SETTINGS CALENDAR SYNCHRONIZATION MEMBERS CALENDAR SYNCHRONIZATION JOB SETTINGS CALENDAR SYNCHRONIZATION AGENT SETTINGS STARTING CALENDAR SYNCHRONIZATION CHAPTER 9 PRE-INSTALLING THE AGENTS CREATING AN INSTALLATION PACKAGE INSTALLING AGENT FILES ON A NON-CLUSTER SERVER INSTALLING AGENT FILES ON CLUSTERS PREPARE CLUSTER SERVERS FOR AGENT FILES INSTALLATION INSTALL THE AGENT FILES ON CLUSTER SERVERS INSTALLING THE AGENTS CHAPTER 10 CUSTOMIZING EXCHANGE MIGRATION WIZARD PROJECT MANAGER SCRIPTING ORGANIZING SCRIPTS ADDING NEW SCRIPTS RUNNING SCRIPTS EXCHANGE MIGRATION WIZARD AGENTS ADD-INS REGISTERING ADD-INS INSTALL ADD-INS WIZARD DIRECTORY SYNCHRONIZATION ADD-INS MAILBOX SYNCHRONIZATION ADD-INS CHAPTER 11 GENERAL AND SERVER OPTIONS OPTIONS DIALOG BOX DIRECTORY SYNCHRONIZATION SETTINGS LICENSE SERVER ADD-INS SWITCH NOTIFICATIONS SECURITY ADVANCED AGENTS MANAGEMENT ADDITIONAL PARAMETERS FOR AGENT S CONFIGURATION FILES COLLECTION ANALYZING UTILITY STATISTICS COLLECTION AGENT SETTINGS SERVER OPTIONS CONNECTION ASSOCIATED DOMAIN CONTROLLER RESOURCE USAGE ASSOCIATED SERVERS iv

7 CHAPTER 12 GETTING STATISTICS, LOGGING INFORMATION, AND REPORTS LOGGING, STATISTICS, AND NOTIFICATIONS AGENT LOGS ONLINE STATISTICS MAIL NOTIFICATIONS AGENTS LOGGING OPTIONS EXCHANGE MIGRATION WIZARD REPORTS STATISTICS COLLECTION AGENT QUEST REPORTING CONSOLE PREDEFINED REPORTS CHAPTER 13 POST-MIGRATION ACTIVITIES STOP THE MAILBOX AND CALENDAR SYNCHRONIZATION JOBS FOR MIGRATED SERVERS DECOMMISSION MIGRATED SERVERS STOP THE PUBLIC FOLDER SYNCHRONIZATION JOBS FOR MIGRATED FOLDERS STOP THE DIRECTORY SYNCHRONIZATION JOBS FOR MIGRATED SITES 162 COLLAPSE THE SOURCE EXCHANGE 5.5 ORGANIZATIONS CLEAN UP THE TARGET OBJECTS ATTRIBUTES DELETE THE AUXILIARY REDIRECTION CONTACTS CHAPTER 14 RECOMMENDATIONS ON TROUBLESHOOTING BEFORE YOU CALL SUPPORT INFORMATION REQUIRED FOR SUPPORT APPENDIX A v

8 vi

9 About This Guide Overview Conventions About Quest Infrastructure Management About Quest Software Contacting Quest Software Contacting Customer Support 7

10 Quest Exchange Migration Wizard Overview This document has been prepared to assist you in becoming familiar with Exchange Migration Wizard. The User Guide contains the information required to use Exchange Migration Wizard. It is intended for network administrators, consultants, analysts, and any other IT professionals using the product. Conventions In order to help you get the most out of this guide, we have used specific formatting conventions. These conventions apply to procedures, icons, keystrokes and cross-references. ELEMENT CONVENTION Select Bolded text Italic text Bold Italic text This word refers to actions such as choosing or highlighting various interface elements, such as files and radio buttons. Interface elements that appear in Quest products, such as menus and commands. Used for comments. Introduces a series of procedures. Blue text Indicates a cross-reference. When viewed in Adobe Acrobat, this format can be used as a hyperlink. Used to highlight additional information pertinent to the process being described. Used to provide Best Practice information. A best practice details the recommended course of action for the best result. Used to highlight processes that should be performed with care. + A plus sign between two keystrokes means that you must press them at the same time. A pipe sign between elements means that you must select the elements in that particular sequence. 8

11 About This Guide 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 Contacting Quest Software Mail: Web site: info@quest.com Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA USA 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 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: Support Guide.pdf 9

12

13 1 Introduction Migration Process Overview Exchange Migration Wizard Project Manager Prerequisites 11

14 Quest Exchange Migration Wizard The multiple advantages and superior capabilities of Microsoft Exchange 2000/2003/2007 Server have persuaded many companies to seriously consider upgrading their Exchange 5.5 systems to the new platform. The migration, however, brings many challenges: The migration should not interrupt a mail system s normal functioning. No data (including public folder content, mailbox messages and their attachments) should be lost. In most cases the Exchange directory structure needs to be reorganized. Quest Exchange Migration Wizard is a complete solution for Exchange 5.5 to Exchange 2000/2003/2007 migration and coexistence that addresses each of these issues. Terminology Used Throughout this document, the following terms are used: Source servers: The Exchange 5.5 servers from which the messaging system is migrated Target servers: The servers to which the system is migrated Console: The computer on which Exchange Migration Wizard is installed In the remainder of this document: Exchange 2003 will denote Exchange 2000 and Exchange 2003 organizations, servers, mailboxes, etc. Exchange 200x will denote Exchange 2000, Exchange 2003, and Exchange 2007 organizations, servers, mailboxes, etc. 12

15 Introduction Migration Process Overview Exchange 5.5 Exchange 2000/2003/2007 Exchange Directory Synchronization Exchange 5.5 Directory Active Directory Public Folders Synchronization Exchange 5.5 Folders Exchange 2000/2003/2007 Folders Mailbox Migration Exchange 5.5 Mailboxes Exchange 2000/2003/2007 Mailboxes Exchange 5.5 Exchange 2000/2003/2007 Calendar Synchronization Calendars Free/Busy Information Calendars Free/Busy Information The Exchange migration process includes the following migration tasks: TDirectory SynchronizationT Exchange 5.5 Directory objects and their properties are synchronized with the target Active Directory. TPublic Folder SynchronizationT Exact replicas of Public Folders are created and maintained on the target Exchange servers. TMailbox SynchronizationT User mailboxes are located on the target servers and all mailbox content is gradually transferred there. Once a user s new Exchange 200x mailbox is an exact replica of the source mailbox, the user can be switched to the target server. TCalendar SynchronizationT Exchange Migration Wizard synchronizes the personal Calendar folders of the migrated mailboxes, including scheduled meetings and appointments. The calendar entries are copied to the user s new Exchange 200x mailbox and the Free/Busy information for the copied meetings and appointments is updated. The tasks are accomplished in parallel and have separate, flexible settings. 13

16 Quest Exchange Migration Wizard Exchange Migration Wizard Project Manager Project Manager is a centralized migration project management application that provides full control over the Exchange migration going on your network. For your convenience, Project Manager organizes all the migration information in an Explorer-like interface. Project Manager displays a Management Tree for Exchange organizations and servers, involved in the migration, and the synchronization jobs in the left pane. The information and statistics on specific objects is displayed in the right pane. The main Project Manager window is shown in the following figure. 14

17 Introduction Prerequisites Before you start the Exchange migration, please make sure that the following requirements are satisfied: Exchange Migration Wizard does not migrate any Exchange configuration information, such as protocols, connectors, or recipient containers. The target organization must be already set up and configured before you start migrating objects. Please refer to the Microsoft Exchange 2000/2003/2007 Server documentation. The administrative accounts for Exchange Migration Wizard agents are configured and granted all the required permissions. Source and target Exchange organizations are prepared for migration as described in the Exchange Migration Wizard - Quick Start Guide. The product is installed and configured, as described in the Exchange Migration Wizard - Quick Start Guide. 15

18

19 2 Domain and Exchange Migration Domain First Exchange First Parallel Migration 17

20 Quest Exchange Migration Wizard Exchange migration is usually planned together with moving to Windows 2000/2003 and Active Directory. This section covers possible migration sequences and provides recommendations on each of them. We also recommend you get familiar with the Exchange Migration Wizard - Best Practices document. This document contains recommendations, best practices and other materials that might be useful for migration planning and implementation. Domain First It is recommended that user accounts corresponding to the Exchange 5.5 mailboxes that will be migrated be moved to the target Windows 2000/2003 domain before you start the Exchange migration. You can use Quest Domain Migration Wizard to move user accounts to the Active Directory domain where you are going to deploy your Exchange 200x servers. Exchange Migration Wizard will automatically locate Active Directory users to whom mailboxes should be assigned in the following cases: If the Active Directory user account is indicated as the primary Windows NT account for the Exchange 5.5 mailbox. In this case you should run Exchange Processing Wizard (a companion application to Domain Migration Wizard) after the accounts are moved to the new location. The wizard allows you to update your Microsoft Exchange 5.5 mailbox owners to reflect the domain migration changes. If the Security Identifier (SID) of the primary Windows NT account for the Exchange 5.5 mailbox is found in the SIDHistory attribute of the Active Directory user account. In this case you should use Domain Migration Wizard to add SIDHistory to the Active Directory objects. For more information, please refer to the Domain Migration Wizard documentation. 18

21 Domain and Exchange Migration Exchange First You can perform the Exchange migration before moving user accounts to the target Active Directory domains. In this scenario, you should use Exchange Migration Wizard to create Active Directory user objects corresponding to the source Exchange 5.5 mailboxes. Please see the Directory Synchronization section of this document for more details on how Exchange Migration Wizard synchronizes the directories. However, Exchange Migration Wizard does not take care of NT account properties, such as logon name and account password. You should run Domain Migration Wizard after the Exchange migration is complete to synchronize NT user account properties and permissions with the Active Directory users created by the wizard. You will have to migrate the user accounts after the Exchange migration is completed. In this scenario, you should configure the wizard to create disabled Active Directory accounts and make the primary Windows NT account of the source mailbox be the Associated External Account of the target user. Users will then be able to access all the Exchange 200x resources using their Windows NT 4.0 accounts. For more information on how to enable the Active Directory accounts, please see the article XADM: How to Enable Disabled Accounts That the ADC Creates at Note that all the Exchange 200x Access Control Lists (ACLs) will refer to the Windows NT 4.0 account s SID. When you later perform the directory migration, be sure to migrate users with SIDHistory. The Exchange 200x security will rely on SIDHistory until you process all the client permissions and modify all ACLs to refer to the new Active Directory accounts. Exchange Migration Wizard allows you to export the results of the directory synchronization to the map files that will be used as the source of account mapping information for Domain Migration Wizard. To export the results of the directory synchronization, right-click the Directory Synchronization node in the Management Tree and start the Export Account Mapping Wizard using the corresponding shortcut menu command. 19

22 Quest Exchange Migration Wizard In the wizard, you should specify the source Exchange 5.5 organization and the target Active Directory domain. The wizard will do the following: 1. Enumerate the mailboxes of the specified Exchange organization. 2. For each mailbox, the wizard will find its owner and get the GUID of the corresponding Active Directory user. 3. Search the target domain for the users with the retrieved GUIDs. The server you specify will be used as the source of the Active Directory information. 4. For each target domain user found, the wizard will save the account mapping information in the exported file. Note that the wizard will create a separate map file for each source domain whose users are the owners of the source mailboxes. If you have several source Exchange 5.5 organizations or several target Active Directory domains for the migration, you should run the Export Account Mapping Wizard for each source organization-target domain pair. Parallel Migration If the migrations are performed in parallel, Exchange Migration Wizard can pick up the users created by Domain Migration Wizard during the directory synchronization process. However, this will impact the Exchange migration, because the users switched to the target will not have full collaboration capabilities. For example, their Global Address List will not be full, since not all Active Directory user accounts are created and mailbox-enabled by the moment when the first user starts using his or her Exchange 200x mailbox. 20

23 3 Required Permissions 21

24 Quest Exchange Migration Wizard The Exchange Migration Wizard agents work with different servers on the network: they create and modify Exchange 5.5 and Active Directory objects, and work with mailboxes and public folders. To do all these tasks, the agents must have the appropriate permissions. Exchange Migration Wizard allows you to use different administrative accounts for different purposes. For example, the Source Exchange account is used for working with the Exchange 5.5 directory, and the Target Exchange account is used to access the Exchange 200x mailboxes and public folders. Please, refer to the Exchange Migration Wizard - Quick Start Guide to find out which accounts are used by which agents, where you can set these accounts, and what privileges each account should have. 22

25 4 Register Exchange Organizations Refreshing Organization Information Removing a Server from the Database 23

26 Quest Exchange Migration Wizard Exchange Migration Wizard lets you completely reorganize your messaging system by simultaneously migrating multiple Exchange organizations and multiple Exchange servers within the same organization. In order to use this capability, before you start an Exchange migration, you should register all the affected Exchange organizations in Exchange Migration Wizard. The source and target Exchange organizations are registered from the shortcut menus of the Source Organizations and Target Organizations nodes of the Management Tree. The commands start graphical wizards that guide you through the registration process. The wizards will prompt you for the accounts to be used with the servers. The accounts you specify should have the privileges specified in the Exchange Migration Wizard - Quick Start Guide. The account you specify in the Add Source Organization Wizard and Add Target Organization Wizard is used by default with all the servers of the registered Exchange organization. Later you can modify the connection settings for each of the registered Exchange servers. To modify the settings for the server, right-click the server in the Management Tree and click Properties on the shortcut menu. It is recommended that when adding the target organization you select the Add Exchange topology only option. This makes the enumeration significantly faster. You can later add administrative mailboxes (for example, for public folder synchronization) using the Add Recipients to EMW Database option explained below. Refreshing Organization Information After you register the source or target organization, Project Manager enumerates the servers, containers, and recipient objects of the organization. Information about all Exchange objects of the registered organizations is stored in the Exchange Migration Wizard database. This information is not updated automatically; you have to refresh it when directory changes occur. Exchange 5.5 To refresh the entire Exchange 5.5 organization, right-click the <Organization name>, the <Source server name> or the Global Address List node in the navigation pane and select Refresh from the shortcut menu. During a refresh, only the changes since the previous refresh (or original enumeration) are retrieved from the directory. This is why a refresh is significantly faster than the initial enumeration. 24

27 Register Exchange Organizations For full refresh from scratch, add the organization again, a second time. By default, the organization is refreshed via the server that was used when adding the organization. This server is bolded in the list. If you want to use another server for refresh, right-click the server and select the Default Server for Refresh option. If you want to see only the most recent mailbox switch status, you do not have to refresh all the directory information. Right-click click the <Organization name>, the <Source server name> or the Global Address List node in the navigation pane and select Refresh Switch Status Only from the shortcut menu. Mailbox switch is discussed in more detail in the Mailbox Synchronization section of this document. You can also add new recipients to the Exchange Migration Wizard configuration database individually. To add new recipients to the database, complete the following steps: 1. In the Management Tree, right-click the server or container holding the recipients to be added and click Add Recipients to EMW Database on the shortcut menu. 2. In the Add Recipients to EMW Configuration Database dialog box, select the objects from the Available recipients list and click Add to update the Exchange Migration Wizard database. Exchange 200x You can refresh any Exchange 200x server s information by right-clicking the server in the Management Tree and clicking Refresh. The recipients deleted from the target Exchange organization are not removed from the Exchange Migration Wizard configuration database during refresh. These recipients should be removed from the database manually. For more details on how to remove the objects from the database, refer to the Removing Recipients from the Database section below. The information that is refreshed depends on the associated settings of the associated domain controller for the selected Exchange server. To verify and change these settings, right-click the Exchange server in the Management Tree, select Properties from the shortcut menu and open the General page and go to the Associated domain controller tab. 25

28 Quest Exchange Migration Wizard Select the Add Exchange topology only option if you want to refresh only information about the target Exchange organization topology, including administrative groups, storage groups, stores, and servers. Deselect the Add Exchange topology only option and select the Use Global Catalog for enumeration option if you want to make full refresh including the Exchange topology and mailboxes. Note that full refresh is a timeconsuming operation, especially in large organizations, so it is recommended to use a quick refresh when you need to update only the Exchange topology information. Adding New Recipients to the Database It is also possible to add new recipients to the Exchange Migration Wizard configuration database manually, bypassing the refresh operation. To do this, right-click a server or a container that holds the recipients you want to add and click Add Recipients to EMW Database on the shortcut menu. The Add recipients to EMW Configuration Database dialog appears. In this dialog, click Browse and browse for the domain and organizational unit from which the recipients will be retrieved. The selected context then is displayed in the in the Container text box. Then click Find Now to enumerate recipients in the selected context. 26

29 Register Exchange Organizations Select objects from the Available recipients list, click >> to add the recipients to the Selected recipients list, and then click Add to update the Exchange Migration Wizard database. Since a full refresh may take a long time, especially in large organizations, it is recommended that add new recipients manually when you do not need to update the Exchange topology. Removing Recipients from the Database You also can remove administrative groups, storage groups, stores, and recipients from the database. To remove the object, complete the following steps: 1. In the Management Tree, browse for the parent object containing the object you want to remove. 2. In the right-hand pane, right-click the object you want to remove and select Remove. Note that objects can be removed only if all their child objects are removed and if they are not specified in any synchronization job. That is, for example, you cannot remove a mailbox store from the database if not all mailboxes are removed from the store. You also cannot remove a mailbox from the store if it is specified as the administrative mailbox in any public folder or calendar synchronization job. 27

30 Quest Exchange Migration Wizard Removing a Server from the Database During the migration, the source Exchange 5.5 servers can be decommissioned as soon as all their recipients are migrated to the target servers. To reflect these changes in Project Manager, you can remove the information about the decommissioned server from the Exchange Migration Wizard database. To do this, right-click the server and click Remove Server From Database on the shortcut menu. Project Manager does not check whether the server you are removing from the database was really removed from the organization. If you remove a server from the database, you have to add the organization again to reregister the server in Project Manager. A simple refresh will not suffice because a refresh just adds objects recently added or modified. Note that removing the last server in the site will remove the site from Exchange Migration Wizard database. If you remove the only server in the organization, the entire organization will be removed from the database. 28

31 5 Directory Synchronization Synchronization Process Setting Up a Directory Synchronization Job Directory Synchronization Settings Directory Synchronization Agent Performance Counters Object Attributes Used for Directory Synchronization How to Improve Directory Synchronization Performance 29

32 Quest Exchange Migration Wizard Exchange Migration Wizard migrates all Exchange 5.5 directory objects and their properties to the target Active Directory. Then the directories are continuously synchronized until the migration is finished. Exchange 5.5 Site AD Domain Mailboxes Distribution Lists Directory Synchronization Job Users Groups Custom Recepients Contacts Synchronization Process Directory synchronization is performed as a separate directory synchronization job for each source site target domain pair. Each job is configured individually, allowing administrators to define which objects will participate in the job, and to select the synchronization direction and other options. The directory synchronization jobs are performed by the Directory Synchronization Agents (DSA). An agent installed on any computer on the network can perform multiple directory synchronization jobs. A Directory Synchronization Agent performs the jobs sequentially during the allowed hours you specify. After you configure and start the synchronization job, the agent will: Search for and synchronize Exchange 5.5 directory and Active Directory objects Create Exchange 200x mailboxes if necessary Set mail redirection for each mailbox to be migrated Synchronize Exchange 5.5 and Exchange 200x mailboxes permissions (optional) Each of these steps is described below in more detail. Also, see the Exchange Migration Wizard - Overview document for further information on this process. 30

33 Directory Synchronization Synchronizing Directory Objects The DSA synchronizes directory objects by searching for matching objects in the Exchange 5.5 directory and Active Directory. If a pair of matching objects is found, Exchange Migration Wizard will synchronize the objects and their properties. If there is no matching object in one of the directories, the wizard can create it. After the Directory Synchronization Agent has found or created the corresponding target object, it will write its globally unique identifier (GUID) to the source object s custom attribute, which you can specify. From this moment on, the pair of corresponding objects will be found by the target object s GUID. Once the matching is established, you can modify the target object and it will be still recognized as corresponding to the source object. The agent uses the update sequence numbers (USNs) to identify objects that were changed since the last synchronization session. At the end of each session, the Highest Committed USN value is saved and the Directory Synchronization Agent does not process objects with lower USNs during the next session. To increase the agent s performance and efficiency, the agent stores a matching cache in its working directory. When the agent finds a modified object, it first checks whether the object is present in the matching cache. This allows the agent to determine the corresponding objects without querying both directories. Exchange Migration Wizard matches objects using the default matching rules. Fore more information about the default matching rules, please refer to the Exchange Migration Wizard - Directory Object Matching document. The default object matching rules can be changed with custom add-ins. For more information on how they can be modified, please see the Customizing Exchange Migration Wizard section of the document. Creating Exchange 200x Mailboxes After the Directory Synchronization Agent has found the corresponding Active Directory user for the source Exchange 5.5 mailbox, it searches for the Exchange 200x mailbox of the user. If the user has an assigned Exchange 200x mailbox, the existing mailbox will be used for mail migration; a new mailbox will not be created. If the user is not mailbox-enabled, the Directory Synchronization Agent will create a new Exchange 200x mailbox for the user. Mailboxes are created in the mailbox store you specify when setting up a new directory synchronization job. 31

34 Quest Exchange Migration Wizard Considerations for Resource Mailboxes Resource mailboxes are mailboxes that represent company resources you can book (such as conference rooms and equipment). In Exchange versions previous to Exchange 2007 all mailboxes were of the same type regardless of their usage requirements. In other words, there was no difference between a user mailbox and a resource mailbox from the technical point of view or user experience. Exchange 2007 introduces new mailbox types for resource mailboxes: Room mailbox and Equipment mailbox. By default, all the mailboxes created by the Directory Synchronization Agent in Exchange 2007 are the user type mailboxes. The Directory Synchronization Agent does not automatically convert user mailboxes that were used as resource mailboxes to the new mailbox types. To convert a user mailbox to the room mailbox, run the following command in the Exchange Management Shell: Set-Mailbox -Identity <MailboxIdParameter> -Type Room To convert user mailbox to the equipment mailbox, run the following command from Exchange Management Shell: Set-Mailbox -Identity <MailboxIdParameter> -Type Equipment This procedure must be performed only after the migration is completed, the mailboxes are switched and the users logon to the target mailboxes. The Calendar Synchronization Agent is responsible for the correct functioning of the resource mailboxes, and the administrator should not interfere with this process. Setting Mail Redirection Auxiliary custom recipients are created to set up automatic mail forwarding from the new Exchange 200x mailboxes to the old Exchange 5.5 mailboxes. Thus, no matter which mailbox mail is sent to, it arrives at the mailbox the user is currently using. 32

35 Directory Synchronization Source User1 (MB) X400 connector Target User1 is mailbox-enabled User1 (CR) - hidden from GAL User1 (Contact) - hidden from GAL Exchange Migration Wizard supports X.400 protocol and Simple Mail Transfer Protocol (SMTP) for mail redirection. The Mail Redirection and Message Replies section of the Exchange Migration Wizard - Overview document describes how redirection is handled and why one might choose each of these protocols. Synchronizing Mailbox Permissions The Directory Synchronization Agent can optionally synchronize the Exchange 5.5 and Exchange 200x objects permissions. The directory permissions are different in Exchange 5.5 and Exchange 200x. The table below shows which permissions in Exchange 5.5 are synchronized to which permissions in Exchange 200x. EXCHANGE 5.5 PERMISSIONS ACTIVE DIRECTORY AND EXCHANGE 200X PERMISSIONS Mailboxes and Users Send As Mailbox Owner Modify Permissions Send As Full Mailbox Access Read Permission Change Permissions Distribution Lists and Groups; Custom Recipients and Contacts Send As Modify Permissions Send As Modify Permissions 33

36 Quest Exchange Migration Wizard The current Exchange Migration Wizard version does not modify any other permissions. The inherited permissions on objects are not synchronized by the wizard. The Directory Synchronization Agent does not require trusts to copy permissions granted to the users from domains other than the domain in which the source Exchange 5.5 server resides. However, you will need to set up trusts between a user s domain and the target Exchange 200x domain for the user to access the corresponding target object. First Directory Synchronization Session The first directory synchronization session is the most important in the directory synchronization process because it performs all of the above tasks on all Exchange directory data. After the first synchronization session is finished, only changes are synchronized. That is why the initial synchronization may take a relatively long time. Please see the How to Increase Directory Synchronization Performance section of this document for recommendations on how to make it faster. However, all of the subsequent synchronization sessions are much faster because the Directory Synchronization Agent does not have to enumerate and synchronize all the directory objects. It is important that the Directory Synchronization Agent finish the first session for each of the jobs before you start calendar synchronization, public folder synchronization, or mailbox migration. Setting Up a Directory Synchronization Job To create a new directory synchronization job, right-click the Directory Synchronization node of the Management Tree and click Add Directory Synchronization Job on the shortcut menu. This will start the Add Directory Synchronization Job Wizard that will help you to install the Directory Synchronization Agent and configure the job. If you want an agent that has already been installed to perform another directory synchronization job, right-click the agent s installation server under the Directory Synchronization node of the Management Tree and click Add Directory Synchronization Job on the shortcut menu. The same wizard will be started, but the first step will be skipped. This section guides you through each step of the wizard and explains the available directory synchronization options. 34

37 Step 1. Directory Synchronization Agent Directory Synchronization The wizard prompts you for the server on which the Directory Synchronization Agent should be installed. Type or browse for the server name on the network. The Directory Synchronization Agent can be installed on any computer on the network that runs Windows 2000/2003 Server. Specify the agent s installation path and the account for the agent s service. Make sure that the account you specify meets the requirements listed in the Exchange Migration Wizard - Quick Start Guide. Step 2. Select Exchange 5.5 Server Select one of the source servers registered in Exchange Migration Wizard. The server will be used as the source of the Exchange 5.5 directory information. The LDAP port and the administrative account will be automatically obtained from the server s properties. 35

38 Quest Exchange Migration Wizard Step 3. Select Active Directory Server Specify the Active Directory domain controller that will be used to obtain Active Directory information for the job. You can type the name of the domain controller, or select one of the domain controllers retrieved when Exchange 200x servers were registered in Exchange Migration Wizard. If the target domain controller is already registered in Exchange Migration Wizard as an Exchange 200x server, the LDAP port and the administrative account will be automatically obtained from the server s properties. Step 4. Select Exchange 200x Server The Directory Synchronization Agent creates Exchange 200x mailboxes for the non-mailbox-enabled Active Directory user accounts. Select the server and the mailbox store where the mailboxes should be created. 36

39 Step 5. Select Mail Redirection Type Directory Synchronization During the transition period, all the users should receive all mail sent to either the source or target mailbox, regardless of whether the user is already migrated. For each user, the Directory Synchronization Agent creates a custom recipient and a contact to redirect mail to the mailbox that is currently being used. Exchange Migration Wizard can use the X.400 protocol or the Simple Mail Transfer Protocol (SMTP) for mail redirection. When the X.400 protocol is used, mail is redirected to the mailbox s unique X.400 address. Each user s Exchange 5.5 and Exchange 200x mailboxes have the same primary SMTP address, so it cannot be used for mail redirection. If you choose SMTP, the Directory Synchronization Agent creates an additional SMTP address for each source and target mailbox. These additional addresses are generated using the templates you specify in this step. Step 6. General Synchronization Options This step allows you to set the directory synchronization direction. If you are going to administer only one of the directories during the transition period, select the direction in which the directory changes will be propagated. If you will administer both the Exchange 5.5 directory and Active Directory during the transition period, select the Both directions option. Note that the next steps of the wizard will allow you to fine-tune the synchronization options for each type of Exchange 5.5 and Active Directory object. This page also allows you to set in which containers the auxiliary Exchange 5.5 custom recipients and Active Directory contacts for mail redirection will be created. 37

40 Quest Exchange Migration Wizard Step 7. Exchange 5.5 to Active Directory Synchronization The Directory Synchronization Agent will synchronize the object types you select in this step from Exchange 5.5 to Active Directory. If in the General Synchronization Options step of the wizard you selected to synchronize directories either from Exchange or in both directions, all the object types are selected by default. You can optionally select which objects should be created in the Active Directory if the matching objects for the corresponding Exchange objects are not found. The objects will be created in the container you specify. If you select to create Active Directory groups, select whether the newly created group will be domain local, global, or universal, and specify whether it should be a distribution group (such as an distribution list) or a security group that can be used in access-control entries. 38

41 Directory Synchronization Normally, the distribution groups should be created. If any of the source distribution lists is used to grant client permissions on a mailbox folder or a public folder, Exchange 200x will automatically convert the corresponding group to a security group when the agents synchronize permissions for this folder. Please note that Exchange 2003 does not allow universal security groups when it is running in mixed mode. If you select to create universal distribution groups and are going to synchronize folder permissions, you must have Exchange 2003 running in native mode. Step 8. Create Options If you select to create Active Directory user objects, the next step of the wizard will prompt you for the create options for the user accounts. By default the Directory Synchronization Agent creates disabled user accounts with blank passwords. Exchange 200x does not allow you to grant client permissions on mailbox folders and public folders to the mailboxes that are created for the disabled user accounts unless the Associated External Account is set. If you want to create disabled user accounts, make sure the Set the Associated External Account option is selected in the job Properties. Refer to the Directory Synchronization Job Settings section below for more details on this option. You might want the Directory Synchronization Agent to create enabled Active Directory accounts. In this case, specify whether the Directory Synchronization Agent should randomly generate passwords or if all passwords should be set to the same value. 39

42 Quest Exchange Migration Wizard The Directory Synchronization Agent generates 14-symbol long passwords using any English uppercase and lowercase letters, numerals (0, 1, 2,... 9), and non-alphanumeric special characters, such as punctuation symbols. If you select the option to create complex passwords, the agent will verify that each password contains characters from at least three of these four classes and that it does not contain any part of the user s full name. Step 9. Select Directory Synchronization Members The Directory Synchronization Agent will search for the objects to be synchronized in the Exchange 5.5 recipient containers you select in this step. You can individually select which containers will be searched for which type of objects. If your migration plan requires it, you can explicitly select the objects to be synchronized. Be careful though, and avoid explicitly selecting an object that already participates in the same or another directory synchronization job via the selected container. Also, if you explicitly select the objects to be synchronized, the objects created in the Exchange 5.5 directory after you configure the job will be out of the synchronization scope. If you want the directory synchronization job to synchronize the entire source site to the target domain, you should not select any containers in this step. Just skip the step by clicking the Next button. If you want to use an alternative target Exchange mailbox store for the selected containers and objects, click the Advanced button. 40

43 Directory Synchronization To change the default mailbox store select the item in the Target Exchange Servers and Mailbox Stores dialog and click the Select Target Mailbox Store button. Select the Use the following Exchange server and mailbox store option and select the desired server and mailbox store from the correspondent lists. Click OK subsequently to apply the settings. 41

44 Quest Exchange Migration Wizard Step 10. Active Directory to Exchange 5.5 Synchronization The Directory Synchronization Agent will synchronize object types selected in this step from Active Directory to Exchange 5.5. If in the General Synchronization Options step of the wizard you selected to synchronize directories either from Active Directory or in both directions, all the object types are selected by default. You can optionally select which objects should be created in the Exchange 5.5 if the matching objects for the corresponding Exchange objects are not found. The objects will be created on the source Exchange 5.5 server selected for the job in the container you specify. Step 11. Conflict Resolution The Directory Synchronization Agent can automatically resolve conflicts during the transition period. If the agent synchronizes objects in both directions, you can set the preferred replication direction. When an object is modified in both directories, it will be synchronized in the direction you specify in this step. The Exchange 5.5 recipient can have both Accept and Reject restriction lists, while the Active Directory management tools support only one restriction list for a mailbox. In the Delivery Restrictions lists box, select whether Exchange Migration Wizard should synchronize only the Accept list, only the Reject list, or both lists when both lists are present. In the latter case, the lists can be viewed and modified only in the Exchange 5.5 directory. 42

45 Directory Synchronization The Exchange 5.5 distribution list can report to both the distribution list owner and to the message originator, while the Active Directory management tools support sending delivery reports to only one recipient. In the Report Translation box, select whether the wizard should set only the distribution list owner, only the mailbox originator, or both in Active Directory when both delivery report recipients are selected for an Exchange 5.5 distribution list. In the latter case, the option can be viewed and modified only in the Exchange 5.5 directory. Step 12. Object Matching Specify how the Directory Synchronization Agent will match Exchange 5.5 objects with objects in Active Directory. 43

46 Quest Exchange Migration Wizard If the Match by the primary Windows NT account / SID option is selected for Mailboxes (this option is selected by default), the Directory Synchronization Agent will match an Exchange 5.5 mailbox with the user object in Active Directory if one of the following is true: The primary Windows NT account of the Exchange 5.5 mailbox points to the Active Directory user. The Security Identifier (SID) of the primary Windows NT account for the Exchange 5.5 mailbox is in the SIDHistory attribute of the Active Directory user. If the Match by the primary SMTP address option is selected for Mailboxes, the Directory Synchronization Agent will match an Exchange 5.5 mailbox with the user object in Active Directory if the primary SMTP address of the Exchange 5.5 mailbox is equal to the primary SMTP address of the Active Directory user. The Directory Synchronization Agent matches Exchange 5.5 distribution lists with Active Directory groups and Exchange 5.5 custom recipients with Active Directory contacts by their primary SMTP address, by default. However, you can change the default matching for distribution lists and custom recipients by selecting the corresponding option from the Object Matching filed. Specifically, you can configure the agent to match these object types by their display names (select the Match by the object's Display Name option). If you select Exchange 5.5 distribution lists and custom recipients to match with corresponding objects in Active Directory by their display names, you should make sure that no Exchange 5.5 distribution lists or custom recipients have identical display names within Exchange 5.5 environment. Otherwise, these objects will be incorrectly matched to the same Active Directory object (i.e. the duplicate match will occur). Refer to the Exchange Migration Wizard - Directory Object Matching for more information. 44

47 Directory Synchronization Step 13. Completing the Wizard After you set up the job, you can select the Start the synchronization job after closing this window check box in the last step of the wizard. 45

48 Quest Exchange Migration Wizard Directory Synchronization Settings All the options that you set in the Add Directory Synchronization Job Wizard are later available in the job s and the agent s Properties dialogs. Directory Synchronization Job Settings To modify any of a directory synchronization job s settings, right-click the job in the Management Tree and click Properties on the shortcut menu. In addition to the settings in the wizard when creating a job, there are additional options in the directory synchronization job Properties dialog box. During the transition period, situations may arise that require full resynchronization of the directories. Select the Full resynchronization check box on the General page of the job s properties to force the Directory Synchronization Agent resynchronize directories for this job. Select the Restore redirection check box to make the agent verify that the redirection custom recipients and contacts exist. If this check box is not selected, the agent will consider the redirection established and will check only whether the objects custom attributes containing auxiliary redirection-related information (Custom Attribute 15 by default) are valid. The Check addresses for duplicates option forces the agent to check each address of the synchronized objects within all the objects of the entire organization. If this check box is not selected, the Directory Synchronization Agent checks an object s addresses for duplicates only within the objects of the same type. 46

49 Directory Synchronization Configure the Exchange 5.5 Queries Exchange Migration Wizard searches for the objects to be synchronized using the LDAP queries. You can reduce the scope of the synchronization by adding custom filters to the default LDAP queries for each object type. The filters you type in this page will be added to the default filter with the AND logical operator. The LDAP search filters are defined in RFC2254. These search filters are represented by Unicode strings. For example, to synchronize only mailboxes whose display name starts with s, in the Mailboxes text box you should type the following: (cn=s*) However, we recommend that this functionality is used only if your migration plan requires it. Only advanced administrators familiar with the LDAP syntax should create such filters. The wizard does not check the validity of the filters you type and an incorrect filter might cause errors during the directory synchronization process. You can also specify the LDAP queries for the Active Directory to Exchange synchronization. The Advanced page of the directory synchronization job s properties allows you to change settings that are not set in the wizard. 47

50 Quest Exchange Migration Wizard The Synchronize permissions check box is selected by default. Clear the check box if you do not want the Directory Synchronization Agent to synchronize directory objects permissions. Select the Set the Associated External Accounts check box for the Directory Synchronization Agent to make the Primary Windows NT Account of the source mailbox the Associated External Account of the target user. This will allow the users to use these accounts to access the Exchange 200x mailboxes and public folders. Select also whether the agent should Replace the existing Associated External Accounts with the Primary Windows NT Accounts of the source mailboxes. The Rolling Migration mode check box is selected by default. This option makes the Directory Synchronization Agent set a special attribute for each synchronized object, as described in the Object Attributes Used for Directory Synchronization section. The Rolling Migration mode option is key for the Rolling Exchange Migration scenario. Please see the Exchange Migration Wizard - Rolling Exchange Migration document for more details. Select the Ignore synchronization schedule check box to make the Directory Synchronization Agent ignore its schedule when performing this job. The option is cleared by default. It is useful when the Directory Synchronization Agent performs several directory synchronization jobs and one of them has higher priority. If the Active Directory Connector has been used in your environment to create Active Directory contacts corresponding to the Exchange 5.5 mailboxes, you should select the Delete ADC created contacts in the target domain check box. Otherwise, the Directory Synchronization Agent will try to reuse these contacts when establishing mail redirection. 48

51 Directory Synchronization Please note that the full resynchronization will be automatically initiated for the job if you modify any of the settings listed below: Mail redirection type SMTP address templates, if SMTP redirection is used Synchronized objects (both from Exchange 5.5 and from Active Directory) LDAP queries (both from Exchange 5.5 and from Active Directory) Synchronization members The Synchronize permissions or the Rolling Migration mode options on the Advanced page If there are connection problems with the Directory Synchronization Agent server and the changes you make cannot be applied to the agent s database, the changes will not be lost. Project Manager will save the changes to the job in the Exchange Migration Wizard configuration database. When the Directory Synchronization Agent server is available again, right-click the job in the Management Tree and click Update Task to save changes in the agent s database on the remote server. SMTP Matching for Linked Attributes In order to maintain a common Global Address List (GAL) for all Exchange 5.5 organizations, the customer uses custom recipients (CR) that point to mailboxes in other source organizations. Since all source organizations are to be migrated to the single Exchange 200x environment, the CRs will not be migrated. However, they can be used to populate linked attributes such as DL membership. When synchronizing any of the object attributes that contain links to other objects, the DSA is unaware of target user accounts that correspond to the source CRs. Hence, these attributes are not populated for the AD objects that are being synchronized. Attributes that are affected include: Accept/Reject mail from (all objects) Member (distribution lists only) Owner (distribution lists only) Manager (mailboxes and custom recipients) Give Send on behalf of (mailboxes only) Alternate recipient (mailboxes only) 49

52 Quest Exchange Migration Wizard To set up the alternative matching for the source custom recipients, mailboxes and distribution lists, click the More options button in the Synchronization Advanced page of the directory synchronization job Properties dialog and use the SMTP Matching for Linked Attributes settings. Directory Synchronization Agent s Settings To modify the Directory Synchronization Agent s settings, right-click the agent s installation server under the Directory Synchronization node of the Management Tree and click Properties. The settings available in the agent s properties will affect all the jobs performed by the agent. 50

53 Directory Synchronization Server The Server page provides service priority information and settings used to connect to the server where the agent is installed can be specified, including: The name of the server where the agent is installed. The account under which the agent connects to the server. Click Modify to change the account. Please note that the specified account should be a local administrator account on the server. The priority of the Quest Directory Synchronization Agent service. By default, it is set to Normal. If several different services apply to one resource simultaneously, service with higher priority will receive an access to the resource first. If the users experience troubles due to heavy traffic originated by the agent's activity, the agent's service priority can be set to Low. That will help unload the resource traffic. Options The Options page helps you set up the following agent's log properties: Append log - select whether the log file should be appended or overwritten during each session. Max log size - enter the maximum log file size in MB if you wish to limit it. The default value of the field is 0. That means that the log file size is not limited. 51

54 Quest Exchange Migration Wizard Schedule The Schedule page allows you to specify the schedule for the agents, as follows: Synchronization Schedule - select the time when the agent is allowed to run. You can select off-peak hours to make sure the agent does not produce stress on the server. Synchronization method - select whether or not the agent should stop for a sleeping period after each synchronization session: Synchronize continuously - the agent will keep looking for unsynchronized mail throughout the allowed working hours. Sleep duration between sessions - the agent will stop for the specified interval between the synchronization sessions. Cache In order to increase the agent's efficiency, a matching cache is created on the server where the Directory Synchronization Agent is working. This means that the agent does not need to search for matching information for every object in both directories during every session. The Cache page helps you specify the cache data expiration period and the necessity to reset the cache after closing the Properties dialog box, as follows: Data expires after - sets the time period (in hours) after which an Exchange/Active Directory object pair is refreshed. Reset cache after closing this dialog box - When this dialog box is closed, the matching cache will be reset. All object pairs will be reestablished. 52

55 Directory Synchronization Agent Performance Counters Directory Synchronization The Directory Synchronization Agent performance counters allow you to monitor the agent. To see the Directory Synchronization Agent performance counters, do the following: 1. From the Start menu, select Administrative Tools and select Performance. 2. In the Performance dialog, select System Monitor. 3. In the right-hand pane, click the Add toolbar button. 4. Specify the server on which the Directory Synchronization Agent is installed. Note that you should be logged on under an account that has administrative rights on the remote server to see its performance. 5. Select the Quest EMW DSA from the list of available Performance objects. 6. Select the counters you want to monitor. 7. Click Add and then close the Add Counters dialog box. 53

56 Quest Exchange Migration Wizard Object Attributes Used for Directory Synchronization Exchange Migration Wizard uses four object attributes for directory synchronization. This section describes what information is stored in those attributes and how this information is used during the synchronization process. The Directory Synchronization Agent can use any of the objects extension attributes. The attributes that you specify to be used by the Directory Synchronization Agent must be empty before the agent is started. Otherwise, the agent might not work correctly. We recommend you to run the Exchange Migration Preparation Wizard Free Custom Attributes within Organizations report to search for unused attributes. The Exchange Migration Preparation Wizard is a complementary program to Quest Exchange Migration Wizard. It can be found on Exchange Migration Wizard distribution CD. With Exchange Migration Preparation Wizard you can collect information about the source Exchange 5.5 environment, run a number of pre-defined reports that display the conflicting objects, and resolve the conflicts. Refer to the Exchange Migration Preparation Wizard - User Guide for more details. It is also possible to use other attributes if the custom attributes are already used in your environment. Please contact technical support if this is required for your migration project. In some environments, new objects are created by copying a template mailbox. If you use such a template to create new mailboxes, you must consider the attributes populated by the Directory Synchronization Agent. The template mailbox must be excluded from the directory synchronization by LDAP filters, or you should clean the custom attributes when copying the template mailbox. 54

57 Directory Synchronization Exchange Migration Wizard can use any of the available 15 custom attributes. To set which attributes should be used to store the directory synchronization information, click Options on the Tools menu and go to the Directory Synchronization Options page. Each attribute used is described below in detail. Auxiliary Information Auxiliary redirection information is stored by default in custom attribute 15. This attribute stores the information on the redirection custom recipient and contact created for an object by the Directory Synchronization Agent, such as: The names of the redirection custom recipient and contact Which mailbox is currently active (i.e., whether the mailbox is switched or not) Whether a mailbox had been configured to redirect incoming mail to another mailbox before the migration The attribute used to store this information is also referenced as the auxiliary attribute. This attribute is initially populated by the Directory Synchronization Agent when it first finds the corresponding object in the opposite directory and creates the redirection custom recipient and contact. This happens when the object participates in the directory synchronization for the first time. For objects that exist in the Exchange 5.5 directory or Active Directory before the synchronization starts, this happens during the agent s first synchronization session. 55

58 Quest Exchange Migration Wizard The information stored by the attribute is later used by the Mail Source Agent and the Mail Target Agent, when the mailbox is switched to the target server. This attribute is also used when you switch a mailbox from the console manually. Refer to the Mailbox Switch section below for more information on mailbox switch operation. The attribute is automatically re-populated if the custom recipient or contact redirection is deleted and re-created by the Directory Synchronization Agent. The data in this attribute is stored in the agent s internal format. Do not populate or modify the attribute manually. Auxiliary Information Attribute Inter-Site Replication To prevent issues with mailbox switch status update when you refresh the organization in Exchange Migration Wizard Project Manager you need to establish inter-site replication of the Auxiliary Information Attribute in Exchange 5.5. The Exchange 5.5 Directory Replication Connector does not replicate Custom Attributes between sites by default. You need to force the Directory Replication Connector to replicate the attribute that stores the auxiliary information between Exchange 5.5 sites. Please refer to the Exchange Migration Wizard - Quick Start Guide for more information on how to establish inter-site replication of the attributes. Individual Object Synchronization Options Individual object synchronization options are stored by default in custom attribute 14. This attribute is used to exclude a single object from the directory synchronization. It can be populated manually by an administrator if needed. The following attribute values are recognized by the agent: EMWDSADoNotSynchronize The Directory Synchronization Agent will not look for the corresponding object in the opposite directory. The object will not be synchronized. EMWDSADoNotMatch The Directory Synchronization Agent will not consider this object to correspond to any object from the opposite directory, even if it meets the matching rules. It will create a new object instead, if the option to create objects was selected. Usually administrators do not need to use this attribute. These options are useful only if for any reason you do not want to synchronize some of the directory objects, for example, if you want to manually create and configure the administrator s mailbox. 56

59 Directory Synchronization Target Object s GUID The target object s global unique identifier (GUID) is stored by default in custom attribute 13. This attribute is used in the Exchange 5.5 directory only. It stores the GUID of the target Active Directory object corresponding to the Exchange 5.5 object. This attribute is initially populated by the Directory Synchronization Agent when it first finds the corresponding object in the Active Directory. This happens when the object participates in the directory synchronization for the first time. For objects that exist in the Exchange 5.5 directory before the synchronization starts, this happens during the agent s first synchronization session. The information stored by the attribute is later used to find the corresponding object in the target Active Directory. Because the GUID is unique within Active Directory, the target object can be renamed or moved to another location and it will still be recognized as corresponding to the source Exchange 5.5 directory object. The attribute used to store the matching target object's GUID is also referenced as the matching attribute. Indexing this attribute will increase the agent s performance. Please see the How to Increase Directory Synchronization Performance section for details. Target Object s GUID Attribute Inter-Site Replication When an agent needs to find the target object by the source object s distinguished name (DN), it queries the source server for the source object s custom attribute, which stores the target GUID. However, the Exchange 5.5 Directory Replication Connector does not replicate custom attributes 11 to 15 between sites by default. For this reason, the target agent will fail to retrieve the matching information. Consequently, permissions on a folder will not be granted or a rule will not be updated if the rules or folder permissions are set up for an object from a different site. To avoid this issue, you need to force the Directory Replication Connector to replicate the attribute that stores the target object GUID between Exchange 5.5 sites. Please refer to the Exchange Migration Wizard - Quick Start Guide for more information on how to establish inter-site replication of the attributes. 57

60 Quest Exchange Migration Wizard Rolling Migration Attribute The Rolling Migration attribute is stored by default in custom attribute 12. This attribute is populated by the Directory Synchronization Agent when it creates new Exchange 5.5 or Active Directory objects. The attribute is set for both the initial object and the newly-created corresponding object. The Directory Synchronization Agent populates this attribute if it is working in Rolling Migration mode. The option is set in the Advanced page of the Directory Synchronization Job Properties dialog box. This attribute, when populated, prevents other directory synchronization jobs from considering the objects synchronized by this job to be new or not matched. Other agents will not require the corresponding objects to be created in the other source or target directory. This prevents the software from creating duplicate Exchange 5.5 and Active Directory objects in complex migration scenarios. Please see the Exchange Migration Wizard - Rolling Exchange Migration document for details. Skip Attributes Auxiliary Information Attribute The Directory Synchronization Agent is able to skip the specified attributes when processing the directory synchronization jobs. This functionality requires to store auxiliary information in one of the custom attributes. By default, the skip attributes auxiliary attribute is the Custom Attribute 11. Select an attribute in Active Directory to store the Exchange 5.5 object's distinguished name (DN). The Exchange 5.5 objects' DN is stored to help the Directory Synchronization Agent track the situation when the source object is replaced by a new object matched to the same target object after the first synchronization of a pair of objects. In this case the Directory Synchronization Agent will detect the difference between the source and target objects by the DN value in the specified attribute, which means that that the object pair is being synchronized for the first time. 58

61 Considerations for Using Custom Attributes Directory Synchronization After the Directory Synchronization Agent populates custom attributes of the synchronized objects, all the other Exchange Migration Wizard components can recognize them. All the components rely on the custom attributes, so be sure to consider the following: In many environments, new mailboxes are created by copying a template mailbox. Note that after the Directory Synchronization Agent has processed an Exchange 5.5 mailbox, that mailbox will be matched to a certain Active Directory user by the GUID stored in one of its custom attributes (Custom Attribute 13, by default). Copying such a mailbox will lead to incorrect matching of several source mailboxes to the same target user. We recommend you to run the Exchange Migration Preparation Wizard Mailboxes with Duplicate Matching Attributes report on the regular basis to search for mailboxes with duplicated matching attributes. The Exchange Migration Preparation Wizard is a complementary program to Quest Exchange Migration Wizard. It can be found on Exchange Migration Wizard distribution CD. With Exchange Migration Preparation Wizard you can collect information about the source Exchange 5.5 environment, run a number of pre-defined reports that show the conflicting objects, and resolve the conflicts. Refer to the Exchange Migration Preparation Wizard - User Guide for more details. You should not change the attributes to be used after the Directory Synchronization Agent has once processed any objects. If you need to change any of the attributes to be used by Exchange Migration Wizard, you have to export the legacy attribute values and then use them to populate the new attribute. For example, you can use the Csvde.exe utility to do the directory export or import. 59

62 Quest Exchange Migration Wizard How to Improve Directory Synchronization Performance The initial directory synchronization is a complex and time-consuming task. The speed of the directory synchronization depends on various factors, including the number of objects in the Exchange 5.5 directory and Active Directory, the network connection bandwidth, and the server load. While some of these cannot be changed, others can be. Specifically, indexing of some attributes in the Exchange 5.5 directory highly improves directory synchronization performance. Please refer to the Exchange Migration Wizard - Quick Start Guide for the procedure and the list of attributes that should be indexed to accelerate the directory synchronization process. 60

63 6 Public Folder Synchronization Synchronization Process Setting Up a New Public Folder Synchronization Job Public Folder Synchronization Settings Starting Public Folder Synchronization Stopping Public Folder Synchronization 61

64 Quest Exchange Migration Wizard Before the users are migrated to the new Exchange 200x environment, you need to copy the public folders contents to the new servers. This ensures that the first migrated user will access the up-to-date public folders. Exchange Migration Wizard uses two-way synchronization for public folders. For example, when a user who is already migrated to Exchange 200x posts a note to an Exchange 200x public folder, the note automatically gets posted to the corresponding Exchange 5.5 public folder. This lets the users share data throughout the migration process. Client permissions on public folders are also preserved and synchronized in both environments. Exchange 5.5 permissions are automatically translated into the corresponding Exchange 200x permissions. Exchange Migration Wizard also allows on-the-fly public folders structure reconfiguration. You can use this ability to improve the public folder structure. 62

65 Public Folder Synchronization Synchronization Process Public folder synchronization is performed as Tpublic folder synchronization jobst. You can migrate public folders from any Exchange 5.5 servers that have public folder replicas. Each public folder synchronization job is configured individually. Public folder synchronization jobs are performed by small and efficient public folders agents installed on Exchange 5.5 and Exchange 200x servers. Because Exchange Migration Wizard can synchronize public folders in both directions, each server can be a source of data and a target at the same time. Exchange Migration Wizard Exchange 5.5 Site Public Folder Source Agent Exchange 2000/2003/2007 Administrative Group Transmission Agent Public Folder Target Agent Public Folder Source Agent Transmission Agent Public Folder Target Agent The following public folder synchronization agents are installed on the Exchange servers: The Public Folder Source Agent locates unsynchronized mail in the source public folders, stores it together with auxiliary information for the target agent in the PUB files, and compresses them. The Transmission Agent transfers the compressed PUB files directly to the destination Exchange server. It also moves PRV files across the network for mailbox synchronization. Please see the Mailbox Synchronization section for details. The Public Folder Target Agent decompresses PUB files, retrieves mail from them, and stores it in the destination public folders. 63

66 Quest Exchange Migration Wizard To make public folder synchronization available in both directions, all the agents should be installed on both the Exchange 5.5 and Exchange 200x servers. Regardless of the synchronization type, one-way or two-way, both the Public Folder Source Agent and the Public Folder Target Agent are installed on source and target servers. However, for one-way synchronization, only the Public Folder Source Agent and the Transmission Agent on the source server and the Public Folder Target Agent on the target server are used. See the Exchange Migration Wizard - Overview document for further information on this process. Public Folder Collections Exchange Migration Wizard allows you to fine-tune the public folder synchronization job by introducing public folder collections. A collection is a set of pairs of the source and target folders that will be used as roots of synchronization. Each collection can include several synchronization roots. A job may handle multiple collections. You can set up the workflow and synchronization settings for each collection. Also, you can suspend the synchronization of a public folder by temporarily disabling the corresponding public folder collection. Public Folder Source Agent The Public Folder Source Agent (PFSA) iterates through the folders of the currently processed public folder collection. For each folder under the synchronization root folder, the Public Folder Source Agent queries Exchange for the changes made since the last saved synchronization state. The agent retrieves these changes and puts them into a PST file. The PST files (Personal Folders files) are data files that store your messages and other items on your computer. This file format is used by Microsoft Outlook to store and back up items. The PST file is compressed and put to a service file (PUB) together with auxiliary information for the target agent. When all folders from a collection are in sync, the Public Folder Source Agent goes to the next public folder collection with lower priority. 64

67 Public Folder Synchronization Transmission Agent The Transmission Agent moves the PUB files created by the Public Folder Source Agent to the target Exchange server. To reduce network load, the agent moves the PUB files with data directly to the destination server. If public folder data from the server is synchronized with several servers, the Transmission Agent moves data in parallel, using a separate thread for each target server. Public Folder Target Agent The Public Folder Target Agent (PFTA) processes incoming PUB files, decompresses their contents, and puts it into the target public folders. The public folder synchronization agents do not change anything in the synchronized messages and folders. The majority of the message fields (including the Sent and Received dates and all address fields) and folder properties remain unchanged. The users in both Exchange organizations see the same messages in their public folders. Synchronization of Deleted Public Folders Exchange Migration Wizard synchronizes messages and folders and their properties and permissions. In addition, all of the changes made to a folder or message, including renaming, moving, and deletion, are synchronized. To avoid data loss, the network administrator should create a special public folder called Aelita EMW Recycle Bin. When a public folder is deleted in one of the environments, the public folder synchronization agents move the corresponding folder in the other environment to the Aelita EMW Recycle Bin folder. Thus, administrators can verify that no important information has been deleted and can restore data if it was deleted by mistake. 65

68 Quest Exchange Migration Wizard For example, a folder moved outside of the current synchronization root is considered deleted. In this case, the Aelita EMW Recycle Bin folder prevents data from being lost. Although the folders are moved to the Recycle Bin and an administrator can move them back, folders that have been deleted once cannot be migrated again. This is because public folder synchronization agents preserve the folders SOURCE_KEY property. On the side where the folders are actually deleted, Exchange tombstones the deleted folders and does not allow creation of folders with the same SOURCE_KEY property again. Therefore, you should never delete production public folders on either source or on target. If you want to experiment with a folder and delete it later, create a test public folder specifically for that purpose. Never experiment with live folders. If you want to do a pilot public folder migration, create a test public folder and use it for your experiments. Avoid doing pilots on the production folders. However, there is a partial workaround to make the agent re-synchronize public folders that were deleted on the target. You need to create copies of the public folders that you want to re-synchronize on the source. When you copy a folder, it gets a new SOURCE_KEY, and therefore the agents will be able to create it on the side where it was deleted. Note that public folder addresses, links, and rules will be lost because you copied the folder. For more information about public folder resynchronization, refer to the Exchange Migration Wizard Resynchronization document. The Aelita EMW Recycle Bin folder should be replicated to all the public folders servers involved in the public folders synchronization process. The Limit administrative access to home site check box should be deselected in the Aelita EMW Recycle Bin folder properties. Setting Up a New Public Folder Synchronization Job To create a new public folder synchronization job, right-click the Public Folders Synchronization node of the Management Tree and click Add Public Folders Synchronization Job on the shortcut menu. This will start the Add Public Folders Synchronization Job Wizard to help you to install the public folder synchronization agents and configure the job. This section guides you through each step of the wizard and explains the available public folder synchronization options. 66

69 Step 1. Select Exchange Servers Public Folder Synchronization The public folder synchronization job is set up between the source and target servers that you select in this step of the wizard. For both the source and the target server, you should specify an administrative mailbox that will be used by Project Manager and the public folder synchronization agents. Refer to the Exchange Migration Wizard - Quick Start Guide for more information about the administrative mailboxes. The account under which the public folder synchronization agents are running should have full access to the corresponding mailboxes so that they can get administrative access to the synchronized folders. Be careful when selecting the administrative mailboxes. Once you start the public folder synchronization process, you should not change the administrative mailboxes. This will lead to full resynchronization of public folder contents and might cause other issues. Project Manager will retrieve the public folder hierarchy using the mailboxes you specify. If you want to specify an alternative account for the hierarchy retrieval, click the Advanced button and specify the corresponding credentials. The wizard will also create the first collection for the job. This first step prompts you for the collection name. 67

70 Quest Exchange Migration Wizard Step 2. Select Public Folders The next step allows you to configure the public folder synchronization collection. Select the root folders to be synchronized. If you don t want to change the folder hierarchy, the easiest way is to select All Public Folders in both Exchange 5.5 and Exchange 200x as the synchronization roots. Deleted public folders cannot be migrated again. If you want to do a pilot public folder migration, create a test public folder and use this folder for your experiments. Avoid doing pilots on the production folders. Experimenting on test folders as opposed to the real ones used by your end-users is the only way to ensure that the pilot project won t interfere with the production migration in the future. You can select an existing Exchange 200x folder as a target root folder. If the target root folder does not exist, you can create it by selecting the Add New Folder command from the shortcut menu as shown on the figure below. Project Manager does not actually create the public folders. The public folder root will be created by the Public Folder Target Agent when the first PUB file comes from the corresponding Exchange 5.5 or Exchange 200x folder. To add a pair of folders to the collection, select the folders in both lists, set the synchronization direction, and click Add. The folders and all their subfolders will be marked as included in the collection. 68

71 Public Folder Synchronization Once you start the public folder synchronization process, you should not change the synchronization roots for any jobs or collections. Changing the selected folder pairs after the synchronization has started might result in duplicate folders in one of the environments. To exclude a folder from synchronization, right-click the folder in the tree and click Exclude. The public folder synchronization agents will not synchronize the content of the folder, but will create it on the corresponding server and synchronize its subfolders, if any. Click Exclude with subfolders to exclude from synchronization a folder itself and all its subfolders. 69

72 Quest Exchange Migration Wizard Step 3. Specify Agent Installation Path The wizard will install the public folder synchronization agents on the Exchange 5.5 and Exchange 200x servers. You can specify the installation path for the agents or keep the default settings. Then click Next. Step 4. Completing the Wizard After the agents are installed, the wizard will inform you that you can start the public folder synchronization job. We recommend that you verify all the agents and collection settings before starting the public folder synchronization. The available options are discussed in the Public Folder Synchronization Settings section below. Step 5. Commit Changes Once a new job is created, it is marked with an exclamation mark. This means that you need to update the public folder synchronization agents databases before starting the job. Right-click the job in the Management Tree and click Commit Changes on the shortcut menu to update the agents task lists on the remote servers. Public Folder Synchronization Settings The options that you specify in the Add Public Folders Synchronization Job Wizard are available in the collection s settings. You can add more collections to the public folder synchronization job. Also, there are different settings specific for the public folder synchronization agents. This section describes options available in both the collection and the agents properties. 70

73 Public Folder Synchronization Add Public Folder Collection To create a new collection for an existing public folder synchronization job, right-click the job in the Management Tree and click Add Collection on the shortcut menu. This will start the Add Public Folders Collection Wizard that will help you to set up and configure a new collection for the job. Each of the wizard s steps is described in this section. Step 1. General Options Specify the name for the collection. Optionally, you can provide a text description for the collection. The collection priority is set automatically and cannot be changed. The collection created first always has the highest priority. You can temporarily disable the collection and it will not be involved in the synchronization process until you enable it. If you want only to migrate public folders and their contents to the target servers, select the Stop synchronizing public folder when it is in sync check box. In this case the agents will not look for changes after the folders are in sync. 71

74 Quest Exchange Migration Wizard Step 2. Workflow The next step of the wizard allows you to set the preferred start and end dates for migrating the collection. By default, the option to Start as soon as possible is selected. You can specify the date and time for the agent to start processing the collection. The collection will not be processed by the agent until the specified time is reached. You can also specify the date and time for the agent to stop processing the collection. When the specified time is reached, the agent will not process the collection any longer. Step 3. Synchronization If the folders that you are including in the collection were previously synchronized, you might want to resynchronize the folders or the public folder items. These options are useful if errors occurred during the previous public folders migration and it is necessary to re-copy data that has already been sent to the target server. For more information about resynchronization of public folders, please refer to the Exchange Migration Wizard Resynchronization document. 72

75 Public Folder Synchronization Step 4. Select Public Folders Populate the collection with public folder pairs and select the one-way or twoway synchronization for every pair. Note that the folders that are already synchronized within other collections of the job are marked in the folders lists and cannot be included in the collection. Once you start the public folder synchronization process, you should not change the synchronization roots for any jobs or collections. Changing the selected folder pairs after the synchronization has started might result in duplicate folders in one of the environments. Step 5. Complete the Wizard and Commit Changes Once the new collection is created, the job is marked with an exclamation mark, which means that you need to update the public folder synchronization agents databases. Right-click the job in the Management Tree and click Commit Changes on the shortcut menu to update the agents task lists on the remote servers. Public Folder Collection Settings All the options that you specify in the Add Public Folders Synchronization Job Wizard and the Add Public Folders Collection Wizard are later available in the collection s properties. To view or modify a collection s settings, right-click the collection in the Management Tree and click Properties on the shortcut menu. 73

76 Quest Exchange Migration Wizard After you modify any of the collection s settings, the job is marked with an exclamation mark, which means that you need to update the public folder synchronization agents databases. Right-click the job in the Management Tree and click the Commit Changes on the shortcut menu to update the agent s task lists on the remote servers. Public Folder Synchronization Agents Settings Each Exchange Migration Wizard agent is configured individually. For each of the public folder synchronization agents, you can set its scheduling, logging, and other options. The Source Server Properties and the Target Server Properties dialog boxes allow you to configure the Public Folder Source Agent, Transmission Agent, and Public Folder Target Agent on every server involved in the migration. General Options There are various options available for the Public Folder Source Agent (PFSA) and the Public Folder Target Agent (PFTA). The General pages of the source and target agents properties allow you to view and modify the following synchronization settings: 74 Administrator Mailbox is used to get administrative access to the server s public folders. It is the same mailbox that you select when setting up a public folder synchronization job. This mailbox does not need any rights on the public folders for the synchronization. The account that is used by the agent should have full access to the mailbox that is specified here. Be careful when selecting the administrative mailboxes. Once you start the public folder synchronization process, you should not change the administrative mailboxes. This will lead to full resynchronization of public folder contents and might cause other issues. Copy rules and Copy permissions check boxes allow you to select whether the folder rules and permissions should be synchronized. These check boxes should be selected for both the source and the target agents. In order to avoid possible conflicts, it is not recommended to synchronize public folder rules in both directions. By default, the rules are synchronized from Exchange 5.5 to Exchange 200x only. The agents store their configuration and statistics in a separate database file. For each agent you can specify how frequently the database should be compacted.

77 Public Folder Synchronization The preceding options are common for the Public Folder Source Agent and the Public Folder Target Agent. Each also has additional options, explained below. For the Public Folder Source Agent you can specify the following options: Whether the folder-associated information such as Forms and Views should be copied to the target servers. Whether the folders belonging to Newsgroup Hierarchies should be skipped. Whether only the messages modified recently should be copied to the target. By default, this option will only apply to the IPM.Note and IPM.Post type messages. The maximum size of mail data put to each PST file. The path where the agent s tracking database should be located. The database is used to store the agent s cache and might grow significantly during the agent s sessions. The default and recommended location of the tracking database is the drive on the Exchange server running the agent. It is not recommended to change this default location. The alternative account credentials for the hierarchy retrieval. When the Public Folder Source Agent is installed on the cluster server, the tracking database is created by default on the shared drive of the Exchange server. If you change the location of the tracking database, make sure that you have selected the shared drive of an Exchange server that is a member of the same Exchange Virtual Server group. 75

78 Quest Exchange Migration Wizard For the PFTA, you can also specify the following: Whether the agent should archive an incoming PST file that cannot be processed and how long the agent should try to process each PST file It is strongly recommended that you set all the options before you start the migration. If you decide to synchronize public folders permissions and/or folder associated information after the folders have been synchronized, you will have to clean up the folders with the help of the Exchange Migration Wizard Cleanup Wizard. (Please see the Resource Kit User Guide for more information on the cleanup process.) Compression The Public Folder Source Agent compresses the PST files before putting them into service PUB files and sending them to the destination servers. The Compression page of the Public Folder Source Agent s properties allows you to select whether the agent should compress mail data and to specify the compression level. If the agent does not compress data, it works faster, but network traffic increases because larger files are transferred to the target servers. 76

79 Public Folder Synchronization Logging Every Exchange Migration Wizard agent saves its logs on the server on which the agent is installed. For each agent you can specify whether the log file will be overwritten or appended during each session, and select which events will be written to the log. The Public Folder Source and Target Agents can send the statistics to an administrator by . All types of events are logged on by default. The log files are highly useful for troubleshooting that often requires the detailed information. This, it is not recommended to change the default logging settings. For more information on the log files and mail notifications, please see the Getting Statistics, Logging Information, and Reports section. Scheduling Options Each public folder synchronization agent has its own scheduling options. This lets you define separately when the agents are allowed to produce additional stress on the Exchange servers and on the network. For each agent you can specify: The hours during which each agent is allowed to run. On the agent s Schedule page of the Server Properties, click Synchronization Schedule. In the dialog box that appears, select the time frame during which the agent should perform synchronization jobs. Whether there should be a sleep period between the agent s sessions. 77

80 Quest Exchange Migration Wizard Starting Public Folder Synchronization After the directory synchronization for all the source Exchange 5.5 sites finishes its first cycle, the target directory is fully populated and matching for all object pairs is established. At this point you can start moving the public folder data to the new Exchange 200x servers. When folder permissions are synchronized, it is critical that matching is established before you start the public folder synchronization. To start the public folder synchronization agents, right-click the job in the Management Tree and click Start All Agents or start each agent individually with the corresponding shortcut menu commands. Stopping Public Folder Synchronization Exchange Migration Wizard can synchronize public folders continuously or only until they are in sync. The option to stop synchronizing public folders means that if a folder pair is in sync, the agents will mark it as synchronized and will not look for changes in these folders any more. This is useful if you want only to move the contents of the folders to the Exchange 200x server and not to synchronize them. You can also select the Stop synchronizing public folder when it is in sync check box on the General page of the Public Folders Collection Properties dialog box when no more users are using the public folders from a collection on the Exchange 5.5 side. In this case the agents move the rest of unsynchronized folder data to the target and stop processing the folders. 78

81 7 Mailbox Synchronization Synchronization Process Setting Up a New Mailbox Synchronization Job Mailbox Synchronization Settings Starting Mailbox Synchronization Checking Mailbox Synchronization Status Mailbox Switch Client Profile Update 79

82 Quest Exchange Migration Wizard The main aim of the Exchange migration is to move every user s mailbox content unchanged to the new Exchange 200x mailbox. After the user s mailbox is switched to the target Exchange server, it should be an exact replica of the user s source mailbox. This is achieved by the mailbox synchronization. During the mailbox synchronization, Exchange Migration Wizard gradually transfers the mail data from the source Exchange 5.5 to the target Exchange 200x servers. All mailbox content, including messages with attachments, contacts, and journal entries, is copied to the target mailboxes. Synchronization Process Mailbox synchronization is performed as a separate mailbox synchronization job between each pair of the source Exchange 5.5 and target Exchange 200x servers. To provide minimal stress to the production environment, Exchange Migration Wizard employs the distributed architecture shown in the figure below. Exchange Migration Wizard Mail Source Agent Mail Target Agent Transmission Agent Exchange 5.5 Server Exchange 2000/2003/2007 Server 80

83 Mailbox Synchronization Mailbox synchronization jobs are performed by small and efficient mail agents that are installed on the source and target Exchange servers: The Mail Source Agent is installed on the source Exchange 5.5 server. It locates the unsynchronized mail in the source mailboxes, stores it together with auxiliary information for the target agent in the PRV files, and compresses the data. The Transmission Agent is also installed on the Exchange 5.5 server. It transfers the compressed PRV files directly to the destination Exchange 200x server. The same agent moves PUB files across the network for public folder synchronization. Please see the Public Folder Synchronization section for details. The Mail Target Agent is installed on the target Exchange 200x server. It decompresses PRV files, retrieves mail from them and stores it in the destination mailboxes. See the Exchange Migration Wizard - Overview document for a detailed description of the process. Mailbox Collections To provide flexibility, the mailboxes to be synchronized are grouped into mailbox collections. A mailbox synchronization job may handle multiple collections. Each of these collections has its own settings, including the destination mailbox store and the preferred dates for migrating the collection s mailboxes. This allows you to plan and configure the whole mailbox migration before you start it. Collections can be populated manually in Project Manager, based on prepared import lists, or randomly generated. 81

84 Quest Exchange Migration Wizard Remote Users Collections One widely-used Microsoft Outlook feature is offline access to a user s mailbox folders. The offline folders (OST) file is stored on a user s computer and keeps a local replica of the corresponding folders in the user s Exchange mailbox. Users who typically work with the offline folder (OST) files and occasionally connect to their Exchange Mailboxes are referred to in this document as the remote users. Because each OST file is associated with only one Exchange mailbox and cannot be used with any other mailbox, a user cannot continue to use the same OST file with the new mailbox after migration. To migrate remote user mailboxes, you can use the Remote Users Collection feature. The mailboxes of remote users should be grouped in Remote Users Collections and processed separately from other mailbox collections after the directory synchronization has been completed. You can create one or several Remote Users Collections depending on the number of remote user mailboxes. Remote Users Collections are processed differently than other mailbox collections. Refer to the Processing Remote Users Collections section for more details. Mail Source Agent The Mail Source Agent (MSA) goes from one mailbox of the currentlyprocessed mailbox collection to another. For each mailbox, it queries Exchange for changes made since the last-saved synchronization state, and stores these changes in a new PST file. The PST files (Personal Folders files) are data files that store your messages and other items on your computer. This file format is used by Microsoft Outlook to store and back up items. The PST file is then compressed and put into a service PRV file together with auxiliary information for the Mail Target Agent. When all mailboxes from the current collection are processed, the Mail Source Agent proceeds to the next mailbox collection and then to the job with another target server (in case there is one). Next, the Mail Source Agent goes back to the first mailbox collection of the first target server, whether or not the previous PST file for the mailbox was removed. The Mail Source Agent (or the Mail Target Agent in case of Remote Users Collection) switches the synchronized mailboxes to the target server. Please see the Mailbox Switch section for details. 82

85 Mailbox Synchronization Transmission Agent The Transmission Agent moves the PRV files created by the Mail Source Agent to the target Exchange 200x server. To reduce network load, the agent moves PRV files with data directly to the destination servers. If mail data from the server is synchronized with several servers, the Transmission Agent uses a separate thread for each target server. Mail Target Agent The Mail Target Agent (MTA) receives the PRV files, decompresses their contents, and puts it into the target mailboxes. The mail agents do not change anything in the synchronized message. The majority of the message fields (including the Sent and Received dates and all address fields) remain unchanged. After the switch, the user will have in the target mailbox the same messages as were in his or her source mailbox. Processing Remote Users Collections The mailboxes of the Remote Users Collections are copied and switched by the Mail Target Agent only. The Transmission Agent and Mail Source Agent do not do anything with these mailboxes. The following considerations apply for Remote Users Collections processing: The PRV files are not created to migrate the mailboxes and, thus, the mailbox data is not compressed but is copied directly to the target server. The Mail Target Agent checks whether the mailbox is logged on. If the user is logged on to the mailbox and the time period since the user logged on to the mailbox is less than 7 days, the Mail Target Agent skips this mailbox from processing in the current session. The Mail Target Agent starts processing the mailbox if it is not logged on or if the user has been logged on to the mailbox for more than 7 days. In the latter case, the user is logged off from the mailbox. 83

86 Quest Exchange Migration Wizard If the target mailbox corresponding to the remote user s source mailbox already exists when the Mail Target Agent starts processing the source mailbox, the Mail Target Agent will remove the target mailbox with all its contents and recreate the target mailbox during the next session. After successful recreation of the target mailbox, the Mail Target Agent starts copying the content of the source mailbox to the target mailbox. As soon as the content is successfully copied, the Mail Target Agent switches the mailbox and creates two hidden messages: a switch message and a recreate message. The switch message will be used by the Client Profile Updating Utility (EMWProf) for updating a mailbox profile. The recreate message will be used for updating the offline folder (OST) file. When the Mail Target Agent processes a mailbox belonging to a Remote Users Collection, that mailbox becomes unavailable for the users for the time of its migration. Therefore, these collections should be scheduled to be processed at the time when the users do not use their mailboxes. For more information about scheduling the collection, refer to the Add Mailbox Collection and Mailbox Collection Settings sections of this document. Setting Up a New Mailbox Synchronization Job To add a new mailbox synchronization job, right-click the Mailbox Synchronization node in the Management Tree and click Add Mailbox Synchronization Job on the shortcut menu. This will start the Add Mailbox Synchronization Job Wizard that will install the mailbox synchronization agents and help you to set up and configure the job. This section guides you through each step of the wizard and explains the available mailbox synchronization options. 84

87 Mailbox Synchronization Step 1. Select Exchange Servers Select the source and the target servers for the mailbox synchronization job. The wizard will display the existing mailbox synchronization jobs in which the selected servers already participate. Step 2. Select Mailbox Store The Mail Target Agent will create the Exchange 200x mailboxes in the Mailbox Store you specify in this step. The mailbox store that you specify in this step of the wizard will be used as default for all the mailbox collections of the job. Later you can individually set a target mailbox store for each of the mailbox collections. Please note that if an Exchange 200x mailbox already exists, it will be moved to the mailbox store specified for the collection. For the existing Exchange 200x mailboxes, it is recommended to select the mailbox stores where they are hosted. This will avoid an increase in network traffic. If Exchange 2003 is running in mixed mode, it will not allow the Mail Target Agent to move a mailbox between Administrative Groups. If the mailboxes were created by the Directory Synchronization Agent in another Administrative Group, the target organization should be in native mode to perform the mailbox migration. 85

88 Quest Exchange Migration Wizard Step 3. Create Collections The wizard can automatically create mailbox collections for the job. You can select one of the following options: Not to create mailbox collections. In this case you should later create collections manually as described below. Create one mailbox collection. In this case the wizard will prompt you to populate the collection in the next step. Create a separate mailbox collection for each mailbox store on the target server. In this case, the name of each collection will be identical to the name of the target mailbox store to which the mailboxes from the collection will be migrated. In the next step, the wizard will allow you to populate each of the collections. Automatically create collections with the specified number of mailboxes. In this case the wizard will create collections that are already populated, each of which will contain the specified number of mailboxes. You should also specify the collection name template to which the wizard will add the creation date and the number of the collection. 86

89 Mailbox Synchronization Step 4. Populate Collections If you selected to create one collection for the job or a collection per each target mailbox store, the next step of the wizard allows you to populate the collections. Select the collection name from the list and click Add to populate collection with mailboxes, distribution lists, or containers. The following mailboxes from a collection will be processed: Mailboxes explicitly added to the collection. Mailboxes implicitly listed in the added distribution lists. Note that if a distribution list contains other distribution lists, mailboxes from the nested distribution lists will not be processed. Only mailboxes hosted on the source server are migrated. Mailboxes from the containers that are added to the collection (both explicitly and implicitly, through other containers). Step 5. Specify Agent Installation Path The wizard will install the mailbox synchronization agents on the Exchange 5.5 and Exchange 200x servers. You can specify the installation path for the agents or keep the default settings. 87

90 Quest Exchange Migration Wizard Step 6. Complete the Wizard After the agents are installed, the wizard will inform you that you can start the mailbox synchronization job. We recommend that you verify all the agents and collection settings before starting the mailbox synchronization. The available options are discussed in the Mailbox Synchronization Settings section below. Step 7. Commit Changes Once a new job is created, it is marked with an exclamation mark. This means that you need to update the mailbox synchronization agents databases before starting the job. Right-click the job in the Management Tree and click Commit Changes on the shortcut menu to update the agents task lists on the remote servers. Mailbox Synchronization Settings The options that you specify in the Add Mailbox Synchronization Job Wizard are available in the collection s settings. You can add more collections to the mailbox synchronization job. Also, there are different settings specifically for the mailbox synchronization agents. This section describes options available in both the collection and the agents properties. Add Mailbox Collection To create a new mailbox collection for an existing mailbox synchronization job, right-click the job in the Management Tree and click Add Collection on the shortcut menu. This will start the Add Mailbox Collection Wizard to help you to set up and configure a new collection for the mailbox synchronization job. Each step of the wizard is described below. Though the Remote Users Collections are also added using the Add Mailbox Collection, the steps for creating the Remote Users Collection are somewhat different. Please pay attention to the notes regarding Remote Users Collections in the steps below. 88

91 Mailbox Synchronization Step 1. General Options In the first step of the wizard, specify general collection settings such as collection name and description. If you are planning to create a Remote Users Collection, specify a name and description that clearly indicate this fact. You can temporarily disable the collection and it will not be involved in the synchronization process until you enable it. Step 2. Workflow The next step of the wizard allows you to set the preferred start date for migrating the collection. By default, the option to Start as soon as possible is selected. 89

92 Quest Exchange Migration Wizard If you want the mailbox synchronization agents to switch the mailboxes from the collection once they are synchronized, select the Switch mailboxes with unsynchronized mail size option and specify the size of mail that can remain unsynchronized by the time the mailboxes of the collection will be switched. As soon as the agent processes the mailbox which contains less unsynchronized mail than the size of mail that can remain unsynchronized, it will set up auxiliary custom recipients to automatically forward all incoming mail from the old Exchange 5.5 mailbox to the new Exchange 200x mailbox. You can also specify whether a mailbox should be switched even if errors occurred during synchronization or if there are appointments that were not processed by the Calendar Synchronization Agent. You can also schedule the mailboxes switching. The agent will not switch any mailbox until the specified time is reached. If you do not want the mailbox synchronization agents to switch mailboxes automatically, select the Do not automatically switch mailboxes option. In this case you will need to switch mailboxes manually using Project Manager. Please see the Mailbox Switch section for more information on what mailbox switch is and how you can manually switch a mailbox to the Exchange 200x server. To create a Remote Users Collection, select the Switch mailboxes and preserve offline folder (OST) files option. It is recommended to start the Remote Users Collection synchronization after the directory synchronization is completed and before the calendar synchronization is started. Step 3. Synchronization If the mailboxes you plan to include in the collection were previously synchronized, you might want to resynchronize the mailboxes or the mail items. These options are useful if errors occurred during the previous mailbox migration and it is necessary to re-copy data that has already been sent to the target server. 90

93 Mailbox Synchronization If you are adding a Remote Users Collection, this page will not be displayed. The Remote Users Collection cannot be resynchronized using these options. To make the Mail Target Agent process mailboxes from the Remote Users Collection again, you need to undo the switch for them using Project Manager. After that, the Mail Target Agent will remove the previouslycreated target mailboxes with all their contents and start the mailboxes resynchronization. Step 4. Complete the Wizard and Commit Changes Once the new collection is created, the job is marked with an exclamation mark, which means that you need to update the mailbox synchronization agents databases. Right-click the job in the Management Tree and click Commit Changes on the shortcut menu to update the agents task lists on the remote servers. Populate Mailbox Collection The mailbox collection can be populated manually, or the mailboxes can be imported from an external list file. Alternatively, the collections can be automatically created and populated by the Add Mailbox Synchronization Job Wizard as described above. The following mailboxes from a collection are processed: Mailboxes explicitly added to the collection. Mailboxes implicitly listed in the added distribution lists. Note that if a distribution list contains other distribution lists, mailboxes from the distribution list-members will not be processed. Only mailboxes hosted on the source server are migrated. Mailboxes from the containers that are added to the collection (both explicitly and implicitly, through other containers). To cancel the migration of any mailbox that has already been added to a collection, simply remove the mailbox from the collection and commit the changes to the agent database. 91

94 Quest Exchange Migration Wizard Import Mailbox Collection Members Exchange Migration Wizard allows you to import a list of mailboxes to be migrated from a file, such as an Excel spreadsheet or a plain text file. You can also import a Microsoft Exchange Administrator directory export or the Quest InTrust Exchange Account Grouping report. If you create a Remote Users Collection, you can find out which mailboxes store their offline data in OST files and which do not using the Quest Offline Folder Wizard. The wizard analyzes the mailboxes of the selected servers and provides three lists for every analyzed server: 1. A list containing the Distinguished Names of the mailboxes storing their offline data in OST files 2. A list containing the Distinguished Names of the mailboxes not storing their offline data in OST files 3. A file containing a list of the errors that occurred when the wizard attempted to logon to mailboxes The wizard can analyze both Exchange 5.5 and Exchange 200x servers. You can import the first list to Remote Users Collections. For more information about the Offline Folder Wizard, please refer to the Offline Folder Wizard User Guide. To import members to a collection from a file, right-click the mailbox synchronization job node in the navigation pane and select Import Members from the shortcut menu. This will start the Import Members Wizard. The wizard steps are described below. Step 1. Specify Import File Type the full path or browse to the import file. Select whether the import file is a custom import file or an Exchange Accounts Grouping report. For a custom file, select what character is used as a column separator. If the Exchange Accounts Grouping report is used as an import file, the wizard will create several collections according to the information in the report. 92

95 Mailbox Synchronization Step 2. Select Matching Attribute The table in the next wizard s steps is obtained from the file you specify. Select whether the first row of the table is the column header. Select Match attribute from the list and select the column that contains the attribute to match on. In the example shown in the figure below, the wizard will search for mailboxes with display names equal to the values in the selected column. If the Exchange Accounts Grouping report is used as an import file, this step is skipped. 93

96 Quest Exchange Migration Wizard Step 3. Select Mailboxes Location Specify either the Exchange 5.5 server on which the mailboxes are hosted or the Recipients container in which the mailboxes are located. Step 4. Mailbox Collections Select the mailbox synchronization job and the collection to be populated. The wizard can either import members to an existing collection, or create a new mailbox collection. If the import files contain mailboxes that were already added to other mailbox collections, you might not want to remove them from those collections. In this case, select the check box at the bottom of the page. 94

97 Mailbox Synchronization If the Exchange Accounts Grouping report is used as an import file, you should provide a template for generating the collection names. To guarantee the uniqueness of each collection s name, the wizard will generate names in the following format: <Template>_imp_<Date><Time>_<Group> where: <Template> is the template you specify in this step of the wizard. <Date> is the current date in YYYYMMDD format. <Time> is the current time in HHMMSS format. <Group> is the group number in the report. Step 5. Complete the Wizard and Commit Changes The wizard informs you about the number of entries from the import file that were applied and the number of errors. After you click Finish you need to update the mailbox synchronization agents databases. Right-click the job in the Management Tree and click Commit Changes on the shortcut menu to update the agents task lists on the remote servers. Populate a Collection Manually To populate a collection manually, you can: With the source server, container, or Global Address List selected in the Management Tree, do the following: a) In the right-hand pane, select mailboxes, distribution lists, or containers. b) Right-click the selection, point to Add To, and click Mailbox Collection. c) Specify the collection in the Add to Collection dialog box that will appear. Drag mailboxes, distribution lists, or containers from the source server, the Global Address List or the Recipient container onto the collection. Drag mailboxes from the All Mailboxes collection onto the collection. This is the simplest way, because all mailboxes of the server can easily be found here. Note that the mailboxes are not removed from the All Mailboxes collection when you drag them to other mailbox collections. The changes made to a synchronization job and its collections do not take effect until you right-click the job and click Commit Changes on the shortcut menu. 95

98 Quest Exchange Migration Wizard Mailbox Collection Settings All the options that you specify in the Add Mailbox Collection Wizard are later available in the collection s properties. To view or modify a collection s settings, right-click the collection in the Management Tree and click Properties on the shortcut menu. Note that in addition to the options you specify in the Add Mailbox Collection Wizard, you can specify the target Mailbox Store for the mailboxes of this collection. The Mail Target Agent will create the Exchange 200x mailboxes in the Mailbox Store you specify for the collection. Please note that if an Exchange 200x mailbox already exists, it will be moved to the mailbox store specified for the collection. If your target Exchange organization is operating in mixed mode, it is strongly recommended to be careful when selecting the target Mailbox Store for the Remote Users Collection. It is recommended to select only the Mailbox Store, located in the Administrative Group where the target mailbox will reside permanently after the migration, for mailbox creation. If you select the store in another Administrative Group for mailbox creation, you will not be able to move the mailbox from this store after migration is finished until you switch your organization to native mode. After you modify any of the collection s settings, the job is marked with an exclamation mark, which means that you need to update the mailbox synchronization agents databases. Right-click the job in the Management Tree and click the Commit Changes on the shortcut menu to update the agent s task lists on the remote servers. 96

99 Mailbox Synchronization Agents Settings Each agent is configured individually. Mailbox Synchronization For each of the mailbox synchronization agents, you can set its scheduling, logging, and other options. To access the source server Properties dialog, which allows you to configure the Mail Source Agent and the Transmission Agent, right-click the Source Organizations <SourceOrganizationName> <SiteName> Servers <ServerName> node in the navigation pane and select Properties from the shortcut menu. To access the target server Properties dialog which allows you to configure the Mail Target Agent, right-click the Target Organizations <TargetOrganizationName> Administrative Groups <ExchangeAdministrativeGroupName> Servers <ServerName> node and select Properties from the shortcut menu. General Options There are various options available for the Mail Source Agent and the Mail Target Agent. The General pages of the source and target agents properties allow you to view and modify the following synchronization settings: Copy permissions check box allows you to select whether the folder permissions should be synchronized. Note that this check box should be selected for both the source and the target agents for the permissions to be synchronized. For each agent you can specify how frequently the agent s local databases should be compacted. The preceding options are common to the Mail Source Agent and the Mail Target Agent. In addition, for the Mail Source Agent you can select: Whether folder-associated information, such as Forms and Views, should be copied to the target servers. Whether only messages modified recently should be copied to the target. The maximum size of mail data put to each PST file. 97

100 Quest Exchange Migration Wizard The path where the auxiliary agent s database should be located. The database is used to store the agent s cache and might grow significantly during the agent s sessions. If the Mail Source Agent is installed on the cluster server, the tracking database is created by default on the shared drive of the Exchange server. If you change the location of the tracking database, make sure that you have selected the shared drive of an Exchange server that is a member of the same Exchange Virtual Server group. For the Mail Target Agent, you can specify the following: Whether the agent should archive an incoming PST file that cannot be processed. How long the agent should try to process each PST file. The timeframe for the agent to process the Remote Users Collections. To specify this, click Schedule and select the time when the agent is allowed to process the Remote Users Collections. You can select off-peak hours to make sure the agent does not produce stress on the server. The Mail Target Agent that is to process the Remote Users Collection should be scheduled for a time when the remote users do not normally use their mailboxes. The Remote Users Collection mailboxes will be unavailable for the users during their migration. Also, note that the Mail Target Agent (MTA) skips the logged-on mailboxes. So, it is recommended to schedule the MTA to process these mailboxes during the off-peak hours. When the agent has switched theses mailboxes, run EMWProf to finalize their migration. For more information, refer to the Client Profile Updating Utility - User Guide. Please note that, while processing the Remote Users Collections mailboxes, the Mail Target Agent will ignore the settings specified on this page, except for the frequency of database compacting and scheduling settings. 98

101 Mailbox Synchronization Please select all the options you want before you start the migration. If you decide to synchronize mailbox folders permissions and/or folder-associated information after the mailboxes have been synchronized, the agents will not resynchronize the folders and messages that are already in sync. In this case, you will have to resynchronize the mailbox folders and messages. Compression The Mail Source Agent compresses the PST files before putting them into service PRV files and sending them to the destination servers. The Compression page of the Mail Source Agent s properties allows you to select whether the agent should compress mail data and specify the compression level. If the agent does not compress data, it works faster, but the network traffic is higher because larger files are transferred to the target servers. 99

102 Quest Exchange Migration Wizard Logging Each agent saves its logs on the server on which the agent is installed. For each agent you can specify whether the log file will be overwritten or appended during each session, and select which events will be written to the log. The Mail Source Agent and Mail Target Agent can send the statistics to an administrator by . All types of events are logged on by default. The log files are highly useful for troubleshooting that often requires the detailed information. This, it is not recommended to change the default logging settings. For more information on the log files and mail notifications, please see the Getting Statistics, Logging Information, and Reports section. Scheduling Options Each mailbox synchronization agent has its own scheduling options. This lets you define separately when the agents are allowed to produce additional stress on the Exchange servers and on the network. For each agent you can specify: The hours during which each agent is allowed to run. On the agent s Schedule page of the <ServerName> Properties dialog, click Synchronization Schedule and select the time frame during which the agent should perform synchronization jobs. Whether there should be a sleep period between the agent s sessions. 100

103 Starting Mailbox Synchronization Mailbox Synchronization We recommend that the first mailbox synchronization job be started after the directories are in sync and the public folders are replicated to the Exchange 200x server, and that it be started together with all the calendar synchronization jobs for all servers. This will ensure that the first user switched to the target mailbox will: See the full Global Address List (GAL) Have access to the public folders Have access to other users Free/Busy information and (if needed) detailed calendar data To start a mailbox synchronization job, right-click the job in the Management Tree and click Start All Agents on the shortcut menu. Checking Mailbox Synchronization Status The Collection Analyzing Utility validates the mailbox synchronization process and reports on synchronization status. The utility performs the following actions for each mailbox from the specified mailbox collection: Checks whether the redirection custom recipient corresponding to the Exchange 5.5 (source) mailbox exists in the Exchange 5.5 directory. Examines the address of the redirection custom recipient and verifies that the same SMTP address exists in the corresponding target mailbox proxy addresses list. Checks whether the redirection contact corresponding to the Exchange 200x (target) mailbox-enabled user exists in Active Directory. Examines the address of the redirection contact and verifies that the same SMTP address exists in the corresponding source mailbox proxy addresses list. Checks if the auxiliary attributes of the source and the target mailboxes are populated by the Directory Synchronization Agent. Checks that the msexchmailboxguid attribute of the target Active Directory user is not empty and that its format is correct. 101

104 Quest Exchange Migration Wizard Checks whether the service accounts specified for Exchange Migration Wizard agents have sufficient permissions to access the source and target mailboxes. Reports on whether the mailbox is switched, Reports on the number of items in the source and target mailboxes. When checking whether the service accounts have sufficient permissions, Collection Analyzing Utility performs the following operations with each source and target mailbox from the specified collection: log on get inbox log off The utility does not check whether the service accounts have access to public folders nor does it check whether the accounts have the logon as service right on the source and target servers. The utility creates a plain-text report file. Each record in the report file consists of the following fields, separated by semicolon: ErrorCode; Sourc boxDN; TargetMailboxDN; SourceRedirectorDN; TargetRedirectorDN; Sourc boxDisplayName; Sourc boxItemsCount; TargetMailboxItemsCount; SwitchStatus; error description(s) Where: ErrorCode - The code identifying an error that occurred during processing. A detailed list of the codes can be found in the List of Error Codes section below. Sourc boxDN - The distinguished name of the source Exchange 5.5 mailbox. TargetMailboxDN - The distinguished name of the target Exchange 200x mailbox-enabled user. SourceRedirectorDN - The distinguished name of the redirection custom recipient in the Exchange 5.5 directory. TargetRedirectorDN - The distinguished name of the redirection contact in Active Directory. Sourc boxDisplayName - The display name of the source Exchange 5.5 mailbox. Sourc boxItemsCount - The number of items in the source mailbox. 102

105 Mailbox Synchronization TargetMailboxItemsCount - The number of items in the target mailbox. SwitchStatus - The switch status of the mailbox: switched, not switched, or unknown. Error description(s) - Description of the errors that occurred during processing. A list of error codes and their descriptions can be found in the List of Error Codes section below. The file containing the report is created in the folder from which Collection Analyzing Utility is run. The file name is comprised of the collection name, the source Exchange server name, and the time stamp, as follows: CollectionName_SourceExchangeServerName_YYYYMMDDHHMMSS.txt. For example: Collection2_rsource_ txt The Collection Analyzing Utility can be run from either Project Manager or the command line. Running Collection Analyzing Utility from Project Manager To run the utility from Project Manager, right-click a mailbox collection, and select Analyze Collection from the shortcut menu. You can configure the behavior of the Collection Analyzing Utility from the Options dialog in Project Manager. To modify available parameters, from the Tools menu, select Options, and go to the Collection Analyzing Utility page. 103

106 Quest Exchange Migration Wizard The following parameters are available on this page: Verify if the agents can log on to source and target mailboxes - Select this option if you want the utility to verify whether the service account specified for the Exchange server has sufficient permissions to log on to the source and target mailboxes. Note that if the number of mailboxes in the collection is large, this might be a time-consuming operation. This option is selected by default. Report on the number of items in source and target mailboxes - Select this checkbox if you want the utility to report on the number of items in source and target mailboxes - members of the collection. This option is selected by default. When the utility has completed processing the collection, click View Report in the Collection Analyzing Utility dialog box to review the report file. Running Collection Analyzing Utility from the Command Line The Collection Analyzing Utility is installed to the %Program Files%\Quest Software\Exchange Migration Wizard folder by default during Exchange Migration Wizard Project Manager installation. To use the utility, run CRCheck.exe with the following command-line parameters: CRCheck.exe /c:<collectionname> /s:<sourceexchangeservername> /t:<targetexchangeservername> [/m] [/i] [/d] /c: - Mailbox collection name. /s: - Source Exchange server name. /t: - Target Exchange server name. 104

107 Mailbox Synchronization /m: - Check whether the service account specified for the Exchange server has sufficient permissions to log on to the source and target mailboxes from the specified collection. Note that if the number of mailboxes in the collection is large, this might be a time-consuming operation. Specify [on] or [off] values to enable or disable this parameter correspondingly. /I - Report on the number of items in source and target mailboxes - members of the specified collection. Specify [on] or [off] values to enable or disable this parameter correspondingly. /d: Delete redirection custom recipients from the Exchange 5.5 directory and redirection contacts from Active Directory. For example: CRCheck.exe /c:collection2 /s:sourceex55 /t:targetex2000 /m:on /i:on Important: If the the homemdb attribute of the source mailbox does not match the source server name specified in the command line, the mailbox will be skipped during processing. When the utility has completed processing the collection, review the report file created in the directory where the utility resides. List of Error Codes The following errors can be written to a report file during Collection Analyzing Utility operation: crclerrabsentssourc box = 1 - The mailbox is a member of the specified collection but it was not found in the Exchange 5.5 directory. crclerrabsentstargetuser = 2 No target user with the GUID from the CA13 attribute of the source mailbox was found in Active Directory. crclerrabsentssourceredirector = 4 - The custom recipient used to redirect mail from the source Exchange 5.5 mailbox was not found. crclerrabsentstargetredirector = 8 - The contact used to redirect mail from the target Exchange 200x mailbox was not found. crclerrabsentsaddressinsourceredirector = 16 - The custom recipient used to redirect mail from the source Exchange 5.5 mailbox does not have the target address. 105

108 Quest Exchange Migration Wizard crclerrabsentsaddressintargetredirector = 32 - The contact used to redirect mail from the target Exchange 200x mailbox does not have the target address. crclerrabsentsaddressinsourc box = 64 - The source mailbox does not have an address to receive messages redirected from the corresponding target Exchange 200x mailbox via the redirection contact. crclerrabsentsaddressintargetuser = The target user does not have an address to receive messages redirected from the corresponding source Exchange 5.5 mailbox via the redirection custom recipient. crclerrabsentsauxilaryattributeforsourc box = Could not read the auxiliary attribute of the source mailbox. Either the attribute was not found or the attribute value is invalid. crclerrabsentsauxilaryattributefortargetuser = Could not read the auxiliary attribute of the target user. Either the attribute was not found or the attribute value is invalid. crclerrabsentsmailboxguid = The msexchmailboxguid attribute of the target user was not found. crclerrcannotlogonintosourc box = Could not log on to the source mailbox. This error is logged if the service account specified for the source Exchange 5.5 server (source Exchange account) does not have sufficient permissions to access the mailbox. crclerrcannotlogonintotargetmailbox = Could not log on to the target mailbox. This error is logged if the service account specified for target Exchange 200x server (target Exchange Account) does not have sufficient permissions to access the mailbox. crclerrinvalidmailboxguid = The value of the msexchmailboxguid attribute of the target user is invalid. 106

109 Mailbox Synchronization Mailbox Switch As soon as a user s Exchange 5.5 and Exchange 200x mailboxes are in sync, the Mail Source Agent (or the Mail Target Agent in case of the Remote Users Collection) can switch the mailbox to the target server. Mailbox switch allows all the Exchange Migration Wizard components to recognize the mailbox as switched and ensures that all new mail now arrives in the user s target mailbox. To switch a mailbox, the Mail Source Agent (or the Mail Target Agent in case of the Remote Users Collection) does the following: When the mailbox is in sync, the agent modifies the source and target mailboxes delivery options. The agent sets the auxiliary custom recipients for automatic forwarding from the old Exchange 5.5 mailboxes to the new Exchange 200x mailboxes. Source User1 (MB) SMTP or X400 connector Target User1 is mailbox-enabled User1 (CR) - hidden from GAL User1 (Contact) - hidden from GAL If unsynchronized mail is allowed in the collection s properties, the Mail Source Agent will set mail redirection when there is less unsynchronized mail in the mailbox than the allowed size. Please see the Mailbox Synchronization Settings section for details. After redirection is set, the agent puts a hidden switch message to the source Exchange 5.5 mailbox. The switch message contains information about the corresponding target mailbox and is used for updating client profiles. If the mailbox was processed in a Remote Users Collection, an additional hidden message is saved in the mailbox by the Mail Target Agent that instructs the EMWProf to preserve the OST file. Please see the Client Profile Update section for details. 107

110 Quest Exchange Migration Wizard During the next session after setting mail redirection, the Mail Source Agent processes the mailbox to make sure all mail is sync. If unsynchronized mail is found in the mailbox, it is synchronized during this session. In case of the Remote Users Collection, the Mail Target Agent moves the mailbox and its' content completely. After this operation the mailbox switch is performed. Finally, the agent marks the mailbox as switched with a special MAPI property. The mailbox and calendar synchronization agents recognize a mailbox with this property set as being switched. Manual Mailbox Switch Project Manager allows you to manually switch mailboxes included in the mailbox collections. To switch mailboxes: 1. In the Management Tree, select the mailbox collection. 2. Select the mailboxes to be switched in the right-hand pane. 3. Right-click the selection and click Switch Mailboxes on the shortcut menu. 4. Select which of the switch actions should be done. For example, you can set mail delivery options and create a switch message for the Client Profile Updating Utility, but not mark the mailboxes as switched. Remote Users Collections are switched automatically. Manual mailbox switch is impossible for mailboxes included in a Remote Users Collection. 108

111 Mailbox Synchronization Undo Mailbox Switch The mail agents do not change or delete anything on the source Exchange 5.5 server. When a mailbox is switched to the target server, new mail arrives only in the target mailbox. That is why any user having problems with Exchange 200x can be switched back to his initial mailbox by an administrator. To undo a mailbox switch: 1. In the Management Tree, select the mailbox collection. 2. Select the mailboxes to be switched back in the right-hand pane. 3. Right-click the selection and click Undo Mailboxes Switch on the shortcut menu. 4. Select which of the switch actions should be rolled back. If you undo the mailbox switch for a mailbox included in a Remote Users Collection, the Mail Target Agent will remove the previously-created corresponding target mailbox and start resynchronizing the mailbox. Client Profile Update Exchange Migration Wizard provides the Client Profile Updating Utility (EMWProf.exe) to automatically update Microsoft Outlook client profiles to use the new Exchange 200x mailboxes. EMWProf updates the profile settings and preserves the offline folder (OST) files for the mailboxes included in Remote Users Collections. EMWProf is integrated with the mailbox synchronization agents. The utility can be run from a logon script and uses the switch and recreate messages created by the mail agents as a source of information. This makes the mailbox switch and profile update unnoticeable for the users. When the utility updates the profile configured for a mailbox, it also updates mailbox rules and copies the read/unread status for the mailbox messages. This ensures that the user s new Exchange 200x mailbox is an exact replica of the source mailbox by the time the user first logs on to it. Please refer to the Client Profile Updating Utility - User Guide for details on the Client Profile Updating Utility. 109

112

113 8 Calendar and Free/Busy Synchronization Personal Calendars Synchronization Free/Busy Information Synchronization Setting Up a New Calendar Synchronization Job Calendar Synchronization Settings Starting Calendar Synchronization 111

114 Quest Exchange Migration Wizard Real-time calendar synchronization during the Exchange migration period is necessary for the transition to be transparent to the users. The users communicate as if they were within a single Exchange organization. For example, a user can always schedule a meeting with the users from another organization, or see whether another user is free or busy. Calendar synchronization is performed as a separate calendar synchronization job between each pair of source and target servers. Calendar synchronization jobs are performed by the Calendar Synchronization Agents (CSA) installed on the source Exchange 5.5 servers. Each Calendar Synchronization Agent synchronizes the personal Calendar folders of the mailboxes hosted on the Exchange 5.5 server with the corresponding mailboxes on its target Exchange 200x server. When calendars are synchronized, their Free/Busy information is updated automatically. However you can also set up synchronization of Free/Busy information, in which case, the Free/Busy information for all mailboxes in a site is synchronized by a single Calendar Synchronization Agent as close to real time as possible. 112

115 Calendar and Free/Busy Synchronization Personal Calendars Synchronization Exchange Migration Wizard synchronizes personal Calendar folders, including scheduled meetings and appointments, resource scheduling settings and folder permissions. The Calendar folders contents are the only mail items that are not synchronized by the mailbox synchronization agents. The Calendar Synchronization Agent copies appointments rather than messages, and the user s Free/Busy information is updated according to the newly-created calendar entries. The Calendar Synchronization Agent logs on to each source and target mailbox to locate unsynchronized calendar entries and copies them to the other corresponding mailbox. When an appointment is copied to the mailbox, the Free/Busy information is automatically updated. This allows all the users in both directories to view the up-to-date detailed calendar and Free/Busy information for other users and resource mailboxes, whether or not a mailbox is already migrated. You can set the Calendar Synchronization Agent for either one-way or two-way synchronization. One-way calendar synchronization means that the calendar entries for each source-target mailbox pair are synchronized one-way only, from the currentlyactive mailbox to the other mailbox: If the mailbox is not switched, the calendar entries are synchronized from Exchange 5.5 to Exchange 200x only. After the mailbox is switched to the target server, the calendar entries are synchronized from Exchange 200x to Exchange 5.5. Two-way calendar synchronization allows you to have up-to-date calendar information even if the mailbox is used on both sides, which is useful for the resource mailboxes and delegates. The calendar permissions are always synchronized one-way, from Exchange 5.5 to Exchange 200x, regardless of whether the mailbox is switched. 113

116 Quest Exchange Migration Wizard Free/Busy Information Synchronization When set for two-way synchronization, the Calendar Synchronization Agent processes all mailboxes of a server for about minutes, assuming the number of the mailboxes is close to the Microsoft recommendations (approximately 1000 mailboxes per server). If users in your organization need to have the most up-to-date Free/Busy information, you can configure one of the Calendar Synchronization Agents to synchronize just this information more frequently. Microsoft Exchange Server stores the users Free/Busy information in a special hidden public folder called SCHEDULE+ FREE BUSY. A replica of this folder is stored in each Exchange 5.5 site and each Exchange 200x Administrative Group. The folder contains a special Free/Busy message for each mailbox of the site or Administrative Group. That is why only one Calendar Synchronization Agent in the site is required to synchronize the Free/Busy information for all mailboxes of the source site. It is recommended to synchronize the Free/Busy information with the Calendar Synchronization Agent installed on the server on which the SCHEDULE+ FREE BUSY folder is located. It is usually the first Exchange 5.5 server in the site. Please refer to the Exchange 5.5 Server documentation for details. Because Free/Busy information should be synchronized as close to real time as possible, Free/Busy synchronization runs according to its own schedule. You can specify the agent s own synchronization period and Free/Busy synchronization will occur at the specified interval. Setting Up a New Calendar Synchronization Job To add a new calendar synchronization job, right-click the Calendar Synchronization node in the Management Tree and click Add Calendar Synchronization Job on the shortcut menu. This will start the Add Calendar Synchronization Job Wizard that will install the Calendar Synchronization Agent and help you to set up and configure the job. This section guides you through each step of the wizard and explains the available calendar synchronization options. 114

117 Step 1. Select Exchange Servers Calendar and Free/Busy Synchronization Select the source and the target servers for the calendar synchronization job. The wizard will display the existing calendar synchronization jobs in which the selected servers already participate. Step 2. Calendar Synchronization Members The wizard allows you to specify mailboxes for the calendar synchronization job. In this step of the wizard, select whether you want to manually select members for calendar synchronization or import members from an existing mailbox synchronization job between the same servers. 115

118 Quest Exchange Migration Wizard Step 3. Select Mailboxes for Calendar Synchronization If you choose to manually select the mailboxes for calendar synchronization, click Add to populate the job with the mailboxes, distribution lists, or recipient containers. As with mail synchronization, Calendar folders of the following mailboxes will be synchronized with the Exchange 200x server: Mailboxes explicitly selected for synchronization. Mailboxes implicitly listed in the added distribution lists. Note that if a distribution list contains other distribution lists, mailboxes from the nested distribution lists will not be processed. Only mailboxes hosted on the source server are synchronized. Mailboxes from the containers that are selected for synchronization (both explicitly and implicitly, through other containers). If you choose to import members of the synchronization from a corresponding mailbox synchronization job, the wizard will display a list of collections of the mailbox synchronization job. Select the collections whose mailboxes should participate in the calendar synchronization. 116

119 Calendar and Free/Busy Synchronization Please note that if you later add or remove mailboxes from the mailbox synchronization collection, these changes will not be applied to the calendar synchronization. Step 4. Synchronization Options Specify the synchronization options for the job and select the Exchange 200x administrative mailbox. This mailbox will be used for the Free/Busy information synchronization. The Calendar Synchronization Agent can synchronize calendars either from active mailboxes only or two ways. The latter option should be used if delegates and resource mailboxes are intensively used in the source Exchange 5.5 organizations. The Synchronize all calendar entries, including the data previously sent to the target mailbox check box should be used if the mailboxes involved in the job already participated in calendar synchronization. The option is useful if errors occurred during the previous synchronization and it is necessary to re-copy data that has already been sent to the target server. 117

120 Quest Exchange Migration Wizard Step 5. Specify Agent Installation Path The wizard will install the Calendar Synchronization Agent on the Exchange 5.5 server. You can specify the installation path for the agent or keep the default settings. Then click Next. Step 6. Complete the Wizard and Commit Changes After the agent is installed, the wizard will inform you that you can start the calendar synchronization job. Once a new job is created, it is marked with an exclamation mark. This means that you need to update the Calendar Synchronization Agent s database before starting the job. Right-click the job in the Management Tree and click Commit Changes on the shortcut menu to update the agent s task list on the remote server. Calendar Synchronization Settings All the options that you set in the Add Calendar Synchronization Job Wizard are available in the job s properties. You can also configure the Calendar Synchronization Agent that performs all the calendar synchronization jobs for an Exchange 5.5 server. This section describes how you can manage the members of the job and the options available in both the job s and the agent s properties. Calendar Synchronization Members The Add Calendar Synchronization Job Wizard allows you to select the members of the calendar synchronization. Later you can add or remove mailboxes, distribution lists, and containers from the job. To add members to the job, do the following: With the source server, container, or the Global Address List selected in the Management Tree, take the following steps: 1. In the right-hand pane, select mailboxes, distribution lists, or containers. 2. Right-click the selection, point to Add To, and then select Calendar Synchronization Job. 118

121 Calendar and Free/Busy Synchronization 3. In the Add to Calendar Job dialog box that will appear, specify the job. Alternatively, you can drag mailboxes, distribution lists, or containers from the source server onto the job. To remove objects from calendar synchronization: 1. Select the job in the Management Tree. 2. In the right-hand pane, select the objects to be removed. 3. Right-click the selection and click Remove from Synchronization Job. After you change the members of the calendar synchronization, you need to update the Calendar Synchronization Agent's database. Right-click the job in the Management Tree and click Commit Changes on the shortcut menu to update the agent s task list. Calendar Synchronization Job Settings The options that you specify in the Add Calendar Synchronization Job Wizard are later available in the job s properties. To view or modify any of these settings, right-click the job in the Management Tree and click Properties on the shortcut menu. 119

122 Quest Exchange Migration Wizard After you modify any of the job s settings, the job is marked with an exclamation mark, which means that you need to update the Calendar Synchronization Agent database. Right-click the job in the Management Tree and click Commit Changes on the shortcut menu to update the agent s task list. Calendar Synchronization Agent Settings To view and modify the Calendar Synchronization Agent s settings, right-click the Exchange 5.5 server in the Management Tree and click Properties on the shortcut menu. The options available for the agent are described below. General If you want the agent to also synchronize Free/Busy information, select the appropriate check box on the General page of the agent s properties. Specify an administrative mailbox on the Exchange 5.5 server and how frequently the agent should synchronize the Free/Busy information for the mailboxes of the site. In order to improve the Free/Busy synchronization speed, the Calendar Synchronization Agent processes only the previously-matched Free/Busy messages. The Free/Busy matching period setting controls how frequently the agent should try to establish matching for each of the source Free/Busy messages. You can also select whether the agent should ignore the sleep period set on the Schedule page when synchronizing Free/Busy information. If the source site s Free/Busy information is synchronized to several target Administrative Groups, you might not want the Calendar Synchronization Agent to write to the log a warning if there is no corresponding mailbox in the target Administrative Group. Otherwise, the warning will be written for each source mailbox and the log will grow significantly. Like all Exchange Migration Wizard agents, the Calendar Synchronization Agent stores its configuration in a database file. You can specify how frequently the database should be compacted. The General page also allows you to select whether the Calendar Synchronization Agent should Copy permissions, and synchronize Free/Busy information. 120

123 Calendar and Free/Busy Synchronization Logging Each agent saves its logs on the server on which the agent is installed. For each agent you can specify whether the log file will be overwritten or appended during each session, and select which events will be written to the log. You can also turn on Extended logging if this is needed for troubleshooting. All types of events are logged on by default. The log files are highly useful for troubleshooting that often requires the detailed information. Therefore, it is not recommended to change the default logging settings. For more information on the log files and mail notifications, please see the Getting Statistics, Logging Information, and Reports section. 121

124 Quest Exchange Migration Wizard Scheduling Options The Calendar Synchronization Agent on each of the source servers has its own scheduling options. This lets you define separately when the agents are allowed to produce additional stress on the Exchange servers and on the network. For each agent you can specify: The hours during which each agent is allowed to run. On the agent s Schedule page of the Server Properties, click Synchronization Schedule. In the dialog box that appears, select the time frame during which the agent should perform synchronization jobs. Whether there should be a sleep period between the agent s sessions. Starting Calendar Synchronization After the directory synchronization for all the source Exchange 5.5 sites finishes its first cycle, all the target mailbox-enabled users are created. We recommend that you configure and start the calendar synchronization for all mailboxes together with the first mailbox synchronization job, so that the up-to-date Free/Busy information and calendar data is available to the user who is switched first. To start the calendar synchronization, right-click the Exchange 5.5 server or the job and start the Calendar Synchronization Agent with the corresponding shortcut menu command. 122

125 9 Pre-installing the Agents Creating an Installation Package Installing Agent Files on a Non-cluster Server Installing Agent Files on Clusters Installing the Agents 123

126 Quest Exchange Migration Wizard In large distributed networks with sites connected by slow links, agent deployment from Project Manager may take up all available bandwidth. Project Manager may appear to hang. This happens because Project Manager has to transfer the agent setup packages to the remote server before it can start installation. The shared component setup (EMWShared.exe) is about 15 MB and can take considerable time and bandwidth to be transferred. Exchange Migration Wizard includes files necessary for creating the installation package to install the Exchange Migration Wizard agents on remote Exchange servers. The package can be distributed to remote sites on any removable media and local site administrators can perform installation prior to starting the migration process. The package setup creates all necessary folders and shares on servers and copies files to the required locations. Before installing the agents, make sure that all servers in your environment meet the software requirements listed in the Software Requirements section of the Exchange Migration Wizard Quick Start Guide. Also make sure that you have installed the CDO hotfix provided by Microsoft on your Exchange servers. Refer to the Exchange Migration Wizard Quick Start Guide for more details. The following files are located in the Exchange Migration Wizard installation folder on the console computer: makepack.cmd File for creating the installation package on the console computer clnsetup.cmd Setup file for cluster servers srvsetup.cmd Setup file for non-cluster servers These batch files allow you to create an installation package that can be then distributed to remote locations without consuming network bandwidth. These files do not eliminate the need to run the agent installation procedure in Project Manager. They simply allow the copying of the setup files to the required location in advance. 124

127 Creating an Installation Package Pre-installing the Agents To create the EMW remote installation package, take the following steps: 1. Run makepack.cmd from the EMW installation folder. By default the installation package is created in the EMW Remote Setup Files subfolder of the EMW installation folder, for example, C:\Program Files\Quest Software\Exchange Migration Wizard\EMW Remote Setup Files 2. To change the path to the installation package, provide a new path as a command-line parameter as in the following example: makepack.cmd C:\RemoteSitePack The created installation package contains two folders with the necessary agent files: Agents Folder with agent setup files and Hotfixes Rcmd Folder with Quest Agent Installer files The installation package also contains two.cmd files: clnsetup.cmd Setup file for clusters srvsetup.cmd Setup file for non-cluster servers When the setup is run on remote servers, all components are copied by default to a subfolder called Aelita Exchange Migration Wizard, which is created in the Windows %systemroot%\system32 folder. This subfolder is shared as QMMEx$ServerName$. On a non-cluster server this can be changed to the location for Exchange Migration Wizard components. Once the files from this installation package are installed, start the desired migration project and work with the remote Exchange organizations using Project Manager. 125

128 Quest Exchange Migration Wizard Installing Agent Files on a Non-cluster Server To install the agent files from the installation package, take the following steps: 1. Copy all files from the installation package to a folder on the Exchange server or Directory Synchronization Agent host server. 2. Run the srvsetup.cmd. To change the default location of the EMW agent components, specify a new path as a command-line parameter as in the following example: srvsetup.cmd C:\EMW Components\ The path must end with a backslash. If the path contains spaces, it must be enclosed in quotation marks. Installing Agent Files on Clusters Prepare Cluster Servers for Agent Files Installation Before installing EMW agent components on remote cluster servers, you must perform the following steps for each Exchange organization that will take part in the migration process: 1. Run EMW Project Manager from the Start menu. 2. Register the source and target Exchange organizations in EMW if you have not done this yet. 3. For each registered Exchange organization, right-click the Exchange server and select Properties on the shortcut menu. This will open the Properties dialog box. 4. Click OK in the Properties dialog box and type the path to the EMW folder on the Exchange cluster shared drive when prompted. EMW Project Manager creates all necessary folders and shares them on the cluster. 126

129 Install the Agent Files on Cluster Servers Pre-installing the Agents To install the agent files on a cluster server, take the following steps: 1. Copy all files from the installation package to a folder on each cluster node. 2. Run the following command on each active cluster node: clnsetup.cmd VEServer where VEServer is the name of the Virtual Exchange Server running on a cluster node. 3. Run clnsetup.cmd without parameters on each passive cluster node. Installing the Agents After the setup files have been copied to the correct locations on the remote servers, run the normal agent installation procedure. When initiating agent installation using the console (by running the Agent Install Wizard or when setting up a new job), Project Manager checks whether the setup files exist on the remote server. If they do, it does not transfer them across the network; it only creates the agent services and runs the setup packages with the necessary parameters. 127

130

131 10 Customizing Exchange Migration Wizard Project Manager Scripting Exchange Migration Wizard Agents Add-Ins 129

132 Quest Exchange Migration Wizard Exchange Migration Wizard allows you to customize each of the migration tasks. The sections below describe what can be done with Project Manager scripting and synchronization agent add-ins, and how the scripts and add-ins are organized and used. Project Manager Scripting Project Manager allows you to execute any external user-defined scripts for selected Exchange 5.5 and Exchange 200x mailboxes. This capability enables you to perform a wide variety of custom migration tasks. A Project Manager script is a user-written script program that: Can be run from Project Manager interface. All scripts are shown as Project Manager Scripting menu commands. The sections below describe how the scripts are organized and managed in detail. Has access to the properties of mailboxes currently selected in Project Manager and the Exchange Migration Wizard configuration database. Project Manager allows you to add the following types of programs and start them from the Scripting menu: Executable (EXE) files Dynamic link libraries (DLL) Any program written in VBScript and Jscript provided by Microsoft, or any other Active Scripting engine from another vendor 130

133 Customizing Exchange Migration Wizard Organizing Scripts User-defined scripts are placed and organized in a tree with the Scripting menu as its root. Scripts added to Project Manager can be invoked as Scripting menu commands. To add or remove scripts and folders, or change their names and position, click Organize on the Scripting menu. As your list of scripts grows, you can keep it organized by creating folders. You may want to organize your scripts by topic. For example, you could create a folder named Active Directory for storing scripts that set Active Directory attributes. To add a new folder, right-click the folder you want to place it in and select New Folder from the shortcut menu. To fill a folder, drag script shortcuts and other folders to it. Script folders become submenus of the Scripting menu. Adding New Scripts To add a new script: 1. Create a script file. 2. On the Scripting menu, click Organize. 3. Right-click the folder you want to place the script in and select New Script from the shortcut menu. This will start the New Script Wizard. 131

134 Quest Exchange Migration Wizard 4. Follow the wizard steps to specify the script's display name (the one to be used in the Scripting menu) and description, specify or browse to the script file location, select the script language, and set other options. All scripts you add are put into the Scripting menu. The tree structure is preserved; all script folders become submenus of the menu. Running Scripts To run a script: 1. Select the objects (Exchange 5.5 or Exchange 200x mailboxes) you want the script to process. 2. Select the script from the Scripting menu. Exchange Migration Wizard Agents Add-Ins Each mailbox and directory synchronization agent s functionality can be customized and extended with add-ins. An add-in is a supplemental program that can extend the capabilities of the agents, providing additional migration options. The available options specific for each synchronization type are described below. An add-in can be written by an administrator or custom created by Exchange Migration Wizard development. 132

135 Customizing Exchange Migration Wizard Registering Add-ins Before you can use an add-in, it must first be registered in Project Manager. To register add-ins, do the following: 1. On the Tools menu of Project Manager, click Options. 2. On the Add-ins page, click Add. 3. In the Add New Add-In dialog box that appears, specify a unique alias for the add-in. 4. Browse to the library that contains the add-in. 5. If the library should be registered on the installation server, the Requires registering on the installation server check box must be selected. Please refer to the add-in s documentation for details. 6. Specify the ProgID and the initialization string, as described in the add-in s documentation. 7. Add any Required Components for the add-in if needed. 8. Click OK. 9. Repeat steps 2 8 to register other add-ins. 10. Back in the Options dialog box, click OK. After that, Project Manager will create a package for each registered add-in and you will be able to install the add-ins on the remote servers where the agents are working. To check whether the packages were created, browse to the %Program Files%\Quest Software\Exchange Migration Wizard\CABS folder. The following files should be present in the folder: setup.ini tasks.ini a separate.cab file for each of the registered add-ins Install Add-Ins Wizard After the add-ins are registered in Exchange Migration Wizard and the packages for them are created, the registered add-ins can be used with the agents. The add-ins are installed on the remote servers with help of the Install Add-Ins Wizard. To start the wizard, right-click the Exchange Migration Project node in the Management Tree and click Install Add-Ins. In the wizard specify the agents that will use the add-ins, the remote servers, and which of the registered add-ins should be installed. 133

136 Quest Exchange Migration Wizard The add-ins will be installed in the ADDINS subfolder of the corresponding agent s folder on the server. The following sections describe how to configure the directory and mailbox synchronization agents to use the installed add-ins. An add-in can be installed only after the corresponding agent has been installed on the server. Directory Synchronization Add-Ins Directory synchronization add-ins can be used to perform the following tasks: Customize attribute mapping. The custom attribute mapping add-ins are used for each object pair during object synchronization. They are called after the Directory Synchronization Agent has completed the default attribute mapping procedure for an object pair, but before the objects are saved. The agent gives an add-in the sets of attributes representing the source and target objects. The add-in returns the objects modified according to the custom attribute mapping rules. After that, the object pairs are synchronized according to the attribute mapping rules returned by the add-in. Customize object matching. The custom object matching add-ins are used for each unmatched object before the agent searches the opposite directory. They are called after the LDAP filter for searching the directory is created by the Directory Synchronization Agent. The agent gives an add-in the default sets of attributes representing the source and target objects. The add-in returns the LDAP filter string that either can be merged with the default search filter (using OR or AND logical operator) or can be substituted for the default filter. After that, the object pairs are matched according to the object matching rules returned by the add-in. To find out what rules the Directory Synchronization Agent uses to match source and target objects by default, refer to the Exchange Migration Wizard - Directory Object Matching document. 134 Customize object creation. The custom object creation add-ins are used before the corresponding objects are created in the directory. The agent gives an add-in the default sets of attributes representing the source and target objects. The add-in returns the set of the attributes with the values that should be applied to the newlycreated objects. After that, the agent creates the objects using the set of attributes returned by the add-in.

137 Customizing Exchange Migration Wizard You can add the add-ins to an existing job: 1. Right-click the job in the Management Tree and click Properties. 2. Go to the Add-Ins page of the Directory Synchronization Job Properties dialog box. 3. Click Add to add the required add-ins. The add-ins will be added to the job, whether or not they are already installed on the server. To install the add-ins, run the Install Add-Ins Wizard as described above. After you start the Directory Synchronization Agent, it will work using the installed add-ins. Default Object Matching Rules All Exchange Migration Wizard components use the default rules for identifying matching objects. Each agent first matches objects by the target object s GUID and the source object s custom attribute specified to store the target object's GUID (Custom Attribute 13, by default). This attribute is populated by the Directory Synchronization Agent during directory synchronization. To find out what rules the Directory Synchronization Agent uses to match source and target objects by default, refer to the Exchange Migration Wizard - Directory Object Matching document. Mailbox Synchronization Add-Ins Each mailbox synchronization agent s functionality can be customized and extended with add-ins. A mailbox synchronization add-in is a supplemental program that can extend the capabilities of the mail agents, providing additional migration options such as: Criteria for choosing folders and messages for copying Rules for moving mail Working with mailbox collections Setting the schedule for server management An add-in can be written by an administrator or custom created by Exchange Migration Wizard development. 135

138 Quest Exchange Migration Wizard To make a mailbox synchronization agent use a registered add-in, do the following: 1. Right-click the server in the Management Tree and click Properties. 2. Open the Add-Ins page under the node of the agent that should use the add-in. 3. Click Add and select the add-in that should be used by the agent. The add-ins will be added to the agent s configuration, whether or not they are already installed on the server. To install the add-ins, run the Install Add-Ins Wizard as described above. Then you can start the mail agents and they will work using the installed add-ins. 136

139 11 General and Server Options Options Dialog Box Server Options 137

140 Quest Exchange Migration Wizard Most of the options available in Exchange Migration Wizard are applicable to a particular synchronization job or agent. Those options are covered in the corresponding chapters of this document. There are also more general settings that affect either all the agents installed on a server or the entire migration project. This section describes all the options that are not covered elsewhere in this document. Options Dialog Box The settings that are applied to the entire Exchange migration project are all gathered in the Exchange Migration Wizard Options dialog box. To open this dialog box, in Project Manager click Options on the Tools menu. Each page of the dialog box is described below. Directory Synchronization Settings Exchange Migration Wizard uses four custom attributes to store the directory synchronization information that is then used by other components. The Directory Synchronization Settings page allows you to set which attributes should be used to store this information. The usage of each of these attributes is discussed in the Object Attributes Used For Directory Synchronization section of the Directory Synchronization chapter. License Server Because Exchange Migration Wizard uses a distributed architecture, the agents obtain all license information from a single license server that you can specify on this page. By default a server on which Project Manager is installed first is used as the license server. By default, each agent connects to the license server using the credentials under which the agent is running. However, you can specify alternate credentials the agents will use to connect to the license server. Note that the Mail Target Agent administrative account must be a member of the local Administrators group on the license server in case this server is located in another trusted forest. 138

141 General and Server Options Please refer to the Licensing section of the Exchange Migration Wizard - Quick Start Guide for further details on how licensing works in Exchange Migration Wizard. Add-Ins An add-in is a supplemental program that can extend the capabilities of the agents, providing additional migration options. This page allows you to add and register the add-ins for the agents. Please, refer to the Exchange Migration Wizard Agents Add-Ins section for more details. Switch Notifications The Mail Source Agent and Mail Target Agent can send a notification message to each user whose mailbox has been switched. Different messages are sent to the user s old Exchange 5.5 and new Exchange 200x mailboxes. You can compose templates for both messages or use the default templates. You must also specify the SMTP address from which the message will be sent, otherwise the notifications will not be sent, even if the Send switch notification to the target mailbox and the Send switch notification to the source mailbox checkboxes are selected. The Address and Subject fields of the source and target switch notification options may not contain non-english character set symbols. 139

142 Quest Exchange Migration Wizard The agent can also insert a server name and a new target mailbox s distinguished name into the message. Security The accounts under which the agents run should have DCOM Access and Launch permissions on each Windows NT 4.0 running computer on which the Exchange Migration Wizard agents are installed. By default, the wizard adds the DCOM privileges to the local server's Administrators group the first time you start an agent on the Windows NT 4.0 server. If you do not want Exchange Migration Wizard to set these privileges automatically, you can clear the Automatically grant administrative DCOM permissions to the agent service accounts on the servers running Microsoft Windows NT 4.0 check box on the Security page of the Options dialog box. In this case you will have to manually set the DCOM privileges for each agent s account on every Windows NT 4.0 running server, as described in the Exchange Migration Wizard - Quick Start Guide. 140

143 General and Server Options Advanced Agents Management If your company collaboration requires using any languages other than English, Exchange Migration Wizard supports localized mailbox and public folder names, localized message subjects, etc. This page allows you select whether the wizard should use the Unicode support. Select the Unicode support check box to make agents recognize localized folder names, message subjects, etc. If this option is selected, the agents will use Unicode when saving mail or public folders data in the service, which will increase the size of the files transferred across the network. This option is selected by default. The target Exchange 2003 servers and source Exchange 5.5 servers must support all the locales used in the source Exchange 5.5 organization. To verify this, open the corresponding server properties in Exchange System Manager and in Microsoft Exchange Administrator and check the list on the Locales tab. Refer to the Exchange Migration Wizard - Localization Support document for more details. The agents can also produce logs in Unicode format. In this case the folder names mentioned in the log will be written correctly using national symbols, but the log file size will increase up to double the size of its English version. To make the agents produce logs in Unicode format, select the Loging in Unicode format option. These settings do not affect the Directory Synchronization Agent. Unicode support and logging are always enabled for the Directory Synchronization Agent. 141

144 Quest Exchange Migration Wizard Additional Parameters for Agent s Configuration Files In some cases it might be necessary to add a new parameter to the configuration file of every agent. For example, when an update is released, the updated agents might require certain parameters to be in the config.ini file. The Additional Parameters page allows you to configure the new parameters for all the agents on your network without touching every single server. If a parameter name is similar to the name of an existing parameter (available in the corresponding server options), the parameter value you specify on this page will be applied to all the agents. Collection Analyzing Utility Please, refer to the Checking Mailbox Synchronization Status section for more details on the options for the Collection Analyzing Utility available on this page. Statistics Collection Agent Settings The Statistics Collection Agent (SCA) connects to all agents, retrieves data from their databases, and puts the consolidated data into the SQL database to which Exchange Migration Wizard is connected. This information is then used by Quest Reporting Console to create comprehensive reports on the migration status and configuration. The SCA options are described in the Getting Statistics, Notifications, and Reports section of the document. Server Options The settings that are applied to every agent installed on a particular server can be viewed and modified in the source and target server properties. To open a server s properties, right-click the server in the Management Tree and click Properties on the shortcut menu. 142

145 General and Server Options Connection The LDAP port and the accounts used by the agents to connect to each source and target servers can be changed on the Connection page of the server s properties. Associated Domain Controller Since Exchange 200x uses Active Directory to store the directory information, Exchange Migration Wizard uses domain controllers to enumerate Exchange 200x objects. Exchange Migration Wizard associates one domain controller with each Exchange 200x server when you first register the target organization in Exchange Migration Wizard. In some cases you may need to change a domain controller associated with the server, for example if a domain controller is temporary unavailable. The Associated Domain Controller page of the Target Server Properties dialog box allows you to change this as well as the account that is used to work with Active Directory. Select the Add Exchange topology only option if you want to refresh only information about the target Exchange organization topology, including administrative groups, storage groups, stores, and servers. 143

146 Quest Exchange Migration Wizard Deselect the Add Exchange topology only option and select the Use Global Catalog for enumeration option if you want to make full refresh including the Exchange topology and mailboxes. Note that full refresh is a timeconsuming operation, especially in large organizations, so it is recommended to use a quick refresh when you need to update only the Exchange topology information. It is recommended that the associated domain controller has a copy of Active Directory Global Catalog. This is required to apply the mailbox and public folder client permissions granted to users migrated to other Active Directory domains. Resource Usage You can optionally set a specific folder to be used by EMW agents. The folder should be specified as a local path on the server. By default, the Aelita Exchange Migration Wizard subfolder is created in the ADMIN$\system32 Windows system folder. This subfolder is then shared as QMMEx$ServerName$. If you want to change the agent's installation folder, you should specify the full local path to the existing folder on the server. For each server you can specify the amount of disk space (either in megabytes or as a percentage of the total available drive space) that should not be used by the agents working on the server. You can also specify the memory limit that should not be exceeded by each agent working on a server. We do not recommend changing this parameter unless your environment really requires it. Increasing the memory limit might be required if agent performance is slow and you see the following trace message in the log: The agent s system memory limit Kb has been exceeded. Agent will be terminated. Exceeding the memory limit affects agent performance, so you might want to increase the memory limit if you have enough resources. Decrease the memory limit if the server is unstable and low on memory. Be very careful with this option. Setting it to a lower value will affect the performance of all the agents. If memory limit is reduced, we recommend that the PST size limit also be set to a lower value, since this will reduce the impact on the mailbox and public folder synchronization agents performance. 144

147 General and Server Options Also, the agents might not even be able to start if the limit is too low. The lowest acceptable value depends on the server. An administrator should carefully test this in the environment to find the value that: Will not affect the agents performance greatly Will not load the server s memory too much Associated Servers The Target Servers page of a source server s Properties dialog provides a list of the Exchange 200x servers that participate in the mailbox synchronization jobs together with this server. The Source Servers page of a target server s Properties dialog provides a list of the Exchange 5.5 servers that participate in the mailbox synchronization jobs together with this server. 145

148

149 12 Getting Statistics, Logging Information, and Reports Logging, Statistics, and Notifications Exchange Migration Wizard Reports 147

150 Quest Exchange Migration Wizard Logging, Statistics, and Notifications Agent Logs When an agent is started, it creates a log file. The agents save their logs on the server on which they are installed. By default, the logs are stored in a subfolder called Aelita Exchange Migration Wizard, which is created in the Windows %systemroot%\system32 folder for every agent. This subfolder is shared as QMMEx$ServerName$. Log files written by the mail, calendar, and public folder synchronization agents can be accessed with the help of the Project Manager Management Tree, in either of the following ways: Right-click the server name (under Source Organizations or Target Organizations) where the agent is installed, point to Log, and select the agent s name from the shortcut menu. Right-click the synchronization job, point to Log, point to Source or Target, and select the agent s name from the shortcut menu. To view the log file of the Directory Synchronization Agent, right-click the server name under Directory Synchronization, point to Log, and select Directory Synchronization Agent from the shortcut menu. The log file of the selected agent will be opened in the window of the text editor set in your system as the default. Normally, you do not have to view the agents logs, as they contain internal technical information. However, the logs are useful for troubleshooting if any errors occur. For each agent, you can select whether the log file should be overwritten or appended during each session, and choose which events (by default, all) are written to the log. It is not recommended to deselect any of the event types because this can make the troubleshooting more difficult. The Mail Source and Mail Target Agents can send the statistics to an administrator by (see the Mail Notifications section below). Online Statistics Online statistics shows data collected by the Directory Synchronization Agent and Mail Synchronization Agents during their sessions. 148

151 Getting Statistics, Logging Information, and Reports Every agent stores its statistics in the local database. Exchange Migration Wizard takes the information from these databases and provides statistics for directory synchronization jobs and for mailboxes. The statistics are displayed in the Statistics panel. To switch the panel, click Statistics Panel on the View menu or click the corresponding toolbar button. To view the statistics for a directory synchronization job, browse to the server name under Directory Synchronization in the Management Tree. The Statistics panel shows the following: Status of the Directory Synchronization Agent Log Info: the number of events that were written to the log by the agent For each job performed by the agent, the Statistics panel shows: The number of changed, created and synchronized objects for the source Exchange server. (Synchronized objects are those that were modified and the modifications were moved to the corresponding target objects.) The number of changed, created, synchronized, and mail-enabled objects for the target Exchange server. (Synchronized objects are those that were modified and the modifications were moved to the corresponding source objects.) 149

152 Quest Exchange Migration Wizard To view the statistics for a mailbox, browse to the source server or the mailbox collection to which it belongs in the Management Tree and select the mailbox. The statistics panel will show the following: The agent s session ID Start time and end time of the agent s session End time of compression The number of messages and folders scanned, copied, added, synchronized, and not synchronized during the agent s session The number of events that were written to the log while the agent was processing this mailbox The agent s status (i.e., last action performed by the agent and the performance date) Whether the mailbox is switched Exchange Migration Wizard reports generated by Reporting Console are based on the online statistical data. For more information about the reports, please refer to the Exchange Migration Wizard Reports section. Mail Notifications The Mail Source Agent, Mail Target Agent, Public Folders Source Agent and Public Folder Target Agent can send notifications to an administrator, providing such information as: Statistics on the migration process Agent s log files with information on the current migration status, errors, and warnings Warnings if the migration process falls behind the specified schedule (start and end dates can be associated with each mailbox collection) With the help of the source server and target server Properties dialog boxes, you can select which events should be written to these logs and how often the notifications are sent. The addresses you specify will also be used to notify you if a mailbox or public folders collection is running behind the specified schedule. Note that you will not receive such notifications if you do not specify an address for the mail synchronization agents. For more information on the agents settings, see the Agents Logging Options section below. 150

153 Agents Logging Options Getting Statistics, Logging Information, and Reports The logging options of the Mail Source Agent, Mail Target Agent, Public Folders Source Agent and Public Folder Target Agent, and Calendar Synchronization Agent can be viewed with the help of the source server and target server Properties dialog boxes. To open one of these dialog boxes, right-click the appropriate server name and select Properties from the shortcut menu. To view or modify the agent s logging options, click the agent s name in the dialog box left pane and select the Logging page. The logging options dialogs for Mail and Public Folder Agents display the following options: Logging options: Log events Shows which log events should be written to the agent s log file. By default all log events are selected. Append log Displays whether the agent s log file should be appended or overwritten during each agent s session. By default the log file is to be appended. Archive log file larger than (MB) Displays the maximum log file size. If the file size exceeds the specified value, it will be archived and put into the..\qmmex$servername$\mail Source Agent\LOGS\ folder. By default the maximum log file size is 10 MB. 151

154 Quest Exchange Migration Wizard Statistics options: Specify whether the statistics should not be written to the agent s database, should not be cleared, or should be kept for the specified period of time. By default the agent s statistics are not cleared. Notification options: Send statistics by Shows whether the collected statistics will be sent by . If they will, specify the address to which the notification will be sent and the mailbox from which it will be sent. By default the statistics are not sent by . Notification period Shows whether the notification will be sent at the end of each agent s session or at the specified interval (in days). The logging options dialogs for the Calendar Synchronization Agent and Transmission Agent allow you to view and modify the types of log events that are written to the log files, to select whether the log file should be appended or overwritten during each agent s session, and to specify the maximum log file size: The logging options for the directory synchronization job can be defined while setting up a job. The Logging page of the Add Directory Synchronization Job Wizard will help you select which log events should be written to the log file for each directory synchronization job. By default all events are selected. For more information, please refer to the Directory Synchronization section above. The logging options for the Directory Synchronization Agent can be set on the Options page of the Directory Synchronization Agent Properties dialog box. To open the dialog box, right-click the name of the server under Directory Synchronization and select Properties from the shortcut menu. 152

155 Getting Statistics, Logging Information, and Reports The logging options dialog for the Directory Synchronization Agent allows you to select whether the log file should be appended or overwritten during each agent s session and to specify the maximum log file size. By default the Directory Synchronization Agent s log file size is 0, which means that the log file is not limited and will never be archived no matter how large it is. After the agent is stopped and started again, new data will be added to the existing log file, if its maximum size is 0 and the file is to be appended. If the log file is to be overwritten, the old file data will be deleted and the new data will be written into this log file. 153

156 Quest Exchange Migration Wizard Exchange Migration Wizard Reports To give you a comprehensive view of the migration configuration, progress, and statistics, Exchange Migration Wizard includes Reporting Console, which retrieves data from the SQL database. Because each agent stores its statistics in its own database, Exchange Migration Wizard also contains the Quest Statistics Collection Agent, which connects to all agents, retrieves information from their database files, and puts the consolidated data into the SQL database that Exchange Migration Wizard is connected to. The Reporting Console takes the migration configuration data and the data put to the database by the Statistics Collection Agent and compiles reports on Exchange Migration Wizard configuration, statistics, and the migration process. 154

157 Statistics Collection Agent Getting Statistics, Logging Information, and Reports The Statistics Collection Agent is installed as an optional component on the computer on which you install Exchange Migration Wizard and is run as a service. The Installation Wizard will prompt you for the account under which the agent service will run on the server. Note that the account should have all the necessary permissions. For more information about permissions, please see the Exchange Migration Wizard - Quick Start Guide. If you don t install this component, you will still be able to view individual logs from agents, as well as their statistics in Exchange Migration Wizard. However, you will not be able to get the comprehensive Reporting Console reports, including data from all computers participating in the migration. The statistics collection agent should be explicitly started with the help of the Options dialog box (General page). Statistics Collection Agent Options Statistics Collection Agent options are set in the Options dialog box. To open the dialog box, click Options on the Tools menu in Exchange Migration Wizard Project Manager. The General page allows you to modify agent s schedule, which determines the hours when the agent is allowed to run. On this page you also can specify whether the Statistics Collection Agent continuously keeps synchronizing the SQL database with the agents databases, or checks for new data at the specified synchronization interval. The agent is started and stopped from this page. 155