EDIT 10/9/2008: We updated the MU (Microsoft Update) release date of this patch as well as the Installation Notes section.
We have released the final version of Update Rollup 4 for Exchange Server 2007 SP1 (KB952580)
The update is live at:
http://www.microsoft.com/downloads/details.aspx?FamilyId=8B492ED2-EA92-412F-A852-3AA1C58D9499&displaylang=en
Related KB article:
http://support.microsoft.com/?kbid=952580
The rollup is marked as "v2" in the file name i.e. "Exchange2007-KB952580-v2-x64-EN.msp" to account for the accidental release of v1 via Microsoft Update on 9th September. This version of rollup will install over the "v1" mentioned above if you have installed a v1 when it was accidentally released.
The rollup is available via the download center link starting today. It will be available via Microsoft Update starting with 11/4/2008.
Installation notes
There are a few possible installation issues that we would like you to be aware of:
- Exchange 2007 managed services might time out during certificate revocation checks
- When installing a Rollup, we recommend you use the same account that you used to install Exchange Server. If you are using a different account, that account needs to have Local Administrator rights as well as rights to read Active Directory on Exchange object as well as server level (as the update needs to determine which roles are installed on the server). Not having required permissions can lead to OWA not being updated correctly and displaying a blank page after update has completed.
- If you have modified the logon.aspx file, it will not be patched by the Update Rollup installer. As a result Outlook Web Access may not be updated correctly and it may display a blank page after the update has finished. In order to avoid this problem, rename the logon.aspx file before applying the update rollup. After you apply an update rollup package, you must re-create Outlook Web Access customization in logon.aspx.
- The update might take long time to apply. To try preventing this, follow the instructions in this post before applying the update. We are working on a permanent fix for this.
