Blog Post

Exchange Team Blog
1 MIN READ

Released: Update Rollup 5 v2 for Exchange 2010 SP2, Exchange 2010 SP1 RU8 and Exchange 2007 SP3 RU9

The_Exchange_Team's avatar
The_Exchange_Team
Platinum Contributor
Dec 11, 2012

Today the Exchange CXP team released the following update rollups to the Download Center. All three releases cover Security Bulletin MS12-080. Because this is a security release, the updates will also be available on Microsoft Update.

Update Rollup 5-v2 for Exchange Server 2010 SP2

This update contains a number of customer reported and internally found issues. For a list of updates included in this rollup, see KB 2785908 Description of Update Rollup 5 version 2 for Exchange Server 2010 Service Pack 2. 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.

  • 2748766 Retention policy information does not show "expiration suspended" in Outlook Web App when the mailbox is set to retention hold in an Exchange Server 2010 environment
  • 2712595 Microsoft Exchange RPC Client Access service crashes when you run the New-MailboxExportRequest cmdlet in an Exchange Server 2010 environment
  • 2750847 An Exchange Server 2010 user unexpectedly uses a public folder server that is located far away or on a slow network

For DST Changes: http://www.microsoft.com/time

Exchange Team

Updated Jul 01, 2019
Version 2.0
announcements
Exchange 2007
Exchange 2010
setup

97 Comments

Show More
  • Anonymous's avatar
    Anonymous
    Dec 12, 2012

    Note that it's no longer required to restart ForeFront service manually since Exchange 2010 SP2 RU4. See http://support.microsoft.com/kb/2743871 Microsoft Exchange Transport service does not restart automatically after an Exchange update is installed.

  • Anonymous's avatar
    Anonymous
    Dec 12, 2012

    @deiruch - what did you try installing, on which kind of server (roles etc.)?

  • Anonymous's avatar
    Anonymous
    Dec 12, 2012

    Didn't work for me. Just wanted to let you guys know. Tried disabling Forefront manually, but that didn't help.

    Action 23:33:18: CA_CUSTOMER_PREPATCH_INSTALL.

    CAQuietExec:  Error 0x80070001: Command line returned an error.

    CAQuietExec:  Error 0x80070001: CAQuietExec Failed

    CustomAction CA_CUSTOMER_PREPATCH_INSTALL returned actual error code 1603 but will be translated to success due to continue marking

    Action 23:33:19: CA_ROLLBACK_SAVEDATA_STOP_SERVICES.

    Action 23:33:19: CA_START_WMI_SERVICES_ROLLBACK.

    Action 23:33:19: CA_ENABLE_WMI_SERVICES_ROLLBACK.

    Action 23:33:19: CA_SAVEDATA_STOP_SERVICES. Stopping services

    CAQuietExec:  Error 0x80070001: Command line returned an error.

    CAQuietExec:  Error 0x80070001: CAQuietExec Failed

    CustomAction CA_SAVEDATA_STOP_SERVICES returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

    Action ended 23:33:31: InstallExecute. Return value 3.

  • Anonymous's avatar
    Anonymous
    Dec 12, 2012

    When compared to the original version, the following fix went MIA in EX2010SP2RU5v2:

    2748870 Declined meeting request is added back to your calendar after a delegate opens the request by using Outlook 2010

  • Anonymous's avatar
    Anonymous
    Dec 12, 2012

    I recently completed the transition from Exchange 2007 to Exchange 2010. My testing and planning included RU 4 and then RU4-v2.

    However, after reading of many problems experienced after either or these RUs, the majority of who roll-backed to RU3, I proceed with just RU3. As RU5 only just came out, I decided to wait a month or so for any fallout.

    The quality assurance of these RU is of some concern and this stage, will have to stick with RU3 until a stable RU is released.

  • Anonymous's avatar
    Anonymous
    Dec 12, 2012

    I agree with Paul and am very concerned with the quality assurance testing that goes into these roll-ups.  I have a policy that I don't touch Roll-ups for a month to wait and see if a recall is going to happen.

  • Anonymous's avatar
    Anonymous
    Dec 12, 2012

    I for one find the product teams decision to fix security vulnerabilities only in Update Rollups completely unacceptable and at odds with many other products in the Microsoft product line. A security vulerability should be addressed by a small hotfix that addresses the vulnerability rather than part of a much wider rollup which includes additional functionallity and a much braoder change to the code base. For those in coprorate environments testing a large rollup is at odds with security patching.

    The number of re-issues for rollups in the last year or so also reinforces the need not to be an early adopter and effectively test updates which is at odds with covering an exploit.

    I wish you would review this methodology.

    Paul