A Patch Begets a Patch...Begets Another Patch?

Microsoft Wednesday rereleased - again - in the use of the last patches O u tlook Network Access (OWA operator), which is based on we b interface for the use of Mi crosoftEx changeSe rver5. 5th and E x changeSe rver20 00.

Our story, so far: last Wednesday, June 6, Microsoft released version 1.0 of a software patch to fix security loopholes in OWA operator. In a notice (http://www.microsoft.com/technet/security/bulletin/ms01-030.asp) released its security Web site, Microsoft recommends that users rolling out its own OWA operator - that is, most of the Exchange 5.5 Exchange 2000 The deployment - to "install the patches immediately." Fast forward two days: Friday, June 8, OWA security update is temporarily disappeared from Microsofts "download" web site, replaced by an obscure news , which means that the patch is "temporarily unavailable", but it promised that it would "return the site in the near future." The day before, Thursday, June 5, at least two users posted messages to the Windows NT system administrator mailing list (http://www.sunbeltsoftware.com/ntsysadmin_list_charter.htm), which, they complain , said that the patch caused their Exchange server to crash shortly after they install it. Coincidence? Clearly not. Last Saturday, Microsoft confirmed that version 1.0 of OWA operator patches is flawed - According to a notice that amendment was attached to the original security bulletin, it is possible the culprit was identified as "a return to the" wrong -, and issued a new 2.0 version of the update has (surface) after testing and certification. Microsoft also expanded the scope of the original security bulletin to include the Exchange 5.5 server are: first, time, as well as.

Get interesting here: Wednesday, June 13, Microsoft released a new version of OWA 3.0 is security updates. Why not do that? Obviously, the reason is very simple, that is, 2.0 version of the patch is itself flawed, and contained "outdated documents," which may eventually crashed Exchange server.

It is not known when the 4.0 version of Microsofts patch will be available to fix its recent updates. -- Stephen s woyer