Update 6/13/13: we added a known issue with transport rules to the blog post below.
Today the Exchange CXP team released Update Rollup 1 for Exchange Server 2010 SP3 to the Download Center.
Note: Some of the following KB articles may not be available at the time of publishing this post.
This update contains fixes for a number of customer-reported and internally found issues. For more details, including a list of fixes included in this update, see KB 2803727. We would like to specifically call out the following fixes which are included in this release:
- 2561346 Mailbox storage limit error when a delegate uses the manager’s mailbox to send an email message in an Exchange Server 2010 environment
- 2756460 You cannot open a mailbox that is located in a different site by using Outlook Anywhere in an Exchange Server 2010 environment
- 2802569 Mailbox synchronization fails on an Exchange ActiveSync device in an Exchange Server 2010 environment
- 2814847 Rapid growth in transaction logs, CPU use, and memory consumption in Exchange Server 2010 when a user syncs a mailbox by using an iOS 6.1 or 6.1.1-based device
- 2822208 Unable to soft delete some messages after installing Exchange 2010 SP2 RU6 or SP3
For DST changes, see Daylight Saving Time Help and Support Center (microsoft.com/time).
A known issue with Exchange 2010 SP3 RU1 Setup
You cannot install or uninstall Update Rollup 1 for Exchange Server 2010 SP3 on the double-byte character set (DBCS) version of Windows Server 2012 if the language preference for non-Unicode programs is set to the default language. To work around this issue, you must first change this setting. To do this, follow these steps:
- In Control Panel, open the Clock, Region and Language item, and then click Region.
- Click the Administrative tab.
- In the Language for non-Unicode programs area, click Change system locale.
- On the Current system locale list, click English (United States), and then click OK.
After you successfully install or uninstall Update Rollup 1, revert this language setting, as appropriate.
We have identified the cause of this problem and plan to resolve it in a future rollup, but did not want to further delay the release of RU1 for customers who are not impacted by it.
A known issue with transport rules after E2010 SP3 RU1 is installed
We have an issue where the messages stick in poison queue and transport continually crashes after this rollup is applied.
We have gathered enough information and have determined the issue. Specifically, the issue is caused by a transport rule (disclaimer) attempting to append the disclaimer to the end of HTML formatted messages. When this occurs, messages will be placed in the poison queue and the transport service will crash with an exception. We are investing resources to develop a code fix. You can either disable or reconfigure the disclaimer transport rule.