Blog Post

Exchange Team Blog
2 MIN READ

Released: Update Rollups for Exchange 2007 & Exchange 2010 and Security Updates for Exchange 2013

Ross Smith IV's avatar
Ross Smith IV
Former Employee
Aug 13, 2013

Update 8/14/13: Due to an issue with the Exchange 2013 Security Update installation process, the Exchange 2013 updates have been removed from the Download Center. For more information, please see Exchange 2013 Security Update MS13-061 Status Update.

Today, Exchange Servicing released several updates for the Exchange product line to the Download Center:

  • Update Rollup 11 for Exchange Server 2007 SP3
  • Update Rollup 7 for Exchange Server 2010 SP2
  • Update Rollup 2 for Exchange Server 2010 SP3
  • Exchange Server 2013 RTM CU1 MSRC Security bulletin MS13-061
  • Exchange Server 2013 RTM CU2 MSRC Security bulletin MS13-061

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

Exchange 2007 Rollups

The Exchange 2007 SP3 RU11 update contains two fixes in addition to the changes for MS13-061. For more details, including a list of fixes included in this update, see KB 2873746 and the MS13-061 security bulletin. We would like to specifically call out the following fixes which are included in this release:

  • 2688667 W3wp.exe consumes excessive CPU resources on Exchange Client Access servers when users open recurring calendar items in mailboxes by using OWA or EWS
  • 2852663 The last public folder database on Exchange 2007 cannot be removed after migrating to Exchange 2013 

Exchange 2010 Rollups

The Exchange 2010 SP2 RU7 update contains the changes for MS13-061.  For more details, see the MS13-061 security bulletin.

The Exchange 2010 SP3 RU2 update contains fixes for a number of customer-reported and internally found issues, as well as, the changes for MS13-061. For more details, including a list of fixes included in this update, see KB 2866475 and the MS13-061 security bulletin. We would like to specifically call out the following fixes which are included in this release:

  • 2861118 W3wp.exe process for the MSExchangeSyncAppPool application pool crashes in an Exchange Server 2010 SP2 or SP3 environment
  • 2851419 Slow performance in some databases after Exchange Server 2010 is running continuously for at least 23 days
  • 2859596 Event ID 4999 when you use a disclaimer transport rule in an environment that has Update Rollup 1 for Exchange Server 2010 SP3 installed
  • 2873477 All messages are stamped by MRM if a deletion tag in a retention policy is configured in an Exchange Server 2010 environment
  • 2860037 iOS devices cannot synchronize mailboxes in an Exchange Server 2010 environment
  • 2854564 Messaging Records Management 2.0 policy can't be applied in an Exchange Server 2010 environment

Exchange Server 2013

MS13-061 is the first security update released for Exchange Server 2013 utilizing the new servicing model.  MS13-061 is available as a security update for:

Important: If you have previously deployed CU2, you must ensure you are running build 712.24 in order to apply the security update. For more information about build 712.24, please see Now Available: Updated Release of Exchange 2013 RTM CU2.

Ross Smith IV
Principal Program Manager
Exchange Customer Experience

Updated Jul 01, 2019
Version 2.0

90 Comments

  • Anonymous's avatar
    Anonymous

    @Sadda - yes we did introduce a fix for E2010 SP3 RU2 that addresses the issue where delegate archive show the name of the primary mailbox owner.  However, a client side fix is also required, but I don't have information on when that is shipping.  

  • Anonymous's avatar
    Anonymous

    @Ross / Brian,

    Is this Update Rollup 2 for Exchange 2010 SP3 fixes an issue with Archive mailbox appearance in Outlook (where both Online Archive and Regular mailbox names appear as same)?

    Thanks!

  • Anonymous's avatar
    Anonymous

    @Steve, no we blindly release code and let you test it for us. ;) j/k I will defer to the last few Q&A bullets in Ross' previous article here for commentary on testing. Short answer is, absolutely we do. http://blogs.technet.com/b/exchange/archive/2013/07/12/e2013-rtm-cu2-issue-public-folder-permissions-loss-after-pf-mailbox-move.aspx

  • Anonymous's avatar
    Anonymous

    Brian, are these CU's/RU's getting tested? It appears that new bugs are created with each new fix. We are almost better off not apply the fixes. Any comments?

  • Anonymous's avatar
    Anonymous

    @Tracy, yes please refer to the whole list for 2010 SP3 RU2 referred above, http://support.microsoft.com/?kbid=2866475 . That should then link to KB2859596 which I believe is the item you are asking about.

  • Anonymous's avatar
    Anonymous

    @Casey Tomlinson - We did address an issue with GetRoomList to scope the recipient session using the user's Address list as opposed to the global scope which resulted in high CPU load on AD servers.

    Ross

  • Anonymous's avatar
    Anonymous

    does this correct the signature bug from RU1?

    --Tracy

  • Anonymous's avatar
    Anonymous

    @juergen, the established servicing model will continue for the remainder of Exchange 2007 and Exchange 2010's product support lifecycle. We heard the feedback and were able to update Exchange 2013's servicing model to allow us to ship individual security updates, as we have just done here for the first time.

  • Anonymous's avatar
    Anonymous

    Once again, please stop Security Updates for Exchange 2010 through URs!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

  • Anonymous's avatar
    Anonymous

    Does this include the GetRoomLists fix that utilized NSPI when no Room Lists were defined?