Migration Manager for Exchange 8.15 - Source and Target Exchange 2003 Environment Preparation

Changing the Default Exchange Account Granting Read Access to the Target Active Directory Domain (Target Exchange Environment Only) Granting Membership in Server Local Administrators Group Granting Full Control on Organizational Unit Granting Full Control on Exchange Servers Granting Full Control on the Microsoft Exchange System Objects Organizational Unit Granting Modify Permissions

Setting Up the Active Directory Account

Changing the Default Active Directory Account Granting Read Access to Active Directory Domain Granting Full Control on Organizational Unit (For Target Exchange Environment Only)

Setting Up Agent Host Account

Changing the Default Agent Host Account Granting Membership in the Local Administrators Group on the License Server

Preparing the Exchange Environment for Exchange Migration

Backing up Exchange Create Aelita EMW Recycle Bin Public Folder (Optional) Creating Mailboxes for Public Folder and Free/Busy Synchronization Creating Administrator Mailboxes for Mailbox and Calendar Synchronization (Optional) Configuring the NSPI Connection Limit

Connecting the Source and Target Exchange Organizations Using SMTP Connectors

Setting Up the SMTP Connectors Forcing Exchange to Accept Redirected Mail as Inbound Mail Modifying Name Resolution Parameters on the Bridgehead Servers in Exchange Configuring DNS Servers for Mail Forwarding Testing the SMTP Connectors (Optional)

Create Aelita EMW Recycle Bin Public Folder (Optional)

Caution: If you skip this step, you must manually turn off using the Aelita EMW Recycle Bin folder during public folder synchronization (set the UseRecycleBin parameter to 0). See the Use Fine-Tuning the Agents section of the Migration Manager for Exchange User Guide for details.

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

Caution: Only deleted public folders will be put into the Aelita EMW Recycle Bin. If you delete a message from a public folder, it will be destroyed permanently in both the Source and Target Exchange organizations.

Creating Mailboxes for Public Folder and Free/Busy Synchronization

Administrator mailboxes should be created on all Exchange 2003 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 administrative mailbox selected for public folder synchronization should be hosted on the same server as the public database. This public database should be associated with the mailbox database where the administrative mailbox resides. For that, in Exchange Management Console open properties of the mailbox database and specify the public database as Default public folder database on the Client Settings tab.

Caution:

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.

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 Attendant mailbox is used as the administrator mailbox on Exchange 2003 servers. However, in some cases it is necessary to create custom administrator mailboxes and use them instead of the Microsoft System Attendant mailbox.

Configuring the NSPI Connection Limit

Important: This step must be performed only if you have any Windows Server 2008 or later domain controllers acting as Global Catalog.

By default, the maximum number of simultaneous Name Service Provider Interface (NSPI) connections equals to 50 per user for Windows Server 2008 or later domain controllers. Therefore, to avoid possible issues related to exceeding that value, you may need to increase the NSPI connection limit on all Windows Server 2008 or later domain controllers acting as Global Catalog. The recommended limit value equals the number of agent instances working simultaneously multiplied by 5.

To change the default connection limit for a domain controller, take the following steps:

Click Start, click Run, type regedit, and then click OK.
Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS
Click the Parameters key.
On the Edit menu, point to New, and then click DWORD Value.
Type NSPI max sessions per user, and then press Enter.
Double-click NSPI max sessions per user, type the appropriate maximum number of the NSPI connections, and then click OK.
Restart the computer or restart Active Directory Domain Services.

For additional information, see the following Microsoft Support articles:

Please select your product:

To serve you better, please complete the Purpose of your Chat:

Recommended Solutions for Your Problem

Migration Manager for Exchange 8.15 - Source and Target Exchange 2003 Environment Preparation

Create Aelita EMW Recycle Bin Public Folder (Optional)

Creating Mailboxes for Public Folder and Free/Busy Synchronization

Creating Administrator Mailboxes for Mailbox and Calendar Synchronization (Optional)

Configuring the NSPI Connection Limit