Outlook 2003 and Exchange Server 2010 'Common Client Access Considerations'

There’re several scenarios for consideration when deploying Exchange Server 2010 into an environment where Outlook 2003 is used. “Most of these scenarios have been documented prior to product release and some applied to previous versions. This document introduces some of scenarios and articles that’ll resolve these issues. If you’re planning a deployment of Exchange Server […]

There’re several scenarios for consideration when deploying Exchange Server 2010 into an environment where Outlook 2003 is used. “Most of these scenarios have been documented prior to product release and some applied to previous versions. This document introduces some of scenarios and articles that’ll resolve these issues. If you’re planning a deployment of Exchange Server 2010, understanding client configuration, and requirements & capabilities of your organization are of importance to user experience. Primarily field office environments or environments where users aren’t joined to domain, profile distribution, or ability or inability to enforce policies or distribute the solutions will dictate how you address the issue. This’s 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 Exchange Server - encryption between Client & Server is enabled, by Default. This’s RC4 encryption - where client negotiates encryption level based on client operating system's capabilities - up to 128-bit encryption,”. This’s documented in following topic in TechNet online:

More info: Common Client Access Considerations for Outlook 2003 and Exchange 2010