I was speaking with some of our system engineers recently and the topic of Outlook/Exchange 2010 issues quickly became a hot topic. It is important that the version of Outlook is given consideration when planning an Exchange 2010 deployment. Although Outlook 2003 is a supported client for Exchange 2010 there is a number of issues which have been identified. Thankfully our unified communications experts provided me this roll call of common support issues and workarounds. I will keep you posted on any developments but keep in mind Office 2003 mainstream support ended long ago…
This is a top support issue for Outlook 2003 access to Exchange 2010.
Exchange Server 2010 introduces additional “out of the box” security for Client communications to the Exchange Server - encryption between the Client and the Server is enabled, by Default. This is RC4 encryption – where the client negotiates the encryption level based on the client operating system’s capabilities – up to 128-bit encryption. This is documented in the following topic in TechNet online:
Understanding RPC Client Access
Prior to Outlook 2007, encryption was not enabled on the Client side, by default. However, if profiles 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 messages 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 is documented in the following article from the Microsoft Knowledge Base:
Outlook connection issues with Exchange 2010 mailboxes because of the RPC encryption requirement
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:
In Outlook 2003, e-mail messages take a long time to send and receive when you use an Exchange 2010 mailbox
Address Book Service (Directory Access)
Directory access has changed in the Exchange Server 2010 world. The following TechNet topic introduces the changes and is currently being updated with more information.
Understanding the Address Book Service
A future topic will cover this in more detail.
Public Folders, 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:
Users who use Outlook 2003 cannot publish their free/busy data in Exchange Server 2010 or in Exchange Server 2007
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.
Error message when Outlook synchronizes an offline address book with Exchange Server 2007 and Exchange Server 2010: “0x8004010F”
Also, if there are missing address book list objects or missing or incorrect address lists, the following may occur:
An error occurs when you try to synchronize the offline address list on an Exchange Server server while you are using Outlook 2003: “0x8004010F”
Opening Additional Mailboxes
Delegate Access issues, 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 their use:
Office Outlook 2003 does not connect to two or more additional mailboxes in a mixed Exchange Server 2007 and Exchange Server 2010 environment
An error occurs when an Exchange server 2003 user tries to open more than one delegate mailboxes of Exchange Server 2010 in Outlook 2003
RPC over HTTP Connectivity
The following article discusses issues with Outlook 2003 connectivity when the RPC proxy server extensions do not load correctly. This article also applies to Exchange Server 2010 connections.
Error message when Outlook 2003 users connect to an Exchange server by using RPC over HTTP: “Server Unavailable”
Integration features with Office Communicator and functionality with Office Communications 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
*Note: This functionality is not available to Outlook 2003/Exchange Server 2003 users, as the Availability Service functionality is required for both the client and the Exchange Server. The only method to obtain this functionality is to upgrade both the client and the server(s).