"Mike Chan [MSFT]" <mc...@online.microsoft.com> wrote in message news:uFkjBn8...@TK2MSFTNGP10.phx.gbl...
"Bill Drake" <bdr...@telus.net> wrote in message news:uOCSsb9g...@TK2MSFTNGP09.phx.gbl...
"Doug Neal [MSFT]" <du...@online.microsoft.com> wrote in message news:%23KVoQf9...@TK2MSFTNGP12.phx.gbl...
"Doug Neal [MSFT]" <du...@online.microsoft.com> wrote in message news:%23KVoQf9...@TK2MSFTNGP12.phx.gbl...
FAQ
http://www.microsoft.com/technet/security/tools/mbsaqa.mspxTechnical white paper
http://www.microsoft.com/technet/security/tools/mbsawp.mspx
are the actual links.
The FAQ and whitepaper links below are no longer working.
"Mike Chan [MSFT]" <mc...@online.microsoft.com> wrote in message news:uFkjBn8...@TK2MSFTNGP10.phx.gbl...
"Doug Neal [MSFT]" <du...@online.microsoft.com> wrote...
During the installation, MBSA 1.2.1 will automatically upgrade MBSA 1.2 - soyou should have no problems updating directly. You do NOT need to uninstallthe previous MBSA 1.2 version.I make note of this for other customer since, you're right - this isn't clear.I hope that helps...
--Doug Neal [MSFT]
du...@online.microsoft.comThis 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 the Microsoft Baseline
Security Analyzer (MBSA) at the following link:
http://support.microsoft.com/default.aspx?scid=fh;en-us;Prodoffer20aThis e-mail address does not receive e-mail, but is used for newsgroup
postings only.
"Bill Drake" <bdr...@telus.net> wrote...
"Mike Chan [MSFT]" <mc...@online.microsoft.com> wrote...
I will make a note of it and update the next release of our FAQ.Thanks,Mike
--
Mike Chan
Technical Product Manager (MBSA)
Security Business Unit
Microsoft CorporationThis posting is provided "AS IS" with no warranties, and confers no rights.
--
"Doug Neal [MSFT]" <du...@online.microsoft.com> wrote...
During the installation, MBSA 1.2.1 will automatically upgrade MBSA 1.2 - so you shouldhave no problems updating directly. You do NOT need to uninstall the previous MBSA 1.2version.I make note of this for other customer since, you're right - this isn't clear. I hope that helps...
--Doug Neal [MSFT]
du...@online.microsoft.comThis 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 the Microsoft Baseline
Security Analyzer (MBSA) at the following link:
http://support.microsoft.com/default.aspx?scid=fh;en-us;Prodoffer20aThis e-mail address does not receive e-mail, but is used for newsgroup
postings only.
"Bill Drake" <bdr...@telus.net> wrote...
The FAQ'a and White Paper (links) aren't working or correct? (you say below).
ARGH!
1. HTML
2. Cross posted to microsoft.public.windows.server.sbs,
microsoft.public.security.hfnetchk, microsoft.public.security.baseline_analyzer,
microsoft.public.security,
- without announcement
- without followup to ONE group only.
3. with invalid From: address
Ain't there a netiquette for you guys?
fup2 microsoft.public.security.baseline_analyzer
not amused
Stefan
Sorry, didn't mean to say all that... Why don't you educate us in
"netaquitte"? And let us judge how well you do... (Remember, your addressing
millions of people).
MBSA 1.2.1 update for Windows XP SP2 compatibility available today!
I understand your frustration and we are committed to ensuring that the results
from MBSA and windows update are the same.
As many of you know, MBSA uses the HFNetChk detection engine by Shavlik. Windows
Update uses the software update engine that was built by Microsoft and supports
only a subset of products that MBSA supports. The two technologies work
differently, and in the current time frame, we must use our internal processes
to ensure that results are the same.
For a short term resolution to your problem, can you tell me what patches are
you referring to? Can you give me more information in this area?
--
Mike Chan
Technical Product Manager (MBSA)
Security Business Unit
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"Peter Ninen" <som...@somewhere.com> wrote in message
news:ejNzdXWh...@TK2MSFTNGP09.phx.gbl...
Here’s a breakdown on the differences between MBSA and Windows Update so users and administrators can decide which is best to use in different situations.
MBSA does one important thing that WU does not: MBSA will check explicit files to ensure a security bulletin and all of the associated files are patched on a machine. This is far and above the best way to ensure your machine is up-to-date for all security bulletins released by Microsoft. WU detection may result in incorrect patch status after uninstalling a patch, using System Restore on a machine or performing an in-place repair of the OS. Since MBSA checks explicit file versions, no matter what state a machine is in, MBSA will correctly detect whether a patch is sufficiently applied in a way that WU cannot.
Windows Update does one important thing that MBSA does not: WU will scan for all updates, not just security updates (which can include drivers, recommended updates and ‘nice to have’ features offered by Microsoft).
Aside from both of these traits, it’s important to understand one more aspect of MBSA 1.2. Although the current version of MBSA has added support for many OS features and components (such as MSJVM, MSXML and MDAC), there are still patches for which MBSA cannot report the status of a patch (such as Outlook Express, WSH [Windows Scripting Host], and Front Page Server Extensions). When MBSA encounters security bulletin information that the MBSA engine cannot scan for, MBSA will report a NOTE message. When MBSA encounters a security bulletin for a component or feature that is not supported by MBSA, there will be no message (no note, no warning – nothing). In both of these cases, it is an important indication that the administrator will need to check the details of this patch manually. These issues are covered more fully in the associated KB article 306460.
I hope that helps explain some of inner workings of MBSA in a way that helps
"Peter Ninen" <som...@somewhere.com> wrote in message news:ejNzdXWh...@TK2MSFTNGP09.phx.gbl...
"Doug Neal [MSFT]" <du...@online.microsoft.com> wrote in message news:OFyBy9Xh...@TK2MSFTNGP12.phx.gbl...
Why isn't the version numberiing consistent? The earlier version
was 1.2.3xx so an upgrade should be numbered at least 1.2.4xx.
--
Earl F. Parrish
--
--
Mike Chan
Technical Product Manager (MBSA)
Security Business Unit
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"Earl F. Parrish" <efp...@nowhere.world> wrote in message
news:elTUlMh...@TK2MSFTNGP12.phx.gbl...
This is what is appended to all my former scans when I upgraded to
1.2.1:
Scanned with MBSA version: 1.2.3316.1 ** Newer version
1.2.4013.0 is available
So you can see how one can be confused by version numbers since
1.2.1 only appears in the "About Microsoft Baseline Analyzer"
display. All my previous reports had version 1.2.3316.1 in the scan
reports. It would be less confusing if the Product number and the
version number were identical.
--
Earl F. Parrish
4013.0 and 3316.1 are internal build numbers for MS reference only.
--
Mike Chan
Technical Product Manager (MBSA)
Security Business Unit
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"Earl F. Parrish" <efp...@nowhere.world> wrote in message
news:%23W16W3h...@TK2MSFTNGP12.phx.gbl...