Thank you for posting this, Bob.
Due to customer requests, MBSA 2.1 changed the default behavior was changed
to prevent automatic installation of updated Windows Update Agent clients
when needed on target machines. To re-enable this feature that was the
default behavior in MBSA 2.0.1, simply check the option to 'Configure
computers for Microsoft Update and scanning prerequisites' in the 'which
computer do you want to scan' screen. As long as you have administrative
rights on the target machines, MBSA will automatically deploy the latest WUA
client - which should solve this issue.
Also note that this settings is not retained between uses so there is no
chance a security auditor could unintentionally upgrade target clients. So,
be sure to re-check this each time you need it. I hope that helps...
Doug Neal [MSFT]
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
This e-mail address does not receive e-mail, but is used for newsgroup
Post by Bob Weiner
We'd like to use MBSA 2.1 to scan the windows machines on our network.
This worked at one time but now is failing (from multiple computers) with
"manually install WUA on each target computer."
What broke? This worked before.
In a domain with a couple thousand computers, with some coming and going
all the time, are we really supposed to manually install an agent just to
run a scan? Can't MBSA do passive scans, like nmap, if it doesn't find an