Update Rollup 9 for Exchange Server 2007 Service Pack 1 was recently released.
Update Rollup 9 for Exchange Server 2007 Service Pack 1 (SP1) resolves issues that were found in Exchange Server 2007 SP1 since the software was released. This update rollup is highly recommended for all Exchange Server 2007 SP1 customers.
For a list of changes that are included in this update rollup, see KB970162.
This update rollup does not apply to Exchange Server 2007 Release To Manufacturing (RTM). For a list of update rollups applicable to Exchange Server 2007 RTM, refer to the section Update rollups for Exchange Server 2007 RTM in the Knowledge Base article KB937052.
This is a cumulative update rollup and replaces the following:
- KB945684 Update Rollup 1 for Exchange Server 2007 Service Pack 1 (KB945684)
- KB948016 Update Rollup 2 for Exchange Server 2007 Service Pack 1 (KB948016)
- KB949870 Update Rollup 3 for Exchange Server 2007 Service Pack 1 (KB949870)
- KB952580 Update Rollup 4 for Exchange Server 2007 Service Pack 1 (KB952580)
- KB953467 Update Rollup 5 for Exchange Server 2007 Service Pack 1 (KB953467)
- KB959241 Update Rollup 6 for Exchange Server 2007 Service Pack 1 (KB959241)
- KB960384 Update Rollup 7 for Exchange Server 2007 Service Pack 1 (KB960384)
- KB968012 Update Rollup 8 for Exchange Server 2007 Service Pack 1 (KB968012)
According to information posted on the Microsoft Exchange Team blog, these are the main bug fixes:
- KB 969911 – This is bug likely to affect customers who have deployed the Messaging Records Management feature and have specified a storage limit for a managed folder. After a move mailbox, the property which marks the folders as managed is not preserved.
- KB 968621 – Store stops responding under certain conditions when scheduled backup is canceled and online maintenance is in progress.
- KB 945877 – Performance improvements to eseutil when it verifies the checksum of transaction logs.
- Support for Windows Server 2008 R2 Domain Controllers in the environment (Note: Exchange Server 2007 itself is not supported to be installed on a Windows Server 2008 R2 system.
- KB 968715 – This bug is likely to affect customers who have deployed CAS-CAS proxying. When a user selects This is a public or shared computer or This is a private computer on the Outlook Web Access logon page, this value is not maintained between the CAS servers when the request is proxied. This bug will most likely affect customers with Internet facing CAS sites which proxy the requests to internal sites. Now the bug was that we defaulted to private access irrespective of the option selected by the user. Outlook Web Access has the following features which allow the administrator to control access of users depending on the logon type
After deploying this rollup, the logon type will now be correctly maintained between CAS servers if the request is proxied.
Administrators should watch out for scenarios where they have configured different behavior based on the logon type and required users to select the private computer option to access files, but users were able to access files without selecting the private computer option due to this bug. These users will now be unable to do so because we fixed the bug.
As usual, I used my virtual machines as a test subject, and the result is pretty good!