Bulletin ID A2E_188
Last Review 06/02/2010
Revision 1.3
Previous IDs None
Obsoletes None

Exchange 2010 Installation

Summary

Exchange 2010 imposes new requirements on Add2Exchange configuration. This bulletin provides the supported configurations, prerequisites and directions on how to configure your server and the Add2Exchange service account in order to work with Exchange 2010.

Description

Exchange 2010 is a significantly different environment from Exchange 2007 and 2003.

Supported Configurations

Because of the requirement for the latest CDO version, there are some configurations which are not supported:

  • Add2Exchange should not be installed on an Exchange 2003 server in the Exchange 2010 environment
    • This is because Exchange 2003's Exchange System Manager will not allow CDO to be replaced with the standalone version.  Moving Add2Exchange to a standalone server, the Blackberry Server or a Virtual Machine or the new Exchange server is supported and recommended.
  • Add2Exchange cannot be installed on a machine with Outlook 2007 installed
    • There are two versions of CDO, one for Outlook 2007 and one for Exchange. The Exchange version is required by Add2Exchange but will not install on a machine that has Outlook 2007.  Add2Exchange can not be installed on a terminal server.

Other than these limitations, Add2Exchange can be installed in any of the configurations that have been available in previous Exchange environments.

Prerequisites - at least up to these or newer

  • Exchange 2010 Public Folders
  • Exchange 2010 Update Rollup 3
  • Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1, version 6.5.8165.0 or later (released 4/28/2010)
  • UAC Disabled
  • Exchange Server Throttling Policy
  • Exchange Server Address Book Connections
Note

It is not ​necessary to disable IPv6 on the server.  Do not do this.

Older versions of Exchange had a CDO issue that required IPv6 to be turned off.  This is no longer the case on current, up-to-date Exchange installations and disabling IPv6 may negatively impact your Exchange install, so do not​ disable it.

Make sure you are up-to-date on your Exchange Service Packs and Update Rollups.

Public Folders

Exchange 2010 must have public folder support installed. Add2Exchange requires public folders, even for private-to-private synchronization. Public Folder support is enabled in the Exchange 2010 setup when you choose to enable Outlook 2003 support.

See your Exchange documentation to enable public folder support post-installation.

Update Rollup 3

Update Rollup 3 is the latest update as of the time of this writing. Any further update rollups or Service Packs will supersede this version, as they are cumulative. Always use the latest.

Be sure to read the Description of Update Rollup 3 for Microsoft Exchange Server 2010 Release to Manufacturing:

http://support.microsoft.com/?kbid=981401

In certain circumstances, the order in which you apply the rollup to your Exchange 2010 servers is important. See the description for details.

The description document states that you can get the rollup through Windows Update. You can also download the Exchange 2010 Update Rollup 3 here:

http://www.microsoft.com/en-us/download/details.aspx?id=415

After applying the rollup to all Exchange 2010 servers, you must reboot all Exchange servers, including any 2007 or 2003 servers.

MAPI Client and CDO

MAPI Client and CDO is Microsoft's name for a single package which installs both. This document uses the terms CDO and CDO Client and CDO interchangeably. Technically the term Client and CDO refers to the Exchange version of the CDO library, as opposed to the Outlook version.

There are two versions of CDO from Microsoft, one for Outlook 2007 and one for Exchange. The Exchange version is required by Add2Exchange. The filename of the required version is ExchangeMapiCdo.exe. The other version, ExchangeCdo.exe, will not work.

If there is an existing version of CDO installed on the server, it is required that you uninstall it prior to installing the latest CDO. While the setup package will install over an older version, some versions do not properly upgrade all files unless you uninstall the previous version.

The server on which Add2Exchange is installed must have the latest MAPI Client and CDO from Microsoft. Earlier versions will not work. The latest CDO at the time of this writing is version 6.5.8165.0, released on 4/28/2010. You can always obtain the latest CDO here:

http://www.microsoft.com/en-us/download/details.aspx?id=1004

CDO does not need to be installed on any other machine than the one running Add2Exchange.

UAC Disabled

User Account Control on the Add2Exchange server must be disabled. Directions for disabling UAC are here:

http://www.petri.co.il/disable_uac_in_windows_vista.htm

Only the registry key method has been tested. On Windows Server 2008 R2 the MSConfig tool looks different than in the article, and it has not been verified whether using that tool actually disables UAC to the extent required by Add2Exchange. It is strongly suggested that you use the registry key method.

Disabling UAC requires a reboot of the server. If you are also installing the Exchange 2010 Update Rollup 3 on the same server, you may wish to do both, then reboot once. Make sure to update all other Exchange 2010 servers prior to rebooting.

Exchange Server Throttling Policy

New policies in Exchange 2010 limit the rate at which clients can make requests. As Add2Exchange makes a larger volume of requests than a normal client, it needs to have ExchangeG##s so-called throttling policy relaxed. This applies only to the Add2Exchange service account.

Exchange Server Address Book Connections

Exchange 2010 also limits the number of Address Book connections that can be made in total. This limit needs to be raised for Add2Exchange. This is a global configuration on the server.

Installation Instructions

Exchange 2010 Update Rollup 3

  1. Read the Description of Update Rollup 3 for Microsoft Exchange Server 2010 Release to Manufacturing at: http://support.microsoft.com/?kbid=981401
  2. Install the Update Rollup 3 on all Exchange 2010 servers, respecting the order of installation in the description document
  3. Reboot all Exchange servers in the organization, including Exchange 2003 and 2007 servers
  4. Verify correct operation of your servers

Disable UAC

  1. Select the server on which you will be installing Add2Exchange
  2. Disable UAC using the registry method provided at: http://www.petri.co.il/disable_uac_in_windows_vista.htm
  3. Reboot the server

Make the Add2Exchange Service Account

If you already have a service account, make sure the permissions match this configuration. You do not need to match the name of the account, but we will use zAdd2Exchange as the service account name in these examples for clarity.

  1. Using Exchange Management Console, create an account and mailbox named zAdd2Exchange
  2. Add the account to the Administrators group
  3. Verify that the account is not a part of the Domain Administrators group
  4. Verify the account by logging in with it
  5. Open the zAdd2Exchange mailbox using OWA or Outlook (if using Outlook, do not save the password)

Assign Rights in Exchange to the Add2Exchange Service Account

  1. Assign the account Owner permission over all public folders involved in synchronization
  2. Verify that Add2Exchange users have Read and Visible permissions to public folders involved in synchronization

In Exchange Management Shell, run the following commands (substitute your account name for zAdd2Exchange):

Get-MailboxDatabase | Add-ADPermission -User "zAdd2Exchange" -AccessRights ExtendedRight -ExtendedRights Receive-As, ms-Exch-Store-Admin
Add-RoleGroupMember "View-Only Organization Management" -Member "zAdd2Exchange"

Next:

  1. Open Active Directory Users and Computers
  2. Select the View menu
  3. Make sure Advanced Features is selected
  4. Right-click the domain name or organizational unit which contains all of the users with mailboxes, usually Users
  5. Select Properties
  6. Select the Security tab
  7. Click Advanced
  8. Select Add
  9. Enter zAdd2Exchange (or your account name, if different)
  10. Select OK
  11. When the permissions dialog appears, select User Objects or, on Server 2008, Descendant User Objects from the Apply onto: dropdown
  12. In the permissions box, scroll down and select Allow for Send As
  13. Click OK
  14. Click OK to exit
Note
If you need to add top-level public folders to the store then you must add the zAdd2Exchange account to the Public Folder Management role group. You could also create the folders from an account already in this role group.
Note
If you want to be able to make user accounts with mailboxes from the zAdd2Exchange account, make the account a members of the Organization Management group of Exchange. If you make this change while logged on as the zAdd2Exchange account, donG##t forget to log off and back on as the zAdd2Exchange account in order for these changes to take effect.

Throttling Policy

Still in Exchange Management Shell, run the following commands:

New-ThrottlingPolicy A2EPolicy
Set-Mailbox "zAdd2Exchange" -ThrottlingPolicy A2EPolicy

Address Book Connections

  1. On the CAS server, go to C:\Program Files\Microsoft\Exchange Server\V14\Bin (use the appropriate drive)
  2. Edit the file microsoft.exchange.addressbook.service.exe.config
  3. Change the value MaxSessionsPerUser to 100000
  4. Save the file
  5. Restart the Address Book Service

Add2Exchange Installation

Install Add2Exchange under the service account as usual. Instructions are at:

http://guides.diditbetter.com/a2e-guide/manual_exchange_2007_and_2010_configuration.htm

Applies To

  • Exchange 2010
  • Windows Server 2008 R2
  • Add2Exchange Enterprise
  • Add2Exchange Standard

Tags: exchange_2010, installation

|

Website and materials copyright 2008-2014, all rights reserved DidItBetter.com Software. US: 800-837-8636 Intl: 001-813-977-5739

DidItBetter.com Software specializes in Exchange Sync and Hosting, Outlook Task Management and CRM solutions.