Prepare client side environment to Upgrade from Exchange 2003/2007 to Exchange 2010

For Environment with high percentage of clients are using Outlook 2003, and because there are some common client access considerations for outlook 2003 and Exchange 2010, then some preparations on client side should be done to cover all considerations as the following:


Exchange 2010 includes additional “out of the box” security for Client communications to the Exchange Server which is encryption between the Client and the Server which is enabled by default, for more information

Prior to Outlook 2007, encryption was not enabled on the Client side, by default, however if profile for Outlook 2007 exist where encryption is disabled, or if Outlook 2003 profiles created with default settings are used with Exchange Server 2010, the connection will fail when Outlook attempts to connect to an Exchange Server 2010 mailbox, One or more of the following common error message will be displayed:

· Cannot start Microsoft Office Outlook. Unable to open the Outlook window. The set of folders could not be opened.

· Unable to open your default e-mail folders. The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.

· The connection to the Microsoft Exchange Server is unavailable. Outlook must be online or connected to complete this action.

· Unable to open your default e-mail folders. The information store could not be opened.

· Outlook could not log on. Check to make sure you are connected to the network and are using the proper server and mailbox name. The connection to the Microsoft Exchange Server is unavailable. Outlook must be online or connected to complete this action.

There are several methods to work around this issue, from immediate manual change by the administrator or the user, to deployment of administrative templates or new profiles, each of these scenarios are documented in the following article:


In Exchange Server 2010 Service Pack 1, the RPC encryption requirement has been disabled, by default. Any new Client Access Servers (CAS) deployed in the organization will not require encryption. However, any CAS servers deployed prior to Service Pack 1, or upgraded to Service Pack 1, will retain the existing RPC encryption requirement setting. Also bear in mind disabling the RPC encryption requirement on a CAS server won't lower the security between Outlook 2007/2010 and any CAS server as RPC communication for these Outlook versions will remain encrypted.


It is recommended to apply Outlook Encryption Administrative template through GPO as described in Microsoft KB Article to enable Outlook RPC Encryption on all existing Outlook 2003 clients.


New Mail Notifications and UDP

Exchange 2010 no longer supports UDP for new mail notifications. However, Outlook 2003 relied primarily upon UDP notifications to display new messages and changes to folders. The result is that Outlook 2003 users will see delays in updates to folders and the Send/Receive process appears to take a long time.

The following article discusses the issue and two possible resolutions for the organization

The two available workarounds for this issue are as the following:

· Install Update Rollup 1 for Exchange 2010.

· User cached mode with outlook 2003 profile.


It is recommended to update all clients Outlook profile to use Cashed Mode.

Public Folder, Offline Address Book and Free/Busy

Outlook 2003 uses the Public Folders free/busy messages to determine availability in the Calendar and as the source for Offline Address Book synchronization. If Public Folders are not configured during Exchange Server 2010 setup, Offline Address Book and Free/Busy will not be available to Outlook 2003 users. These users will encounter connection errors.

If free/busy Public Folders folder is not replicated to Exchange Server 2010, users will encounter the following

The following error message will be displayed if no public folder replicas for free/busy information were on Exchange 2010:

“0x8004010F” Error message:

· When outlook synchronizes an offline address book with Exchange Server 2007 and Exchange Server 2010, this if clients inside the organization or connected via VPN/RAS, and the organization uses a Proxy server, the Client Access Server should be listed in the “Bypass proxy server for local addresses” configuration

· When try to synchronize address list on an Exchange Server while using Outlook 2003

Opening Additional Mailboxes

Opening other user’s folders or mailboxes are a common operation in the enterprise, Outlook 2003 users may encounter issues if the environment is not properly prepared for this use the following:

· Office Outlook 2003 does not connect to two or more additional mailboxes in a mixed Exchange 2007 and Exchange Server 2010 environment

· An error occurs when an Exchange server 2003 user tries to open more that delegate mailboxes of Exchange Server 2010 in Outlook 2003


It is recommended to upgrade all Outlook 2007 to Outlook 2007 Service Pack 2 or higher;EN-US;924470.

RPC over HTTP Connectivity

The following article discusses issues with Outlook 2003 connectivity when the RPC proxy server extensions do not load correctly, and this article applied to Exchange 2010 connections


If the mentioned error shown while migration pilot one of the proposed solution will be tested to solve the issue.

Unified Communication

Integration features between Outlook 2003 and Office Communicator and functionality with Office Communication Server have been documented in the following documents:

· The presence information for a Communications Server user may not appear, or may appear intermittently, in Outlook 2003 Service Pack 2 or in Outlook 2007

· Communicator does not update the free/busy information as scheduled


It is recommended to follow the solutions in KB article “” to avoid the related presence issue, also it is recommended to upgrade all Outlook 2003 clients to Outlook 2003 Service Pack 3 because Outlook 2003 Service Pack 2 is no longer supported, this beside apply Outlook 2003 fix that will solve some Outlook issues as listed in the KB article.


Related Posts:

Transition Process to Upgrade from Exchange 2007 to Exchange 2010:

Comments (6)

  1. Maged Ezzat says:

    The upgrade process itself is not a big deal what you should take care about is the environment preperation in both Server side and client side and the transition & co-existance between old Exchange 2003/2007 and Exchange 2010 which is the practical situation in most of Exchange environment that Mailbox Move sometimes could not be done in one shot, see Transition Process to Upgrade from Exchange 2007 to Exchange 2010:…/high-level-transition-process-to-upgrade-from-exchange-2007-to-exchange-2010.aspx

  2. Frank Bicocchi says:

    I had just performed an exchange 2003 to exchange 2010 migration. First off, this went flawless! I was so happy with the outcome. As many of you know, Exchange 2010 requires 64 bit OS. THEREFORE, I started the projected by creating a new 64-bit Windows 2008 enterprise server and a new windows 2008 64 bit enterprise domain controller in an existing 2003 active directory environment. First, let me say that you have to run adprep off the 2008 cd on your DC that holds your fsmo roles. I installed exchange 2010 and brought up a new BES 5.0.2 server as I thought this would be an excellent time to refresh corporate blackberry users. I love this version of exchange! I was running co-existence mode until the migration was complete and then I uninstalled exchange 2003 from my environment and retired that old clunky exchange server. Let me say that despite the noise about making your client access and mailbox role a VM. I had no issue doing this, as I am a huge VMware and virtualization fan. I have had no issue with my cas, hub, and mailbox roles all in one VM with zero performance issues. One thing I do not like is that by design store.exe is now a memory hog! However, there are parameters that you can use in adsiedit.msc where you can limit the memory usage of store.exe that work great! All in all the only complaint I got was from the helpdesk, as they cannot install Exchange management tools on their desktops because they run 32 bit OS. I told them to upgrade their desktop OS to 64 bit so they can run the tools. I know they make some third party management tools that allow your helpdesk to still perform common exchange tasks but I am NOT a big third party fan. If anyone has any questions about more details about my migration from exchange 2003 to 2010 I will be more than happy to answer them. In addition, when you plan your exchange 2010 rollout one big thing to remember here is give yourself plenty of space for the info store lun as exchange 2010 does NOT like to have less than 2 gb free space of the store lun or luns. If it goes below 2 GB mail will stop flowing and will not flow again until you free up some space.

    Frank Bicocchi

  3. Anonymous says:

    Microsoft Exchange Server 2003 entered the market on September 28, 2003 and continued the great messaging

  4. Anonymous says:

    Pingback from Exchange 2003 migration toolkit | The Exchange Tube

  5. Anonymous says:

    Pingback from Exchange 2003 migration toolkit | The Exchange Tube

Skip to main content