Released: Exchange Server 2010 SP3 Update Rollup 1

Released: Update Rollup 1 for Exchange Server 2010 SP3

By The Exchange Team

Today the Exchange CXP team released the Update Rollup 1 for Exchange Server 2010 SP3 (KB 2803727) to the Download Center.

Update Rollup 1 for Exchange Server 2010 SP3

This update contains a number of customer reported and internally found issues. In particular we would like to specifically call out the following fixes which are included in this release:

Note: Some of the following KB articles may not be available at the time of publishing this post.

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: http://www.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 a computer that is running 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:

  1. In Control Panel, open the Clock, Region and Language item, and then click Region.
  2. Click the Administrative tab.
  3. In the Language for non-Unicode programs area, click Change system locale.
  4. 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.

Exchange Team

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s