Installing Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1
Installing the Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1
Migration Manager needs version 6.5.8353.0 or later of Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1 to be installed on the computers where Migration Manager agents will run (that is, Exchange 2007 and 2010 Servers and agent hosts only).
Since the MAPI CDO setup package is not available for distribution, you should download it from the Microsoft Web site. At the moment of the last document update, the download link is http://www.microsoft.com/en-us/download/details.aspx?id=42040.
After installing the API, restart the computer.
Specifying displayName Value for Target Exchange 2007 Mailbox Database Objects
Specifying displayName Value for Target Exchange 2007 Mailbox Database Objects
Mailbox databases in Exchange 2007 organizations are created with blank displayName parameters. As a result, some agents may stop working. To resolve this issue, you have to specify the displayName values for the target Exchange 2007 mailbox databases. You can do it either manually, as described in the related subtopics, or using the SetStoreDisplayName.js script located in the QMMEx Reskit\Scripts folder on the Migration Manager for Exchange Installation CD. You must run the script after you install Migration Manager for Exchange.
To specify the displayName value for the target Exchange 2007 mailbox database objects
- Launch the ADSIEdit utility from the Windows Support Tools: click Start | Run and type in ADSIEdit.msc. Click OK.
NOTE: If you have Windows 2003 domain controller the ADSIEdit utility, which is part of the Windows 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 2003 CD.
- In the ADSIEdit snap-in, browse to the container named
CN=Exchange Administrative Group (FYDIBOHF23SPDLT),
CN=Administrative Groups,CN=<ExchangeOrganizationName>,
CN=Microsoft Exchange,CN=Services,CN=Configuration,
DC=<…>,DC=<…> - For each Exchange 2007 server involved on the migration steps, open the container named CN=<StorageGroup>,CN=InformationStore,CN=<ServerName>,
CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),
CN=Administrative Groups,CN=<ExchangeOrganizationName>,
CN=Microsoft Exchange,CN=Services,CN=Configuration,
DC=<…>,DC=<…> - Then, for each mailbox database, right-click the database object and select Properties from the shortcut menu.
- On the Attribute Editor tab, copy the adminDisplayName attribute value to the displayName attribute value and click OK.
- Click OK to apply the settings and close the dialog box.
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:
- 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
Setting Up Connection with the Source Exchange Organization Using SMTP Connectors
This section describes how to set up a connection with the source Exchange organization using SMTP connectors. On this step you may need to coordinate with the administrator of the source Exchange organization to set up the connection properly.
For more details, see the related topics: