How to migrate from Microsoft Exchange Server 2003 or 2007 to Microsoft Exchange Server 2010 in a BlackBerry Enterprise Server 5.0 environment

Article ID: KB22601

Type: Support Content

Last Modified: 07-17-2014

 

Product(s) Affected:

  • BlackBerry Enterprise Server for Microsoft Exchange
  • BlackBerry Enterprise Server Express for Microsoft Exchange
CollapseEnvironment
  • BlackBerry Enterprise Server 5.0 SP1 to 5.0 SP4 for Microsoft Exchange
  • BlackBerry Enterprise Server Express 5.0 SP1 to 5.0 SP4 for Microsoft Exchange
  • Microsoft Exchange Server 2003 to 2010
CollapseOverview

When migrating Microsoft Exchange 2003 or 2007 to Microsoft Exchange 2010 in a BlackBerry Enterprise Server 5.0 environment, complete the following tasks:

Summary of Tasks

  1. Verify the requirements are met to support Microsoft Exchange Server 2010.
  2. Update the MAPI subsystem to support Microsoft Exchange Server 2010 on the BlackBerry Enterprise Server.
  3. Move the BlackBerry Enterprise Server service account mailbox.
  4. Create a new throttling policy that does not limit concurrent connections.
  5. Assign the proper permissions to the BlackBerry Enterprise Server service account.
  6. Increase the maximum number of connections to the Address Book service.
  7. (Optional) Configure the BlackBerry Enterprise Server to run without public folders.
  8. (Optional) Configure a management role for Microsoft Exchange Web Services.
  9. (Optional) Permit meeting requests from outside of the organization when using Microsoft Exchange Web Services.
  10. Verify that the MAPI profiles settings for the new Microsoft Exchange Server 2010 were created correctly.
  11. Restart the BlackBerry Enterprise Server Machine.


    Important:
    Restarting certain BlackBerry Enterprise Server services delays email message delivery to BlackBerry smartphones. For more information, see KB04789 .



Task 1

Verify that the requirements are met to support Microsoft Exchange Server 2010.

Before proceeding with the migration, verify the versions of the following components:

  1. The BlackBerry Enterprise Server is at a minimum of 5.0 SP2 MR5 or 5.0 SP3 MR3.
     
    • To check the version of the BlackBerry Enterprise Server, see KB19714 and KB05131.
    • For BlackBerry Enterprise Server 5.0 SP2, apply MR5. For BlackBerry Enterprise Server 5.0 SP3, apply MR3 (for BlackBerry Enterprise Server Express, MR2).
    • To download Service Packs and Maintenance Releases for BlackBerry Enterprise Server 5.0, visit http://www.blackberry.com/support/downloads/.
       
  2. The Microsoft Exchange Server 2010 must be at the minimum of Update Rollup 1 (14.00.0682.001). Recommended level for Exchange SP1 is Update Rollup 3 (14.01.0289.007).
     
    • To check the version of a Microsoft Exchange Server, see KB20412.
    • For more information about Microsoft Exchange Server 2010 RU1, visit the Microsoft Help and Support site and search for "KB976573" or "Description of Update Rollup 1 for Exchange Server 2010".
    • If Exchange 2010 is running at SP1, it is recommend to apply Update Rollup 3. To learn more about Microsoft Exchange Server 2010 RU3, visit the Microsoft Help and Support site and search for "KB2529939" or "Description of Update Rollup 3 for Exchange Server 2010 Service Pack 1".
       
  3. The Microsoft MAPI/CDO Package installed on the BlackBerry Enterprise Server should be the latest available from Microsoft. 
     
    To verify the Microsoft Exchange Server MAPI Client and CDO 1.2.1 versions, complete the following steps:
     
    1. Verify that the following .DLL files exist in ExchangeMAPI folder located in the Program Files folder and System32 folder:
       
       C:\Windows\System32\MAPI32.DLL, Version: 1.0.2536.0
       C:\Program Files\ExchangeMAPI\CDO.DLL, Version: 6.5.8244.0
       C:\Program Files\ExchangeMAPI\EMSMDB32.DLL, Version: 6.5.8244.0
       
       
    2. Right-click each file and go to the Version tab to review the versions.
    3. (Optional) In the BlackBerry Messaging Agent (MAGT) logs, verify the following [ENV] environment variables are reported:
       
      [ENV] MAPI32.DLL: C:\Windows\System32\MAPI32.DLL, Version: 1.0.2536.0
      [ENV] CDO.DLL: C:\Program Files\ExchangeMAPI\ Version: CDO.DLL, 6.5.8244.0
      [ENV] EMSMDB32.DLL: C:\Program Files\ExchangeMAPI\ EMSMDB32.DLL, Version: 6.5.8244.0
       
      If the MAPI/CDO is not at minimum version 6.5.8211.0, download the required version for preparation to update the files in Task 10 below. To locate and download the file, visit Microsoft Help and Support site and search for "Download MAPI CDO 1.2.1". For more information on how to upgrade MAPI on the BlackBerry Enterprise Server, see KB15779.

Recommended Updates:

Install the following Microsoft Windows Kernel Memory Manager hotfixes on all servers running Windows 2008 R2 and Exchange 2010:

NoteTo locate these updates please visit the Microsoft Help and Support site and search for the listed KB article numbers. These hotfixes are also included in Microsoft Windows 2008 R2 SP1.

  • KB979149 - A computer that is running Windows 7 or Windows Server 2008 R2 becomes unresponsive when running a large application
  • KB2155311 - Poor performance occurs on a computer that has NUMA-based processors and that is running Windows Server 2008 R2 or Windows 7 if a thread requests lots of memory that is within the first 4 GB of memory.

Task 2

Update the MAPI subsystem to support Microsoft Exchange Server 2010 on the BlackBerry Enterprise Server.

Verify the version of MAPI Client and Collaboration Data Object (CDO) 1.2.1 as indicated in Task 1, and update as required. Visit the Microsoft Help and Support site and search for download of MAPI CDO 1.2.1.

Follow the steps in KB15779 to update the MAPI subsystem.



Task 3

Move the BlackBerry Enterprise Server service account mailbox.

See KB03296 for instructions regarding moving the service account mailbox (the default name for this account is usually BESAdmin). 
 

For more information about Microsoft Mailbox Moves from Microsoft Exchange Server 2007 to 2010, please visit the Microsoft TechNet site and search for "Move Mailboxes from Exchange 2007 Servers to Exchange 2010 Servers" or "dd638192".
 
For more information about Microsoft Mailbox Moves from Microsoft Exchange Server 2003 to 2010,
please visit the Microsoft TechNet site and search for "Move Mailboxes from Exchange 2003 Servers to Exchange 2010 Servers" or "dd638187".

After the mailbox move, verify the move request is complete, please visit the Microsoft TechNet site and search for "View Move Request Properties" or "dd876924".


Task 4

Create a new client throttling policy that does not limit concurrent connections.

By default, Microsoft Exchange Server 2010 uses client throttling policies to track the bandwidth that each BlackBerry smartphone user consumes, and enforces bandwidth limits, as necessary. The default connection is set to 20. Turn off client throttling for the Windows account that has a Microsoft Exchange Server 2010 mailbox because the policies affect the performance of the BlackBerry Enterprise Server negatively. The default name for this account is usually BESAdmin.

To create and set the BESPolicy to null, follow these steps:

  1. On a computer that hosts the Microsoft Exchange Management Shell, click Start > Microsoft Exchange Server 2010 > Exchange Management Shell.
  2. Type: New-ThrottlingPolicy BESPolicy
  3. Type: Set-ThrottlingPolicy BESPolicy -RCAMaxConcurrency $NULL -RCAPercentTimeInCAS $NULL -RCAPercentTimeInMailboxRPC $NULL -RCAPercentTimeInAD $NULL –EWSMaxConcurrency $NULL –EWSPercentTimeInAD $NULL –EWSPercentTimeinCAS $NULL –EWSPercentTimeInMailboxRPC $NULL –EWSMaxSubscriptions $NULL –EWSFastSearchTimeoutInSeconds $NULL –EWSFindCountLimit $NULL
     
    If the Microsoft Exchange Server is 2010 SP1, it is also necessary to execute the following command:
    Set-ThrottlingPolicy BESPolicy -CPAMaxConcurrency $NULL -CPAPercentTimeInCAS $NULL -CPAPercentTimeInMailboxRPC $NULL
  1. To assign the new Throttling Policy to the BESAdmin account, type:
    Set-Mailbox "BESAdmin" -ThrottlingPolicy BESPolicy

To confirm that all required settings have been set correctly, follow these steps:

  1. On a computer that hosts the Microsoft Exchange Management Shell, click Start > Microsoft Exchange Server 2010 > Exchange Management Shell.
  2. Type: Get-ThrottlingPolicy BESPolicy

These items should be blank:

  • CPAMaxConcurrency (Exchange 2010 SP1)
  • CPAPercentTimeInCAS (Exchange 2010 SP1)
  • CPAPercentTimeInMailboxRPC (Exchange 2010 SP1)
  • EWSMaxConcurrency
  • EWSPercentTimeInAD
  • EWSPercentTimeInCAS
  • EWSPercentTimeInMailboxRPC
  • EWSMaxSubscriptions
  • EWSFastSearchTimeoutInSeconds
  • EWSFindCountLimit
  • RCAMaxConcurrency
  • RCAPercentTimeInAD
  • RCAPercentTimeInCAS
  • RCAPercentTimeInMailboxRPC

To check which throttling policy is applied to the BESAdmin account, follow these steps:

  1. On a computer that hosts the Microsoft Exchange Management Shell, click Start > Microsoft Exchange Server 2010 > Exchange Management Shell.
  2. Type: Get-Mailbox "besadmin" | fl -property ThrottlingPolicy

Note: These are Active Directory objects, and therefore they need to be replicated to all Domain Controllers within the environment. When the BlackBerry Enterprise Server connects to the Client Access Servers, the Client Access Server will apply the Throttling Policy to the assigned account based on the information in the connected Domain Controller's Active Directory database.


Task 5

Assign the proper permissions to the BlackBerry Enterprise Server service account.

  1. On a computer that hosts the Microsoft Exchange Management Shell, click Start > Microsoft Exchange Server 2010 > Exchange Management Shell.
  2. Assign Receive-As to the BESAdmin account:
    Get-MailboxDatabase | Add-ADPermission –User “BESAdmin” –AccessRights ExtendedRight –ExtendedRights Receive-As, ms-Exch-Store-Admin, ms-Exch-Store-Visible 
     
  3. Assign the View-Only role to the BESAdmin account:
    Add-RoleGroupMember “View-Only Organization Management” –Member “BESAdmin”
     
  4. Assign the Send-As to the BESAdmin account that is in an OU or CN:
    Add-ADPermission –InheritedObjectType User –InheritanceType Descendents –ExtendedRights Send-As –User “BESAdmin” –Identity “OU=<organizational_unit>,DC=<domain_1>,DC=<domain_2>,DC=<domain_3>”
    or
    Add-ADPermission –InheritedObjectType User –InheritanceType Descendents –ExtendedRights Send-As –User “BESAdmin” –Identity “CN=<common_name>,DC=<domain_1>,DC=<domain_2>,DC=<domain_3>”
     
    For example:
    Add-ADPermission –InheritedObjectType User –InheritanceType Descendents –ExtendedRights Send-As –User “BESAdmin” –Identity “CN=BES Admin Exch2K10,OU=TestOU,DC=SEN104,DC=EXAMPLE,DC=COM"
     
    Successful application of this permission can be verified via Active Directory Users and Computers or via the Exchange Management Shell interface. To verify that this permission has been applied using PowerShell, run the following command (where <Display_Name> is the display name of the BlackBerry smartphone user to be verified):
    Get-Mailbox -Identity "<Display_Name>" | Get-ADPermission | where { ($_.ExtendedRights -like "*Send-As*") -and -not ($_.User -like "NT AUTHORITY\SELF") } | select Identity, User, ExtendedRights, IsInherited | FT -Wrap 
     
    The following output indicates success: 
     
    Identity User ExtendedRights IsInherited
    -------- ---- -------------- -----------
    user01 domain\BESAdmin {Send-As} True

Task 6

Increase the maximum number of connections to the Address Book service for base Microsoft Exchange 2010.

By default, Microsoft Exchange Server 2010 limits the maximum number of connections from the BlackBerry Enterprise Server to the Address Book service to 50. To permit the BlackBerry Enterprise Server to run, increase the number of permitted connections to a large value (for example, 100,000).

On the computer that hosts the Microsoft Exchange Client Access Server:

  1. Navigate to <drive>:\Program Files\Microsoft\Exchange Server\V14\Bin
  2. Open the microsoft.exchange.addressbook.service.exe.config file in a text editor (such as Notepad).
  3. Change the value of the MaxSessionsPerUser key to 100000.
  4. Save and close the file.
  5. Restart the Address Book service.

Increase the maximum number of connections to the Address Book service for Microsoft Exchange 2010 SP1.

In Microsoft Exchange 2010 SP1 the settings are maintained in the Client Throttling Policy. There are 3 CPA entries and they should be set to NULL. If they are not set to NULL run the following CMDLET to set the parameter:

Set-ThrottlingPolicy BESPolicy -CPAMaxConcurrency $NULL -CPAPercentTimeInCAS $NULL -CPAPercentTimeInMailboxRPC $NULL


 

Task 7

(Optional) Configure the BlackBerry Enterprise Server to run without public folders.

If the public folders were not installed in Microsoft Exchange, configure the BlackBerry Enterprise Server to run without public folders by changing a registry key.

Important: Always back up the registry before making changes.

  1. On each computer that hosts the BlackBerry Enterprise Server, click Start > Run.
  2. In the Open field, type regedit to open the Registry Editor.
  3. Click OK.
  4. Perform one of the following actions:
    • If running a 32-bit version of Windows, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Messaging Subsystem\CDO
    • If running a 64-bit version of Windows, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows Messaging Subsystem
  5. If the CDO registry key does not exist, create a registry key named CDO.
  6. In the CDO registry key, if the DWORD value does not exist, create a DWORD value named Ignore No PF.
  7. Change the DWORD value to 1.
  8. Click OK.

Task 8

(Optional) Configure a management role for Microsoft Exchange Web Services.

To configure the BlackBerry Enterprise Server to use Microsoft Exchange Web Services to manage calendars on BlackBerry smartphones, configure a management role for Microsoft Exchange Web Services in Microsoft Exchange Server 2010.

  1. On a computer that hosts the Microsoft Exchange Management Shell, open the Microsoft Exchange Management Shell.
  2. Type: New-ManagementRoleAssignment -Name:"BES Admin EWS" -Role:ApplicationImpersonation –User:"BESAdmin"

For more information about configuring the BlackBerry Enterprise Server to use Microsoft Exchange Web Services, please visit BlackBerry Enterprise Server for Microsoft Exchange - Manuals and Guides and review the Administration guide for the specific version of BlackBerry Enterprise Server and KB20157.


Task 9

(Optional) Permit meeting requests from outside of the organization when using Microsoft Exchange Web Services.

To permit BlackBerry smartphone users to receive meeting requests from outside of the organization when using Microsoft Exchange Web Services, configure the calendar settings for the BlackBerry smartphone users' mailboxes in Microsoft Exchange Server at a specific mailbox server or for a specific BlackBerry smartphone user by performing the following steps:

  1. On a computer that hosts the Microsoft Exchange Management Shell, open the Microsoft Exchange Management Shell.
  2. To assign these settings for all mailboxes on a specific mailbox server:
    Get-Mailbox –Server <messaging_server_name> -ResultSize Unlimited | Set-CalendarProcessing -ProcessExternalMeetingMessages $true –AutomateProcessing AutoUpdate

    To assign these settings for a specific BlackBerry smartphone user mailbox:
    Set-CalendarProcessing -ProcessExternalMeetingMessages $true –AutomateProcessing AutoUpdate "UserName"

For more information, see  KB20866.


Task 10

Verify that the MAPI profiles settings for the new Microsoft Exchange Server 2010 were created correctly.

On the BlackBerry Enterprise Server:

  1. Go to Start > Programs > BlackBerry Enterprise Server > BlackBerry Server Configuration.
  2. Select the BlackBerry Server tab > Edit MAPI Profile.
  3. Verify the new Microsoft Exchange Server 2010 Client Access Server name and service account name.
  4. Perform a Check name to resolve the properties.
  5. Select Apply and OK.

Task 11

Prior to testing, restart the BlackBerry Enterprise Server Machine. (Not only BlackBerry Enterprise Server Services)

Note: Restarting the BlackBerry Enterprise Server or certain BlackBerry Enterprise Server services, delays email message delivery to BlackBerry smartphones. For more information, see KB04789.


CollapseAdditional Information

When Microsoft Exchange Server 2010 is introduced into a mixed Microsoft Exchange Server 2003 and/or Microsoft Exchange Server 2007 environment, there are specific steps that must be performed, as the Microsoft Exchange 2010 Client Access Server (CAS) component takes over all client calls in the environment for all servers.

For information on Client Access Server coexistence, visit the Microsoft TechNet site and search for "aa998186" or "CAS Coexistence".

Disclaimer

By downloading, accessing or otherwise using the Knowledge Base documents you agree:

   (a) that the terms of use for the documents found at www.blackberry.com/legal/knowledgebase apply to your use or reference to these documents; and

   (b) not to copy, distribute, disclose or reproduce, in full or in part any of the documents without the express written consent of RIM.


Visit the BlackBerry Technical Solution Center at www.blackberry.com/btsc.