Exchange 2010 SP3 RU16 Released

Today heralded the arrival of Rollup Update Rollup 16 (RU16) for Exchange Server 2010 Service Pack 3.  RU16 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 RU22 was released for that version of Exchange.

Exchange 2010 SP3 RU16 Download

This is build 14.03.0339.000  of Exchange 2010, and KB 3184730 has the full details for the release.  The update file name is Exchange2010-KB3184730-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


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 (11)

  1. Samim Shaikh says:

    Exchange environment supporting for our client is Exchange 2010 SP3 RU14. Planing to install RU16 as part of 3 month maintenance activity. Does any one installed or tested RU 16 or have any feedback ?

    1. Jacob Suzelle says:

      Hello Folk,

      Recently i have upgraded to RU 16…. No hiccups till now

      1. Samim Shaikh says:

        Thanks for your feedback… We are planning to move from RU14 to 16

  2. Devendra Desai says:

    Exchange environment supporting for our client is Exchange 2010 SP3 CU8. Planing to install CU16 .
    How we can proceed.. can I update directly from CU 8 to CU 16
    have any feedback ?

    1. Samim Shaikh says:


      Are you asking about RU or CU…… RU is available for Exchange 2010.

      1. Correct. Exchange 2007 and 2010 are serviced via RUs. 2013 onwards uses CUs.

        Note though that the Exchange 2007/2010 RU line is cumulative for the service pack it services. Since they are already on SP3 (as they must be) they can go direct to the latest RU.

        With 2007/2010 there is a two step install – SP plus the latest RU.

        With 2013/2016 just install the latest CU. One step. Done.


        1. Devendra Desai says:

          Correct, I’m talking about Exchange 2010 SP3 RU16,
          Planing to install RU16 .
          How we can proceed.. can I update directly from RU 8 to RU 16

        2. Samim Shaikh says:


          I have query about exchange 2010 SP3 Rollup 16…. We have DAG member of 4 spanned at 2 different data center.

          (Primary Data center 2 MBX & Secondary Data center 2 MBX)

          With some reason we are unable to patch RU 16 on secondary data center and RU 16 patching completed at Primary data center.

          Overall : Primary data center : 2 MBX with RU 16
          Secondary DC : 2 MBX with RU 14.

          Post fail activity of patching RU 16 we noticed that Patched MBX DB’s are note replicating from Secondary DC RU 14 MBX server.
          error are :

          IncomingLogCopyingNetwork : {Sxxxxxxx,DAGNetwork02-DAG_Replication,An error occurred while communicating with s
          erver ‘SGISGEX08’. Error: Unable to read data from the transport connection: A conne
          ction attempt failed because the connected party did not properly respond after a pe
          riod of time, or established connection failed because connected host has failed to

          DBLogCopyKeepingUp *FAILED* Failures:…

          Please can you suggest due to unbalanced Rollup version of exchange can cause the issue of replication or what other issue we can face.

          Microsoft recommend to have all server MBX/HT/CAS at same level of patch / roll up but due to some difficulties we are forced to cancel rest two server to patch and apart from this all fronted and cas server are RU 16.

          1. Ideally all will be at the same build level Samim, though I would be surprised that this would cause this issue. No impossible, but not expected behaviour.

            Ensure that any server restart has not applied any other changes, such as unwanted GPO or AV settings etc.


  3. Simon Blixt says:

    I do not find this in my Windows Update after updating to RU 15, how “critical” is this one?

    1. Depends on the environment Simon.

      If you are in hybrid remember the support policy in that case is N and N -1 for updates.
      Now that SP3 RU17 is out, that may require an upgrade for you


Skip to main content