14 DAY TRIAL // Update Rollup 9 for Exchange Server 2007 Service Pack 1 is available for download since the end of the past week, with Microsoft gearing up to serve the refresh via Windows Update by the end of this month. The Redmond company stressed that the update rollup was considered highly recommended to all customers running the first service pack for Exchange Server 2007. According to the software giant the focus with Update Rollup 9 for Exchange Server 2007 SP1 is to deliver resolves for a number of issues that have been identified in Exchange Server 2007 SP1 since released.
“The majority of changes in this rollup are bug fixes. Here are a few that I would like to call out: KB 969911 - This bug is likely to affect customers who have deployed the Messaging Records Management feature and have specified a storage limit for a managed folder. 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,” revealed a member of the Exchange Customer Experience team.
Microsoft has accompanied the refresh with KB 970162, providing customers with not only additional details about the refresh, but also with an exhaustive list of all fixes made available with the rollup. Just as it was the case with similar past refreshes, Update Rollup 9 is a cumulative update rollup, replacing all precursors. The refresh is already available for download, and Microsoft will start offering it via Microsoft Update come July 28.
Another fixed issue is “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,” the Exchange Customer Experience team representative added.