Microsoft has released Update Rollup 1 for Exchange Server 2010 Service Pack 3.

From the Microsoft Exchange Team blog:

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

Note also the following known issue:

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:

  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.

Download Update Rollup 1 for Exchange Server 2010 SP3 here.

Deploying Exchange Server 2010 SP3 Update Rollup 1

The standard order of deployment for Exchange Server updates applies.

  1. Client Access servers, starting with the internet-facing ones. See this article for how to patch a CAS array.
  2. Hub Transport and Edge Transport servers
  3. Mailbox servers. See this article for how to patch a Database Availability Group.
  4. Unified Messaging servers

About the Author

Paul Cunningham

Paul is a former Microsoft MVP for Office Apps and Services. He works as a consultant, writer, and trainer specializing in Office 365 and Exchange Server. Paul no longer writes for


  1. Carol Ostos

    Hey Paul, quick question, are you aware of any issues if all Exchange Servers in an organization are not at the same version? For example, our servers are still running EX2010 SP2 RU2 but just noticed one of our offices has introduced new servers and they have installed EX2010 SP3, Should we be worried about this? I mean we were not sure about SP3 but something tells me the ideal scenario is to have the same version across all servers in an organization. Appreciate your thoughts on this!! Cheers

    1. Carol Ostos

      and if we are forced to upgrade to SP3, can we go from SP1 RU2 to SP3? or would we have to apply SP2 and then SP3?

        1. Avatar photo
          Paul Cunningham

          For one thing it means that other site has updated your AD Schema for Ex2010 SP3. Whether that is a concern for you and your normal change control procedures I don’t know 😉

          Orgs can run on mixed versions of Exchange. The general rule is that the internet-facing site (ie the internet-facing CAS) needs to be the highest version. This is so that the internet-facing CAS can proxy connections for OWA/ActiveSync/etc to the internal CAS in the appropriate site.

          Yes you can go directly from one SP to another without installing the SP’s or UR’s in between.

  2. Michael A

    I tried to install Rollup 1 for SP3 and I keep getting a 1603 error. I verified that set-executionpolicy is “undefined” for all items, but it still doesn’t install.

    1. SUF


      What I realized, I cannot install it when I just double click on the msp package but it works from elevated command prompt with the following command:

      msiexec /update Exchange2010-KB2803727-x64-en.msp

      I hope this helps.

      1. Astage

        Most grateful thanks for this – just spent a couple of nights bashing my head against this wall!

Leave a Reply