Migrate BES from Exchange 00/03 to 07

Migrate the BlackBerry Enterprise Server from Microsoft Exchange Server 2000 or 2003 to Microsoft Exchange Server 2007


Doc ID : KB14502
Last Modified : 2008-02-22
Document Type : How To

Environment

• BlackBerry® Enterprise Server for Microsoft® Exchange
• Microsoft® Exchange Server 2000, 2003, and 2007

Procedure

To migrate the BlackBerry Enterprise Server from Microsoft Exchange Server 2000 or 2003 to Microsoft Exchange Server 2007, complete the following steps:

1. Stop all BlackBerry Enterprise Server services.
2. Move the BlackBerry Enterprise Server service account. The default name for this account is BESAdmin.
3. After migrating the Microsoft Exchange Server, verify the Microsoft Exchange Server 2007 permissions for the BlackBerry Enterprise Server.
4. Set the required permissions for the BlackBerry Enterprise Server in Microsoft Exchange 2007. For more information, see KB12483. Note: If Microsoft Exchange System Manager 2003 Service Pack 2 is installed on the BlackBerry Enterprise Server, skip to step 11.
5. Remove Microsoft Exchange System Manager 2000.
6. Perform a search for MAPI32.dll and cdo.dll.
7. Rename any cdo.dll and MAPI32.dll files from the system32 folder and the program files\exchsrvr\bin folder to a .bak file extension.
8. Download and install the latest Messaging Application Programming Interface (MAPI) and Collaboration Data Object (CDO) clients. For more information, see KB12697.
9. Install a MAPI subsystem by downloading and installing the Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1. For more information, see Microsoft Help and Support.
10. Resolve the MAPI profile for the BESAdmin mailbox on the Microsoft Exchange Server 2007 by going to Start > Programs > BlackBerry Enterprise Server > Edit the MAPI.
11. Restart the BlackBerry Enterprise Server. Important: Restarting the BlackBerry Enterprise Server will delay email message delivery to BlackBerry smartphones. For more information, see KB04789.

Additional Info

For more information, see KB13302.