|
Posted by Doug Neal [MSFT] on March 27, 2007, 9:07 pm
If you were Registered and logged in, you could reply and use other advanced thread options
As previously indicated on the MBSA home page
(http://www.microsoft.com/mbsa) and in KB 926464
(http://support.microsoft.com/kb/926464), the MBSA 2.0 offline catalog
WSUSSCAN.CAB has been discontinued as of today, March 27, 2007. This
further underscores the need for customers to upgrade to MBSA 2.0.1 or the
MBSA 2.1 beta which use the newer WSUSSCN2.CAB file. Please be sure to
check the MBSA home page for details on how this may affect you if you are
still using MBSA 2.0 (this does not affect customers who have upgraded to
MBSA 2.0.1 or customers who are still using the older MBSA 1.2.1 scan tool).
To understand how this may affect MBSA users, it may be helpful to
understand the 3 different sources for the MBSA security update signature
(catalog) file used to determine needed security updates.
Option 1 - Microsoft Update catalog: When scanning, MBSA 2.x will establish
a connection to each target machine. If that target machine has
unobstructed internet access to the Microsoft Update site, the target client
will use the online Microsoft Update site to obtain its list of needed
security updates and report the results back to the MBSA scan tool.
Option 2 - WSUS Server: If the target machine is unable to reach Microsoft
Update, it will attempt to connect to an assigned WSUS 2.0/3.0 Server to
obtain a list of missing security updates from the WSUS Server and report
results back to the MBSA scanner.
Option 3 - WSUSSCN2.CAB (offline CAB file): If neither MU nor a WSUS Server
can be contacted by the target machine, the target client will request a
copy of the offline catalog (WSUSSCN2.CAB) from the scanning machine (where
the MBSA scan was started).
It is only this mode (called 'offline mode') with MBSA 2.0 that will no
longer work with today's retirement of the outdated WSUSSCAN.CAB file
referenced in KB 926464. Users who may still be using MBSA 2.0 in offline
mode (or when one or more target clients cannot contact the Microsoft Update
site or an assigned WSUS Server) will get the error, "The catalog file is
damaged or an invalid catalog"
The "The catalog file is damaged or an invalid catalog" error message is
further indication that the customer should upgrade to MBSA 2.01 or the MBSA
2.1 beta which use the newer WSUSSCN2.CAB file for offline scans.
Please feel free to refer to the MBSA home page or MBSA 2.0.1 FAQ
(http://www.microsoft.com/technet/security/tools/mbsa2/qa.mspx) for the
latest information regarding MBSA 2.0.1 and the MBSA 2.1 beta.
Also feel free to post any inquiries regarding this update to this
newsgroup. Thank you.
--
Doug Neal [MSFT]
dugn@online.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights.
If newsgroup discussion with experts and MVPs is unable to solve a problem
to your satisfaction, feel free to contact PSS for support on the Microsoft
Baseline Security Analyzer (MBSA). Information is available at the following
link:
http://support.microsoft.com/default.aspx
This e-mail address does not receive e-mail, but is used for newsgroup
postings only.
|
| Similar Threads | Posted | | MBSA 2.0 | August 17, 2005, 6:12 am |
| MBSA.EXE | November 21, 2006, 7:36 pm |
| re MBSA | March 28, 2007, 6:58 am |
| Nessus vs MBSA | July 27, 2005, 11:57 am |
| MBSA 1.2.1 End of Life Q&A | February 17, 2006, 2:07 pm |
| MBSA 2.1 Beta 2 Now Available | May 9, 2007, 6:25 pm |
| MBSA 2.1 RELEASED | May 5, 2008, 7:59 pm |
| MBSA 1.2.1 end-of-life statement | February 14, 2006, 1:25 pm |
| MS07-002 Not Detected by MBSA 2? | January 10, 2007, 3:07 pm |
| How does MBSA collect it's data? | September 4, 2007, 3:36 am |
|
XML site map