There are several scenarios for consideration when deploying Exchange Server 2010 in an environment where Outlook 2003 is used. Most of these scenarios have been documented prior to the product release and some applied to previous versions. However, in a review of support cases, we've found that they have not been used prior to contacting Microsoft.
This post introduces some of the scenarios and the articles that will resolve these issues. If you're planning a deployment of Exchange 2010, understanding client configuration and the requirements and capabilities of your organization are of importance to the user experience. Primarily field office environments or environments where users are not joined to the domain, profile distribution, or the ability or inability to enforce policies or distribute the solutions will dictate how you address the issue.
This is a top support issue for Outlook 2003 access to Exchange 2010.
Note: In Exchange 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 RPC encryption. However, any CAS servers deployed prior to SP1, 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 2010/2007 and any CAS server as RPC communication for these Outlook versions will remain encrypted.
Exchange 2010 introduces additional "out of the box" security for client communications with 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 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 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:
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 Microsoft Knowledge Base article 2006508: Outlook connection issues with Exchange 2010 mailboxes because of the RPC encryption requirement
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. For more details about the issue and two possible resolutions for the organization, see In Outlook 2003, e-mail messages take a long time to send and receive when you use an Exchange 2010 ...
Update 1/28/2010: UDP notification support has been added to Exchange 2010, and will be available in Exchange 2010 SP1 Update Rollup 3, slated for March 2011. For details, see UDP Notification Support Re-added to Exchange 2010.
Directory access has changed in the Exchange Server 2010 world. The TechNet topic Understanding the Address Book Service introduces the changes and is currently being updated with more information.
A future topic will cover this in more detail.
Outlook 2003 uses the Public Folders free/busy messages to determine availability in the Calendar and as the source for Offline Address Book (OAB) synchronization. If Public Folders are not configured during Exchange 2010 setup, OAB 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 2010, users will encounter the issue mentioned in Users who use Outlook 2003 cannot publish their free/busy data in Exchange Server 2010 or in Exchang...
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"
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
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).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.