8.7. Target Exchange 2010 Environment Preparation

Transcription

1 8.7 Target Exchange 2010 Environment Preparation

2 2011 Quest Software, Inc. ALL RIGHTS RESERVED. This document contains proprietary information protected by copyright. The software described in this document 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. If you have any questions regarding your potential use of this material, contact: Quest Software World Headquarters LEGAL Dept 5 Polaris Way Aliso Viejo, CA legal@quest.com Refer to our website for regional and international office information. TRADEMARKS Quest, Quest Software, the Quest Software logo are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. For a complete list of Quest Software's trademarks, please see Other trademarks and registered trademarks are property of their respective owners. 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. Quest Migration Manager for Exchange Updated February 18, 2011 Software version 8.7

3 CONTENTS About This Guide... 3 Overview... 3 Conventions... 3 Introduction... 4 Before You Begin... 5 Preparation Overview... 5 Step 1: Checking the System Requirements... 5 Step 2: Setting Up Accounts and Required Permissions... 5 Step 3: Preparing the Target Exchange Environment for Exchange Migration... 6 Step 4: Setting Up Connection with the Source Exchange Organization Using SMTP Connectors... 6 Preparation Checklist... 6 Prerequisites... 7 Target Active Directory Synchronization Account... 7 Target Exchange Account... 7 Target Active Directory Account... 8 Target Agent Host Account... 8 Step 1: Checking System Requirements... 9 Step 2: Setting Up Accounts and Required Permissions Step 2.1: Setting Up the Target Active Directory Synchronization Account Step 2.2: Setting Up the Target Exchange Account Step 2.2.1: Changing the Default Target Exchange Account Step 2.2.2: Granting Read Access to the Target Active Directory Domain Step 2.2.3: Granting Membership in Server Local Administrators Group Step 2.2.4: Granting Full Control on Organizational Unit Step Granting Full Control on the Microsoft Exchange System Objects Organizational Unit Step 2.2.6: Granting Permission to Make Public Folders Mail-Enabled Step 2.2.7: Granting Full Control on Exchange 2010 Mailboxes Step 2.2.8: Granting Membership in Recipient Management Group Step 2.3: Setting Up the Target Active Directory Account Step 2.3.1: Changing the Default Target Active Directory Account Step 2.3.2: Granting Read Access to Active Directory Domain Step 2.3.3: Granting Full Control on Organizational Unit Step 2.3.4: Granting Read Permission for the Microsoft Exchange Container Step 2.4: Setting Up Target Agent Host Account Step 2.4.1: Changing the Default Target Agent Host Account Step 2.4.2: Granting Membership in the Local Administrators Group on the License Server Step 2.5: Setting Up Single Administrative Account for Exchange Migration (Optional) Step 2.5.1: Creating the Single Administrative Account Step 2.5.2: Granting Access to Active Directory Step 2.5.3: Granting Full Control on Exchange Organization i

4 Step 2.5.4: Granting Full Control on Exchange 2010 Mailboxes Step 2.5.5: Granting Access to SQL Server Step 2.5.6: Granting Read Permission for the Microsoft Exchange Container Step 2.5.7: Granting Local Administrative Rights Step 2.5.8: Changing the Default Active Directory, Exchange and Agent Host Account Step 3: Preparing the Target Exchange Environment for Exchange Migration Step 3.1: Backing Up Exchange Transaction Log File Cleanup Step 3.2: Creating Aelita EMW Recycle Bin Public Folder Step 3.3: Creating Administrator Mailboxes for Public Folder and Free/Busy Synchronization Step 3.4: Creating Administrator Mailboxes for Mailbox and Calendar Synchronization (Optional) Step 3.5: Creating Custom Throttling Policies Step 3.6: Installing the Microsoft Exchange Server MAPI Client and Collaboration Data Objects Step 3.7: Disable RPC Encryption on Target Exchange 2010 Servers (Optional) Step 4: Setting Up Connection with the Source Exchange Organization Using SMTP Connectors Step 4.1: Setting up Target Exchange 2010 Organization for Internet Mail Flow between Target and Source Exchange Organizations Option A: Establishing Internet Mail Flow Directly Through a Hub Transport Server Option B: Establishing Internet Mail Flow through a Subscribed Edge Transport Server Step 4.2: Configuring Target DNS Server for Mail Forwarding Step 4.3: Testing the SMTP Connectors (Optional) Summary Appendix A: Exchange 2003 to Exchange 2010 Migration Restrictions About Quest Software, Inc Contacting Quest Software Contacting Quest Support Third Party Contributions Boost 1.0 License Agreement Loki License Agreement Loki License Agreement ZLib License Agreement ii

5 Target Exchange 2010 Preparation About This Guide Overview This document is prepared to assist you in setting up your Exchange 2010 organization and its environment for being target organization in Exchange migration process conducted by Migration Manager for Exchange. It is intended for network administrators, consultants, analysts, and any other IT professionals using Migration Manager for Exchange. 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 crossreferences. ELEMENT Select Bolded text Italic text Bold Italic text Blue text CONVENTION 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. 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. 3

6 Quest Migration Manager for Exchange 8.7 Introduction Follow the steps in this document to prepare your Exchange 2010 organization and its environment for being the target organization in the Exchange migration process conducted by Migration Manager for Exchange. For more information about Migration Manager for Exchange refer to the Quest Migration Manager for Exchange Overview document. On some of steps you may need to coordinate the setup process with the administrator of the source Exchange organization. 4

7 Target Exchange 2010 Preparation Before You Begin Preparation Overview This section provides a short overview of the main steps that should be performed to set up your target Exchange 2010 organization and its environment for migration using Migration Manager for Exchange. These steps are described in detail below. Setting up the target Exchange 2010 organization consists of four main steps: Step 1: Checking the System Requirements On this step make sure that your environment meets the minimal system requirements for Migration Manager for Exchange agents. Step 2: Setting Up Accounts and Required Permissions On the second step you should set up the accounts and required permissions for Exchange migration. There are four main types of accounts used by Migration Manager for Exchange agents: Target Active Directory Synchronization Account This account is used by: a) The Directory Synchronization Agent (DSA) to access the target Active Directory domain b) The Mail Source Agent (MSA) to perform mailbox switch Target Exchange Account This account is used by Migration Manager for Exchange agents installed on agent host to access the target Exchange server. Target Active Directory Account This account is used by Migration Manager for Exchange agents to access the target domain. Target Agent Host Account This account is used to install and run the Migration Manager for Exchange agents on agent host and to access the license server. You can simplify the setup by using a single administrative account with all Migration Manager for Exchange agents. Such account should have permissions that are required for all the agents on every server that is involved in the migration, both in the source and in the target organization. 5

8 Quest Migration Manager for Exchange 8.7 Step 3: Preparing the Target Exchange Environment for Exchange Migration On the third step you should perform common environment preparations: Back up Exchange. Create the Aelita EMW Recycle Bin public folder. Create administrator mailboxes for public folder and free/busy synchronization Create administrator mailboxes for mailbox and calendar synchronization (optional) Create custom throttling policies Install Microsoft Exchange Server MAPI Client and Collaboration Data Objects version or later. Disable RPC Encryption on target Exchange 2010 servers (optional). Step 4: Setting Up Connection with the Source Exchange Organization Using SMTP Connectors On the final fourth step you should set up the connection with the source Exchange organization using SMTP connectors. This task consists of three subtasks given below: 1. Setting up the target Exchange 2010 organization for Internet mail flow between target and source Exchange organizations 2. Configuring target DNS server for mail forwarding 3. Testing the SMTP connectors (optional) Preparation Checklist This checklist will help you set up your target Exchange 2010 organization and its environment properly. Make sure you have done all the steps below before completing the preparation. CHECK STEP REFER TO Check the system requirements Step 1 Set up the Target Active Directory Synchronization Account Step 2.1 Set up the Target Exchange Account Step 2.2 Set up the Target Active Directory Account Step 2.3 Set up the Target Agent Host Account Step 2.4 Set up a single administrative account (optional) Step 2.5 Back up Exchange Step 3.1 Create the Aelita EMW Recycle Bin public folder Step 3.2 6

9 Target Exchange 2010 Preparation CHECK STEP REFER TO Create administrator mailboxes for public folder and free/busy synchronization Create administrator mailboxes for mailbox and calendar synchronization (optional) Step 3.3 Step 3.4 Create custom throttling policies Step 3.5 Install Microsoft Exchange Server MAPI Client and Collaboration Data Objects version or later Disable RPC Encryption on target Exchange 2010 servers (optional) Set up the target Exchange 2010 organization for Internet mail flow between target and source Exchange organizations Step 3.6 Step 3.7 Step 4.1 Configure the target DNS server for mail forwarding Step 4.2 Test the SMTP connectors (optional) Step 4.3 Prerequisites Before starting the preparation of the target Exchange 2010 organization and its environment, make sure that you have the privileges to grant all of the following permissions to accounts. The list of permissions given below contains all required permissions for the accounts. However some of the permissions can be emulated by their equivalents. For more information, see the corresponding steps for each account. Target Active Directory Synchronization Account Membership in the Administrators or Domain Admins group of the target domain. Target Exchange Account Read access to the target domain. Membership in the local Administrators group on all target Exchange servers involved in the migration. If a server is a domain controller, the account should be added to the domain local Administrators group of the domain. Full Control permission on the organizational units (OUs) (and their child objects) where the target synchronized objects are located. Full Control permission on the Microsoft Exchange System Objects organizational unit in all domains in which target Exchange 2010 servers involved in public folder synchronization reside. Full Control permission on target Exchange 2010 organization 7

10 Quest Migration Manager for Exchange 8.7 Membership in the Public Folder Management group. Permissions to log on to every mailbox involved in the migration. Membership in the Recipient Management group. Target Active Directory Account Read access to the target domain. Full Control permission on the organizational units (OUs) (and their child objects) where the target synchronized objects are located. Read permission for the Microsoft Exchange container in the target Active Directory. Target Agent Host Account Membership in the local Administrators group on the license server (unless alternative credentials are used for the license server). If server is located in another trusted forest, the account should have local Administrator permissions on the license server. Local Administrator permissions on the agent host server. 8

11 Target Exchange 2010 Preparation Step 1: Checking System Requirements Any computer that does not meet the requirements should be upgraded before installing Migration Manager for Exchange components. Migration Manager for Exchange uses the following Exchange-specific agents involved in the migration process: Public Folder Source Agent Public Folder Target Agent Mail Target Agent Calendar Synchronization Agent Free/Busy Synchronization Agent Transmission Agent Agents work on agent host servers. Agent host can be: 1. An Exchange server itself, which is the default configuration. After you enumerate an Exchange organization all Exchange servers are registered as agent hosts for themselves. 2. Another Exchange server from the same Exchange organization. 3. A stand-alone server. It can be located in another forest or workgroup. Requirements from the following table apply to Exchange 2010 servers acting as agent hosts: Platform Operating system Additional software One of the following: Intel EM64T AMD 64 One of the following: Microsoft Windows Server 2008 (x64 edition) Microsoft Windows Server 2008 R2 Microsoft Exchange Server MAPI Client and Collaboration Data Objects version or later 9

12 Quest Migration Manager for Exchange 8.7 For detailed information about system requirements, see the Exchange Migration Agents section of the System Requirements and Access Rights document. Target Exchange 2010 Organization Considerations The mailbox database containing the administrator mailbox (the System Mailbox used by default or custom administrator mailbox) should be mounted for each target Exchange 2010 server involved in the migration. The Migration Manager for Exchange console shows only those servers from target Exchange 2010 organization that host the Mailbox role. This is required because only servers with actual data are considered for migration. Public folder stores are no longer mandatory for Exchange 2010 organizations. Some restrictions may apply in Exchange 2003 organization to Exchange 2010 organization migration scenario. For information, see Appendix A. 10

13 Target Exchange 2010 Preparation Step 2: Setting Up Accounts and Required Permissions This section describes requirements for accounts working with the target Exchange servers. Migration Manager for Exchange allows you to use different administrative accounts for different purposes. Exchange data is migrated by Migration Manager for Exchange agents, which use the following accounts: Target Active Directory Synchronization Account This account is used by: a) The Directory Synchronization Agent (DSA) to access the target Active Directory domain b) The Mail Source Agent (MSA) to perform mailbox switch Target Exchange Account This account is used by Migration Manager for Exchange agents installed on agent host to access the target Exchange server. Target Active Directory Account This account is used by Migration Manager for Exchange agents to access the target domain. Target Agent Host Account This account is used to install and run the Migration Manager for Exchange agents on agent host and to access the license server. If you want to have a single administrative account for Exchange migration, you should skip steps and perform Step 2.5: Setting Up the Single Administrative Account for Exchange Migration. Step 2.1: Setting Up the Target Active Directory Synchronization Account This section describes how to set the required permissions for the Target Active Directory Synchronization Account. This account is used by: The Directory Synchronization Agent (DSA) to access the target Active Directory domain The Mail Source Agent (MSA) to perform mailbox switch 11

14 Quest Migration Manager for Exchange 8.7 The required privilege level for the Target Active Directory Synchronization Account is membership in the Administrators or Domain Admins group of the target domain. If for some reason you cannot grant such privileges to the Target Active Directory Synchronization Account then see the SOL11575 article on the Quest Support website for the list of minimal required permissions. To grant the necessary permission to the Target Active Directory Synchronization Account, perform the following: 1. On the target domain controller in the Active Directory Users and Computers snap-in, click Builtin, then in the right pane right-click Administrators and click Properties. 2. Go to the Members tab, click Add and select the Target Active Directory Synchronization Account (in our example, QMM_Trg_DSA). 3. Close the dialog boxes by clicking OK. 12

15 Target Exchange 2010 Preparation Step 2.2: Setting Up the Target Exchange Account This section describes how to set the required permissions for the Target Exchange Account used by Migration Manager for Exchange agents. This account is used for the following: Working with target Exchange mailboxes and public folders (used by the Mail Target Agent, Public Folder Source Agent, and Public Folder Target Agent) Making the newly-created public folders mail-enabled (used by the public folder agents only: Public Folder Source Agent and Public Folder Target Agent) Synchronizing Calendar information (used by the Calendar Synchronization Agent) Synchronizing free/busy data (optional) (used by the Free/Busy Synchronization Agent) Moving mailboxes The required privileges for the Target Exchange Account are as follows: Read access to the target domain. Membership in the local Administrators group on all target Exchange servers involved in the migration. If a server is a domain controller, the account should be added to the domain local Administrators group of the domain. Full Control permission on the organizational units (OUs) (and their child objects) where the target synchronized objects are located. Full Control permission on the Microsoft Exchange System Objects organizational unit in all domains in which target Exchange 2010 servers involved in public folder synchronization reside. Full Control permission on target Exchange 2010 organization Membership in the Public Folder Management group. Permissions to log on to every mailbox involved in the migration. Membership in the Recipient Management group. To set up the Target Exchange Account, perform the steps below. Note that the steps are given only as an example of a possible Target Exchange Account setup. Step 2.2.1: Changing the Default Target Exchange Account The default Target Exchange Account (initially displayed on the Connection page of the Exchange server Properties) is set when you add the target organization to the migration project (see the Registering Source and Target Organizations section of the Migration Manager for Exchange User Guide for details). If necessary, you can change the default Target Exchange Account by clicking Modify on the General Connection page in the properties of the corresponding target server in the Migration Manager for Exchange Console. 13

16 Quest Migration Manager for Exchange 8.7 To go on using the default Target Exchange Account for Exchange migration, grant the permissions required for Exchange migration to this account (as described on the steps below). Step 2.2.2: Granting Read Access to the Target Active Directory Domain Target Exchange Account should have Read access to the target Active Directory. To grant this permission to the Target Exchange Account, complete the following steps: 1. In the Active Directory Users and Computers snap-in, right-click the domain name (in our example, targetdomain), and then click Properties. 2. On the Security tab, click Add and select the Target Exchange Account (in our example, QMM_Trg_Ex). 3. Select the Target Exchange Account, and then check the Allow box for the Read permission in the Permissions box. 4. Click the Advanced button. In the Advanced Security Settings dialog box, select the account you specified on step 2, and click Edit. 5. In the Permission Entry dialog box, select This object and all descendant (child) objects from the Apply to drop-down list. 6. Close the dialog boxes by clicking OK. 14

17 Target Exchange 2010 Preparation Step 2.2.3: Granting Membership in Server Local Administrators Group The Target Exchange Account used by Migration Manager for Exchange agents should be a member of the local Administrators group on each target Exchange server involved in the migration. If the Exchange server is a domain controller, the account should be added to the domain local Administrators group of the domain. To add the Target Exchange Account to the local Administrators group on each target Exchange server involved in the migration, perform the following: 1. Open the Computer Management snap-in (Click Start Run, enter compmgmt.msc and then click OK). 2. In the left pane click System Tools Local Users and Groups Groups. 3. Right-click the Administrators group and click Add to Group. 4. Click Add and select the Target Exchange Account (in our example, QMM_Trg_Ex). 5. Close the dialog boxes by clicking OK. 15

18 Quest Migration Manager for Exchange 8.7 Step 2.2.4: Granting Full Control on Organizational Unit To work with the target Active Directory objects, the Target Exchange Account needs the Full Control permission on the organizational units and their child objects that contain the objects to be synchronized. This permission should be set on the domain controller where the objects you need to synchronize are located. To grant the required permissions to the account, perform the following steps: 1. In the Active Directory Users and Computers snap-in, right-click the OU where the objects are located, and click Properties. 2. On the Security tab, click Add, and select the Target Exchange Account (in our example, QMM_Trg_Ex). If there is no Security tab, you should select View Advanced Features in the Active Directory Users and Computers snap-in. 3. Select the account name, and then enable the Allow option for the Full Control permission in the Permissions box. 4. Click the Advanced button. In the Advanced Security Settings dialog box, select the account you specified on step 2, and click Edit. 5. In the Permission Entry dialog box, select This object and all descendant (child) objects from the Apply to drop-down list Close the dialog boxes by clicking OK.

19 Target Exchange 2010 Preparation Step Granting Full Control on the Microsoft Exchange System Objects Organizational Unit The Target Exchange Account used by Migration Manager for Exchange agents needs the Full Control permission on the Microsoft Exchange System Objects organizational unit (OU) in all domains in which target Exchange 2010 servers involved in public folder synchronization reside. 1. In the Active Directory Users and Computers snap-in, right-click the Microsoft Exchange System Objects OU and click Properties. If there is no Microsoft Exchange System Objects OU, you should select View Advanced Features in the Active Directory Users and Computers snap-in. 2. On the Security tab, click Add, and select the Target Exchange Account (in our example, QMM_Trg_Ex). 3. Select the account name, and then enable the Allow option for the Full Control permission in the Permissions box. 4. Click the Advanced button. In the Advanced Security Settings dialog box, select the account you specified on step 2, and click Edit. 5. In the Permission Entry dialog box, select This object and all descendant (child) objects from the Apply to drop-down list. 6. Close the dialog boxes by clicking OK. 17

20 Quest Migration Manager for Exchange 8.7 Step 2.2.6: Granting Permission to Make Public Folders Mail-Enabled If a public folder is mail-enabled in the source organization, the Public Folder Target Agent needs to be able to make it mail-enabled in the target organization as well. To achieve this, assign your Target Exchange Account permissions to run the Enable- MailPublicFolder cmdlet, as follows: 1. Add this account to the Public Folder Management group in the target Exchange 2010 organization: a) In the Active Directory Users and Computers snap-in select the Microsoft Exchange Security Groups node. b) In the right pane, right-click Public Folder Management group and click Properties. c) On the Members tab click Add and select the Target Exchange Account (in our example, QMM_Trg_Ex). d) Close the dialog boxes by clicking OK If the Target Exchange Account is located in another trusted forest, you cannot add the account to the Public Folder Management group. In this case grant the following permissions for the Exchange Administrative Group (FYDIBOHF23SPDLT) container and its descendant (child) objects to the account in the Configuration partition using the ADSIEdit snap-in: Modify public folder replica list permission Modify public folder deleted item retention permission Modify public folder quotas permission 18

21 Target Exchange 2010 Preparation 2. Give the account the Full Control permission on the CN=<ExchangeOrganizationName>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<...>,DC=<...> container: a) From the Start menu, select Run. In the Run dialog box, type ADSIEdit.msc. Click OK. If you have a Windows 2000/2003 domain controller, the ADSIEdit utility, which is part of the Windows 2000/2003 Support Tools, may not be installed. In this case install the Support Tools by running the Support\Tools\Suptools.msi file located on the Windows 2000/2003 CD. b) In the ADSIEdit snap-in, open the CN=<ExchangeOrganizationName>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<...>,DC=<...> container c) Right-click the CN=<ExchangeOrganizationName> container and click Properties. d) In the Properties dialog box, click the Security tab. e) On the Security tab, click Advanced. f) In the Advanced Security Settings dialog box, click Add. g) In the Select User, Computer, Service Account, or Group (or similar) dialog box, select the Target Exchange Account (in our example, QMM_Trg_Ex) and click OK. h) In the Permission Entry for dialog box, select This object and all descendant (child) objects from the Apply to drop-down list. i) Allow Full Control permission for the Target Exchange Account. j) Close the dialog boxes by clicking OK. 19

22 Quest Migration Manager for Exchange 8.7 Step 2.2.7: Granting Full Control on Exchange 2010 Mailboxes The Target Exchange Account used by Migration Manager for Exchange agents needs the Full Control permission on each mailbox database involved in migration and on its associated public folder database if it exists. To grant this permission run the following cmdlet in Exchange Management Shell: Get-MailboxDatabase Add-ADPermission -User ap\qmm-exchangeaccounts - AccessRights GenericAll -ExtendedRights Receive-As Step 2.2.8: Granting Membership in Recipient Management Group To perform Move mailbox operations, the Target Exchange Account needs to be assigned permissions to run the following cmdlets: New-MoveRequest Get-MoveRequest Remove-MoveRequest Get-MoveRequestStatistics To grant these permissions, add the account to the Recipient Management group in the target Exchange 2010 organization, as follows: 1. In the Active Directory Users and Computers snap-in select the Microsoft Exchange Security Groups node. 2. In the right pane, right-click Recipient Management group and select Properties from the shortcut menu. 3. On the Members tab click Add and select the Target Exchange Account (in our example, QMM_Trg_Ex). 20

23 Target Exchange 2010 Preparation 4. Close the dialog boxes by clicking OK. Step 2.3: Setting Up the Target Active Directory Account This section describes how to set the required permissions for the Target Active Directory Account used by Migration Manager for Exchange agents. This account is used for the following: Working with the target Active Directory Re-homing mailboxes Switching mailboxes and synchronize mailboxes in Remote Users Collections (Mail Source Agent, Mail Target Agent) The required permissions for the Target Active Directory Account are as follows: Read access to the target domain Full Control permission on the organizational units (OUs) (and their child objects) where the target synchronized objects are located. Read permission for the Microsoft Exchange container in the target Active Directory 21

24 Quest Migration Manager for Exchange 8.7 To set up the Target Active Directory Account, perform the steps below. Note that the steps below are given only as an example of a possible Target Active Directory Account setup. Step 2.3.1: Changing the Default Target Active Directory Account The default Target Active Directory Account (initially displayed on the Associated domain controller page of the Exchange server's properties) is set when you add the target organization to the migration project (see the Registering Source and Target Organizations section of the Migration Manager for Exchange User Guide for details). To change the Target Active Directory Account, click Modify on the General Associated domain controller page of the corresponding target server properties in the Migration Manager for Exchange Console. To go on using the default Target Active Directory Account for Exchange migration, grant the permissions required for Exchange migration to this account (as described on the steps below). Step 2.3.2: Granting Read Access to Active Directory Domain The Target Active Directory Account used by Migration Manager for Exchange agents needs Read access to the target domain to work with servers and target Active Directory. To grant this permission to the account, complete the following steps: 1. On the target domain controller in the Active Directory Users and Computers snap-in, right-click the domain name, and then click Properties on the shortcut menu. 2. On the Security tab, click Add and select the account to which you wish to assign permissions (in our example, QMM_Trg_AD). If there is no Security tab, you should select View Advanced Features in the Active Directory Users and Computers snap-in. 3. Select the account name, and then enable the Allow option for the Read permission in the Permissions box. 4. Click the Advanced button. In the Advanced Security Settings dialog box, select the account you specified on step 2 and click Edit. 22

25 Target Exchange 2010 Preparation 5. In the Permission Entry dialog box, select This object and all descendant (child) objects from the Apply to drop-down list. 6. Close the dialog boxes by clicking OK. Step 2.3.3: Granting Full Control on Organizational Unit To work with the target Active Directory objects, the Target Active Directory Account needs the Full Control permission on the organizational units and their child objects that contain the objects to be synchronized. This permission should be set on the domain controller where the objects you need to synchronize are located. To grant the required permissions to the account, perform the following steps: 1. In the Active Directory Users and Computers snap-in, right-click the OU where the objects are located, and click Properties. 2. On the Security tab, click Add, and select the Target Active Directory Account (in our example, QMM_Trg_AD). If there is no Security tab, you should select View Advanced Features in the Active Directory Users and Computers snap-in. 3. Select the account name, and then enable the Allow option for the Full Control permission in the Permissions box. 23

26 Quest Migration Manager for Exchange Click the Advanced button. In the Advanced Security Settings dialog box, select the account you specified on step 2, and click Edit. 5. In the Permission Entry dialog box, select This object and all descendant (child) objects from the Apply to drop-down list. 6. Close the dialog boxes by clicking OK. Step 2.3.4: Granting Read Permission for the Microsoft Exchange Container In the target Exchange 2010 organization, the Target Active Directory Account requires the Read permission on the Microsoft Exchange container in the target Active Directory. To grant this permission, add the account to the View-Only Organization Management group in the target Exchange 2010 organization, as follows: 1. In the Active Directory Users and Computers snap-in select the Microsoft Exchange Security Groups node. 2. In the right pane, right-click View-Only Organization Management group and click Properties. 24

27 Target Exchange 2010 Preparation 3. On the Members tab click Add and select the Target Exchange Account (in our example, QMM_Trg_AD). 4. Close the dialog boxes by clicking OK. If the Target Active Directory Account is located in another trusted forest, you cannot add the account to the View-Only Organization Management group. In this case grant the Read permission for the Microsoft Exchange container and its child objects to the account in the Configuration partition using the ADSIEdit snap-in. Step 2.4: Setting Up Target Agent Host Account This section describes how to set the required permissions for the Target Agent Host Account used by Migration Manager for Exchange agents. This account is used to install and run Migration Manager for Exchange agents on the target agent host and to access the license server. The required privileges for the Target Agent Host Account are as follows: Membership in the local Administrators group on the license server (unless alternative credentials are used for the license server). If server is located in another trusted forest, the account should have local Administrator permissions on the license server 25

28 Quest Migration Manager for Exchange 8.7 Local Administrator permissions on the agent host server. By default each Exchange server is an agent host for itself. If you use the default agent host then to simplify the account setup process, you can grant these permissions to the Target Exchange Account and use it instead of the Target Agents Host Account. To set up the Target Agent Host Account, perform the steps below. Note that the steps are given only as an example of a possible Target Agent Host Account setup. Step 2.4.1: Changing the Default Target Agent Host Account The default Target Agents Host Account (initially displayed on the Default Agent Host page of the Exchange server Properties) is set when you add the target organization to migration project (see the Registering Source and Target Organizations section of the Migration Manager for Exchange User Guide for details). If necessary, you can change the default Target Agent Host Account by clicking Modify on the General Default Agent Host page of the corresponding target server properties in the Migration Manager for Exchange Console. To go on using the default Target Agent Host Account for Exchange migration, grant the permissions required for Exchange migration to this account (as described on the steps below). Step 2.4.2: Granting Membership in the Local Administrators Group on the License Server The Target Agent Host Account should be a member of the local Administrators group on the license server (unless alternative credentials are used for the license server). If license server is a domain controller, the account should be added to the domain local Administrators group of the domain. Local Administrator permissions are required on the license server if this license server is located in another trusted forest. To add the Target Agents Host Account to the local Administrators group on the license server perform the following: 1. Open the Computer Management snap-in (Click Start Run, enter compmgmt.msc and then click OK). 2. In the left pane click System Tools Local Users and Groups Groups. 3. Right-click the Administrators group and click Add to Group. 4. Click Add and select the Target Agent Host Account (in our example, QMM_Trg_AH). 26

29 Target Exchange 2010 Preparation 5. Close the dialog boxes by clicking OK. Step 2.5: Setting Up Single Administrative Account for Exchange Migration (Optional) You can simplify the setup by using one account with all Migration Manager for Exchange agents. This account should have the permissions that are required for all the agents on every server that is involved in the migration both in the source and in the target organization. However, using such an account in a production environment may be a security risk because it would be extremely powerful. The steps below will help you to set up a single administrative account that can be used by all agents. The same account should be used to launch Migration Manager for Exchange Console. Step 2.5.1: Creating the Single Administrative Account This step should be performed in coordination with the administrator of the source Exchange organization. The Migration Manager for Exchange administrative account should be created either in the source or in the target domain. Two-way trusts between the source and the target domain should be established. 27

30 Quest Migration Manager for Exchange 8.7 To ensure that the Migration Manager for Exchange administrative account is not a member of any Active Directory group with some of the permissions denied, we recommend creating a new user account. In our example we create the new user account in the target domain and name it QMMEx. To create such account, perform the following: 1. On the target domain controller in the Active Directory Users and Computers, right-click Users and then click New User. 2. In the New Object - User wizard, type First name and User logon name of the administrative account (in our example, QMMEx), then click Next. 3. Type and confirm the password, select necessary options for the account, click Next and then click Finish. Step 2.5.2: Granting Access to Active Directory The administrative account should have access to the target Active Directory to create objects and modify their properties. To grant such access privileges to the account, add the account to the domain local Administrators group: 1. In the Active Directory Users and Computers snap-in, click Builtin, then in the right pane right-click Administrators and click Properties. 2. Go to the Members tab, click Add and select the administrative account (in our example, QMMEx). 28

31 Target Exchange 2010 Preparation 3. Close the dialog boxes by clicking OK. Step 2.5.3: Granting Full Control on Exchange Organization Grant the administrative account the Full Control permission on the CN=<ExchangeOrganizationName>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<...>,DC=<...> container: 1. From the Start menu, select Run. In the Run dialog box, type ADSIEdit.msc. Click OK. If you have a Windows 2000/2003 domain controller, the ADSIEdit utility, which is part of the Windows 2000/2003 Support Tools, may not be installed. In this case install the Support Tools by running the Support\Tools\Suptools.msi file located on the Windows 2000/2003 CD. 2. In the ADSIEdit snap-in, open the CN=<ExchangeOrganizationName>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<...>,DC=<...> container 3. Right-click the CN=<ExchangeOrganizationName> container and click Properties. 4. In the Properties dialog box, click the Security tab. 5. On the Security tab, click Advanced. 6. In the Advanced Security Settings dialog box, click Add. 29

32 Quest Migration Manager for Exchange In the Select User, Computer, Service Account, or Group (or similar) dialog box, select the administrative account (in our example, QMMEx) and click OK. 8. In the Permission Entry for dialog box, select This object and all descendant (child) objects from the Apply to drop-down list. 9. Allow Full Control permission for the administrative account. 10. Close the dialog boxes by clicking OK. Step 2.5.4: Granting Full Control on Exchange 2010 Mailboxes The administrative account used by Migration Manager for Exchange agents needs the Full Control permission on each mailbox database involved in migration and on its associated public folder database if it exists. To grant this permission run the following cmdlet in Exchange Management Shell: Get-MailboxDatabase Add-ADPermission -User ap\qmm-exchangeaccounts - AccessRights GenericAll -ExtendedRights Receive-As 30

33 Step 2.5.5: Granting Access to SQL Server Target Exchange 2010 Preparation The administrative account should have the appropriate permissions to create and modify databases on a SQL server. In SQL Server Management Studio, browse to the server that will be used by Migration Manager for Exchange, and select Logins from the server Security node. To create a new login for the administrative account, complete the following steps: 1. Right-click Logins and click New Login. 2. On the General page of the Login - New dialog box, specify the administrative account in the Name field (in our example, QMMEx) and select the Windows Authentication method. 31

34 Quest Migration Manager for Exchange On the Server Roles page of the Login - New dialog box, select the dbcreator role. 4. Close the dialog boxes by clicking OK. Step 2.5.6: Granting Read Permission for the Microsoft Exchange Container The administrative account requires the Read permission on the Microsoft Exchange container in the target Active Directory. To grant it, complete the following steps: 1. On the target domain controller in the Active Directory Users and Computers snap-in select the Microsoft Exchange Security Groups node. 2. In the right pane, right-click View-Only Organization Management group and click Properties. 3. On the Members tab click Add and select the administrative account (in our example, QMMEx). 32

35 Target Exchange 2010 Preparation 4. Close the dialog boxes by clicking OK. Step 2.5.7: Granting Local Administrative Rights The administrative account should be a member of the local Administrators groups on the following servers: The Directory Synchronization Agent servers The Migration Manager for Exchange Console server The license server specified in the Migration Manager for Exchange Console options The agent host servers If a server is a domain controller, the account should be added to the domain local Administrators group of the domain. To add the administrative account to the Administrators group, perform the following on each server listed above: 1. Open the Computer Management snap-in (Click Start Run, enter compmgmt.msc and then click OK). 2. In the left pane click System Tools Local Users and Groups Groups. 33

36 Quest Migration Manager for Exchange Right-click the Administrators group and click Add to Group. 4. Click Add and select the administrative account (in our example, QMMEx). 5. Close the dialog boxes by clicking OK. Step 2.5.8: Changing the Default Active Directory, Exchange and Agent Host Account To begin using the single administrative account for Exchange Migration, you should log on under this account to the computer where the Migration Manager for Exchange Console is installed. Then select the administrative account in the Console instead of the current Target Exchange Account, Target Active Directory Account and Target Agent Host Account: To change the default Target Exchange Account, click Modify on the General Connection page in the properties of the corresponding target server in the Migration Manager for Exchange Console. To change the default Target Active Directory Account, click Modify on the General Associated domain controller page in the properties of the corresponding target server in the Migration Manager for Exchange Console. To change the default Target Agent Host Account, click Modify on the General Default Agent Host page in the properties of the corresponding target server in the Migration Manager for Exchange Console. 34

37 Target Exchange 2010 Preparation Step 3: Preparing the Target Exchange Environment for Exchange Migration Step 3.1: Backing Up Exchange Before implementing Migration Manager for Exchange in your production environment, back up your Exchange infrastructure. We recommend that target Active Directory data be backed up at least twice a day during migration. Transaction Log File Cleanup When Migration Manager for Exchange synchronizes mail and public folders, for every megabyte of data migrated from the source to the target, a transaction log file of equal size is generated on the target Exchange server. Exchange-aware backup applications purge the transaction logs after the backup completes. By the time the backup finishes, all logged transactions have already been applied to the store and backed up to tape, making log cleaning safe. Large transaction logs that are generated during mailbox migration quickly occupy free disk space. To work around this problem, perform one of the following: If a full backup strategy is implemented in the organization or there is no backup strategy at all, then circular logging may be enabled for unattended log deletion. If an incremental or differential backup strategy is already implemented in the organization, then make sure that logs are cleared automatically when backup process is finished. Do not enable circular logging in this case. Note also that Microsoft recommends turning OFF circular logging on the Exchange server. For more information, refer to Microsoft Knowledge Base article : XADM: How Circular Logging Affects the Use of Transaction Logs. 35

38 Quest Migration Manager for Exchange 8.7 Step 3.2: Creating Aelita EMW Recycle Bin Public Folder If you plan to perform public folder synchronization using Migration Manager Public Folder agents, you should create a special public folder called Aelita EMW Recycle Bin. Replicate this folder to all the public folder servers involved in the public folder synchronization process. This folder will help prevent data loss in case of accidental public folder deletion or incorrect moves. 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, if it exists, instead of permanently deleting the folder. You can use this folder to check whether important information has been deleted, and restore any data deleted by mistake. Step 3.3: Creating Administrator Mailboxes for Public Folder and Free/Busy Synchronization Administrator mailboxes should be created on all target Exchange 2010 servers involved in public folder and free/busy synchronization. These mailboxes will be used to access the public folder tree and the Schedule+ Free/Busy folder when creating public folder and free/busy synchronization jobs. The administrator mailbox specified for the synchronization job should not be changed during the synchronization process. The administrator mailboxes should not be included in mailbox or calendar synchronization jobs. Step 3.4: Creating Administrator Mailboxes for Mailbox and Calendar Synchronization (Optional) Mailbox and calendar synchronization agents access the migrated mailboxes via the administrator mailbox. By default, the Microsoft System Mailbox is used as the administrator mailbox on Exchange 2010 servers. However, in some cases it is necessary to create custom administrator mailboxes and use them instead of the Microsoft System Mailbox. Step 3.5: Creating Custom Throttling Policies To prevent possible issues in an Exchange 2010 Service Pack 1 or later organization, you should create custom throttling policies and apply them to the Target Exchange Accounts. To do this, run the following PowerShell commands for each Target Exchange Account: New-ThrottlingPolicy <QMM_Exchange_Account_Throttling_Policy_Name> Set-ThrottlingPolicy <QMM_Exchange_Account_Throttling_Policy_Name> - RCAMaxConcurrency $null -RCAPercentTimeInAD $null -RCAPercentTimeInCAS $null -RCAPercentTimeInMailboxRPC $null Set-ThrottlingPolicyAssociation -Identity <QMM_Exchange_Account_Name> - ThrottlingPolicy <QMM_Exchange_Account_Throttling_Policy_Name> 36