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

Create Aelita EMW Recycle Bin Public Folder (Optional)

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.

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.

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

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:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS
3. Click the Parameters key.
4. On the Edit menu, point to New, and then click DWORD Value.
5. Type NSPI max sessions per user, and then press Enter.
6. Double-click NSPI max sessions per user, type the appropriate maximum number of the NSPI connections, and then click OK.

7. Restart the computer or restart Active Directory Domain Services.

For additional information, see the following Microsoft Support articles:

• Error: "Trying to connect to Microsoft Exchange Server" results in MAPI_E_LOGON_FAILED
• NSPI connection to a Windows-based domain controller causes MAPI client applications to fail and returns a "MAPI_E_LOGON_FAILED" error message