We're an Exchange 2003 (in a 2008 R2 schema AD forest) shop. We have Exchange running on a single cluster composed of two nodes.
We have random instances where there are users who, when using Outlook 2010 to connect to their mailbox, Outlook crashes as soon as it completes loading. This occurs regardless of:
Office location/proximity to the cluster
With or without Cached Exchange Mode
With Outlook 2010 in regular or safe mode
Regardless of Outlook Authentication or Encryption Setting
From any system in our organization - built from scratch or from a corporate deployment
With out any other connections in the profile (ie, IMAP to another server, or a MAPI Livemeeting plugin)
However, with Outlook 2007, there are no issues at all, and the user can work without issue.
I haven't seen any authentication issues for that user logged in our exchange server, and the error logged in the local application event log is as follows:
Log Name: Application
Source: Application Error
Date: 8/31/2010 1:55:44 PM
Event ID: 1000
Task Category: (100)
Faulting application name: OUTLOOK.EXE, version: 14.0.4760.1000, time stamp: 0x4ba8fefd
Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdadb
Exception code: 0xc0000374
Fault offset: 0x000c283b
Faulting process id: 0x12e8
Faulting application start time: 0x01cb494ed8061f9e
Faulting application path: C:\Program Files\Microsoft Office\Office14\OUTLOOK.EX
Faulting module path: C:\Windows\SYSTEM32\ntdll.
Report Id: 1ef19a24-b542-11df-a34a-00
<Provider Name="Application Error" />
<Data>C:\Program Files\Microsoft Office\Office14\OUTLOOK.EX
We're at the point where we're about to export the users' mailbox to a PST file, delete the mailbox, and re-create it. However, I don't see this as a feasible option for tens, or hundreds of users (we're just beginning to push out Win7 and Outlook 2010).