Another Exchange Windows Update problem we encountered this week...
After loading the WindowsUpdate site I noticed that it was recommending an Exchange Update (KB888619) on the Windows Update. Now Exchange Updates are not something that you generally find on Windows Updates. (See image on the left)
After installing this update OWA was broken. The theme was not loading properly, and the right hand side of the reading pane had a single line reading "Loading..."
Initially I thought that the theme was broken with some replaced style-sheets, etc.
However, a quick scan through the Microsoft newsgroups I found a post (Problem with OWA after Installing KB888619) on microsoft.public.exchange.connectivity that explained the behaviour:
"You need to install 888619 on your Front End Server as well because that fix
adds an updated directory under the /exchweb folder which contains new .asp
files. With this folder missing on your Front End you will see the exact
behaviour you are experiencing. You would also see this problem if you
applied Service Pack 1 to your Back Ends, and not your Front Ends. - Ben Wolfe [MSFT]"
So, I guess this again highlights the importance of keeping your environment - and not just Exchange - on the same versions of updates and service packs. In my defense I must add that since Windows Update didn't recommend this update on the other servers, I automatically assumed that either the server already has it installed, or didn't need the update.
The Lesson - Don't assume.
As a side note - this update replaces the file C:\Program Files\Exchsrvr\exchweb\bin\auth\usa\logon.asp that is used by forms-based authentication. So if you customised your logon page then remember that you'll need to re-apply those changes.
- Marlon
PS. Can anyone tell me how to enable Windows Update to check for Exchange Server updates on my other servers. I've had a quick look around, but didn't notice anything on first glance.