We are having an issue with the delegatesentitemsstyle in Office 2007 (SP2 + KB970944) on Windows Server 2008 R2 (RDS).
Until several weeks ago it seems that Outlook was correctly moving items 'sent as' another user from the sending users' Sent Items folder to the Sent Items folder of the person that they were impersonating. Now emails sent as another user are simply sitting in the sending users' own Outbox and are not being moved even when a manual send/receive is invoked (as suggested byhttp://support.microsoft.com/kb/972148 as Outlook on RDS isn't using Cached Exchange mode).
Having looked through the logs it seems that several updates were applied to the server between the last known successful move and the start of the emails being queued in the users' own Outbox:
- Update for Microsoft Office Outlook 2007 Junk Email Filter (KB2492475)
- Security Update for Windows Server 2008 R2 x64 Edition (KB2475792)
- Security Update for Windows Server 2008 R2 x64 Edition (KB2479628)
- Update for Windows Server 2008 R2 x64 Edition (KB2467023)
- Security Update for Windows Server 2008 R2 x64 Edition (KB2393802)
- Update for Windows Server 2008 R2 x64 Edition (KB2454826)
- Cumulative Security Update for Internet Explorer 8 for Windows Server 2008 R2 x64 Edition (KB2482017)
- Update for Windows Server 2008 R2 x64 Edition (KB2487426)
- Security Update for Microsoft Office Visio 2007 (KB2434737)
- Security Update for Windows Server 2008 R2 x64 Edition (KB2425227)
- Windows Malicious Software Removal Tool x64 - February 2011 (KB890830)
- Security Update for Windows Server 2008 R2 x64 Edition (KB2485376)
I am still in the process of working through these to try and ascertain which update, if any, may have caused the issue. I was hoping that someone else may have encountered this issue and save me the work! :)
So far I have uninstalled and reinstalled Office 2007, reinstalled SP2 and the hotfix but I have had no luck (I was hoping to rule out an Office update).
Additionally at about that time we migrated from Exchange 2007 SP3 to Exchange 2010 SP1. It is possible that the issue is with the Exchange migration but as I have not seen mention of it elsewhere I am covering my bases.
Any assistance gratefully received...