Exchange 2010 SP3 RU17 Released

March 21st heralded the arrival of Rollup Update Rollup 17 (RU17) for Exchange Server 2010 Service Pack 3.  RU17 is the latest rollup of customer fixes available for Exchange Server 2010.  All updates are delivered via a RU for Exchange 2010 and 2007.  Exchange 2013 and 2016 have a different release model, where security updates are decoupled from the standard cumulative updates.

To update Exchange 2007, SP3 RU23 was released for that version of Exchange.  This will be the last update for Exchange 2007, as it will transition out of support of the 11th of April 2017.  Goodbye my old friend!  Now let us return our scheduled programming….

Exchange 2010 SP3 RU17 Download

This is build 14.03.0352.000  of Exchange 2010, and KB 4011326 has the full details for the release.  The update file name is Exchange2010-KB4011326-x64-en.msp

Note that this is only for the Service Pack 3 branch of Exchange 2010.  Why?  Exchange 2010 SP2 exited out of support on the 8th of April 2014 and will no longer receive updates.  Customer must be on Exchange 2010 SP3 to receive updates.

Also note that Exchange 2010 transitioned into its Extended product support lifecycle phase on the 13th of January 2015.  Exchange 2010 will now be serviced as per the extended support policy.

Issues Resolved

Updated DST time zone information


KB 4014076 Migration ends and errors reported when you on-board or off-board a mailbox through Exchange Online in an Exchange Server 2010 hybrid environment

KB 4014075 UNC path does not open in OWA when the path contains non-ASCII characters in an Exchange Server 2010 environment

KB 4013917 You cannot search in a shared mailbox through OWA in an Exchange Server 2010 Service Pack 3 (Update Rollup 15 or 16) environment

KB 4012911 Culture element is added in the wrong order when you use the ResolveNames operation in EWS in Exchange Server 2010

Important Notes

The below are the normal notes to consider before deploying an Exchange RU.  In this case, the below must also be tempered with the fact that there are security fixes.

There are a couple of items to mention:

  • Test the update in your lab before installing in production.  If in doubt test…
  • Ensure that you consult with all 3rd party vendors which exist as part of your messaging environment.  This includes archive, mobility and management services.
  • Ensure that you do not forget to install updates on management servers, jump servers/workstations and application servers where the management tools were installed for an application.  FIM and 3rd party user provisioning solutions are examples of the latter.
  • If the Exchange server does not have Internet connectivity then this introduces significant delay in building the Native images for the .Net assemblies as the server is unable to get to  To resolve this issue, follow these steps:
    1. On the Tools menu in Windows Internet Explorer, click Internet Options, and then click the Advanced tab.
    2. In the Security section, click to clear the Check for publisher’s certificate revocation check box, and then click OK.

    We recommend that you clear this security option in Internet Explorer only if the computer is in a tightly controlled environment. When setup is complete, click to select the Check for publisher’s certificate revocation check box again.

  • Install the update from an elevated command prompt
  • Ensure that the Windows PowerShell Script Execution Policy is set to “Unrestricted” on the server being upgraded or installed.  See KB981474.
  • Update Internet facing CAS servers first
  • Backup any OWA customisations as they will be removed
  • Uninstall any Interim Updates (IUs) before installing the RU.  You will have received these private files directly from Microsoft.
  • Disable file system antivirus prior to installing the RU.
  • Restart server after RU has been installed and then re-enable file system antivirus
  • Test (yes, technically this is in here for a second time but it is very important!)




Comments (13)
  1. Jason Davis says:


    Do you have any idea why RU for Exchange 2007 and 2010 do not show up in Windows Update any longer? This happened after EX2K10 RU15 and RU21 for EX2K7….

    1. Not something I have looked into Jason. Though it *may* be related to the fact that RU15 was the last security update RU for Exchange 2010.


      1. Jason Davis says:

        Thanks so much for the response…that would make sense. I plan on downloading the packages separately anyways but that is an interesting thought. I’ll not do that on a couple of SBS 11 boxes I have out there and wait for the next security related RU to be released and go from there!

        Thanks Again!

        1. I went looking this morning – you should be seeing this in MU at the end of this month.


          1. This is now present on my lab WSUS server.


  2. Olivier says:

    Hello Roderick,
    I put the update KB4011326 on a Windows 2008 R2 server that come to version 14.03.351.000.
    I also put the same update KB4011326 on a Windows 7 pro x64 that come to version 14.03.352.000.
    Now, because of this difference in version number, i’m not able anymore to remotly connect the server with EMC from the Windows 7.
    Any idea ?

    1. Hi Oliver, not something directly observed. If this repros from a fresh install of Windows 7, then I would get a case open so this can be tracked.

      Curious if it still happens if the Windows Profile is rebuilt to remove any cached data.


    2. Joe Lynch says:

      Olivier, I have observed the same problem: it seems that the build numbers are different between the downloadable MSP (14.3.352) and the WSUS/MU version (14.3.351). I’d manually upgraded everything with the MSP apart from one jump server which upgraded via WSUS approval, and that jump server is the only system to have this problem.

  3. Marc Bauer says:

    Since we upgraded from RU11 to RU17 we expierence a very annoying issue. People permanently get undelivery messages with an error message:

    #550 5.6.0 CAT.InvalidContent.Exception: InvalidCharsetException, Character set name (cp-850) is invalid or not installed.; cannot handle content of message with InternalId

    How can we get rid of this? I already followed but no success. I configured the version to sp3, not the RU version. I tried with fallback language “en” and “de”. The undelivery errors seems to be caused by spam with encoding issues.

    I have seen such a bug was already fixed in past in an sp1 RU. Any idea how to proceed now?

    1. Hi Marc,

      I would start by raising a CSS support case with us, so that we can triage this as necessary.


      1. Marc Bauer says:

        What type of support is this? I can open a single incident case, but as you may know these guys are totally incompetent and it may take a year to get to second level.

  4. Jerry says:

    Hi Rhoderick, can an AD schema upgrade to Windows Server 2016 be done manually through command prompt without actually introducing new 2016 DCs and without breaking Exchange 2010? I understand the 2016 DCs aren’t supported but not sure if extending the schema is. I need this for a new AD FS 2016 Farm. If not, are there any plans to allow this with a future update rollup? Thank you.

  5. Sally Peters says:

    I installed RU 18. I had previously installed 15-16 but not 17. I am having an issue now with connectivity. The RU broke autodiscover, ecp and Outlook 2016. ugh. We have 2016 OL and 2013OL. I am going to remove RU18 and see if I can get it working again. I hate when updates break things.

Comments are closed.

Skip to main content