Released: Update Rollup 6 for Exchange 2007 Service Pack 3


Earlier today the Exchange CXP team released Update Rollup 6 for Exchange Server 2007 SP3 to the Download Center.

Note: The post title erroneously referred to Update Rollup 3. It has been updated to reflect the correct rollup number.

This update contains a number of customer-reported and internally found issues since the release of RU5. See KB 2608656: Description of Update Rollup 6 for Exchange Server 2007 Service Pack 3′ for more details.

We would like to specifically call out the following fixes which are included in this release:

  • DST Cadence Release for Dec 2011 – Exchange 2007
  • 22656040 An Exchange Server 2007 Client Access server may respond slowly or stop responding when users try to synchronize the Exchange ActiveSync devices with their mailboxes
  • 2498852 “0x80041606” error message when you perform a prefix search by using Outlook in online mode in an Exchange Server 2007 environment
  • 22653334 The reseed process is unsuccessful on the SCR passive node when the circular logging feature is enabled in an Exchange Server 2007 environment
  • 22617784 Journal reports are expired or lost when the Microsoft Exchange Transport service is restarted in an Exchange Server 2007 environment
  • 2289607 The week numbers displayed in OWA do not match the week numbers displayed in Outlook for English users and French users in an Exchange Server 2007 environment

General Notes:

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

Note for Forefront Protection for Exchange users  For those of you running Forefront Protection for Exchange, be sure you perform these important steps from the command line in the Forefront directory before and after this rollup’s installation process. Without these steps, Exchange services for Information Store and Transport will not start after you apply this update. Before installing the update, disable ForeFront by using this command: fscutility /disable. After installing the update, re-enable ForeFront by running fscutility /enable.

Exchange Team

Comments (8)
  1. markh says:

    Note: The post title erroneously referred to Update Rollup 3. It has been updated to reflect the correct rollup number.

    This update contains a number of customer-reported and internally found issues since the release of RU4

    Umm…shouldn't that have referred to Update 5, not 4?

  2. Bharat Suneja [MSFT] says:

    @MarkH: Yes, indeed – fixed. Thanks for catching that!

  3. HotFix says:

    You might want to fix KB22656040 as it refers to Exchange 2010, not Exchange 2007 in the Resolution:

    "Note After you apply this update rollup, the Exchange Server 2010 server will drop EAS sessions if the number of sessions for a user exceeds the session limit. When the number of sessions is dropped lower than the limit, new requests can be automatically processed."

  4. susan says:

    Do you know when it will be slated to be on WSUS?

  5. SuperGumby says:

    When installing to SBS08 using the normal Domain Administrator account created during SBS installation I get:

    'The installer has insufficient permission to modify c:blah_exch_folderrelnotes.htm'

    Do I gotta enable the 500 account just to install this thing?

  6. HotFix says:

    @SuperGumby – Try running the executable through a command window that you have "Run as Administrator". I suspect you are running into UAC issues where the roll up is not running on the right context.

  7. GregW says:

    After upgrading our Exchange 2007 Server to SP3, I then applied the Update Rollup 6.  Installation went smoothly and Exchange now reports the it is at version 8.3.245.2.  For some reason however, when runing windows update it wants to download and install Update rollup package 5 for Exchange Server 2007 SP3.  I have selected to hide this update and now it wants to install Update Rollup 4.  I thought that the update rollups were cumulative and you only needed to apply the latest one?  Do you need to install all update rollups sequentially?

  8. Mark Berry says:

    Installing on SBS 2008, I had to manually stop the Windows SBS Manager service (DataCollectorSvc.exe) before the install would proceed. I blogged screen shots but this site will not let me paste a link. You can search for the MCB Systems blog.

Comments are closed.