MBSACLI 2.0 /xmlout Parsing Script
flag
Messages 1 - 10 of 19 - Collapse all
/groups/adfetch?adid=UmaAgBEAAAA5clbOuiDYtewv_P8kV7xZnT3luubDeskUok6AUQ17nQ
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Follow-up To:
Add Cc | Add Follow-up to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers that you hear
 
1.  Andrew Aronoff  
View profile   Translate to Translated (View Original)
 More options 7 July 2005, 02:07
Newsgroups: microsoft.public.security.baseline_analyzer
From: Andrew Aronoff <NOSPAM_WRONG.ADDR...@yahoo.com>
Date: Thu, 07 Jul 2005 03:07:06 +0200
Local: Thurs 7 July 2005 02:07
Subject: MBSACLI 2.0 /xmlout Parsing Script
I have written a VBS script that runs MBSACLI 2.0 with the /xmlout
option and parses the XML output file to produce a readable text file.

The script can be downloaded here:
http://www.silentrunners.org/MBSACLI%20XML%20Parser.vbs

The MD5 hash is: E2EE397BC540EC23D901018EC033890E
This hash applies to the initial release, R00. The release number will
always be found on line 15 of the script.

The script is free, but is provided with no warranty, expressed or
implied. It changes settings in the registry (and is designed to reset
the registry to the initial settings before it's done) and requires
Internet connectivity (so that it can retrieve hotfix datafiles from
Microsoft). You use this script at your own risk!

Please note:

1. The script must be located in the same directory as MBSACLI.EXE and
WUSSCAN.DLL. (It will display an error message if it isn't.)

2. The output text file will be placed in the same directory as the
script. The title root is "Hotfix Check Results.txt".

3. The script can be run with a single command line parameter that
will be appended to the output file name. If "Workstation 999" is the
command line parameter, the output text file title would be "Hotfix
Check Results Workstation 999.txt".

4. The script can only be run under Windows 2000 and Windows XP, since
earlier OS's are incompatible with MBSACLI 2.0. Running under an
earlier OS will display an error message.

5. The script must be run under an Administrator account. Running
under a non-admin account will display an error message.

6. The script will only report uninstalled hotfixes. The report format
is:

Sequence number. Hotfix title
Security bulletin number, Knowledge Base article number, update type,
update severity.
(Optional) restart-pending notice.
Security Bulletin URL
Download URL

A typical entry might be:

#. Some alarmiing hotfix title here
MS00-000 KB123456, Security Update, Maximum Severity: Critical
Security Bulletin URL: http://www.microsoft.com/.../MS00-000.mspx
Download URL: http://ridiculously_long_filename_here.exe

7. Microsoft Update Agent 2.0 is required for MBSACLI 2.0. Once it's
installed, the script does not require the Automatic Updates service
to be started. The script will enable the service if it's disabled and
start it up. It will restore the original service status before it
exits.

8. The script is written for use on workgroup PC's. Revisions are
welcome so that it can be used in a domain.

9. The script will hang if MBSACLI.EXE cannot download its .CAB file.
If someone has a suggestion to avoid this, please let me know.

10. If the script throws an error, please let me know and I'll fix the
bug.

11. If you have an XML parsing suggestion, please let me know and I'll
improve the script.

12. If you need customization assistance to get the script to work
your way in your shop, make me an offer. ;-)

13. MS will, of course, provide their own scripts. I have no idea what
their scripts will do.

regards, Andy
--
                                  **********

       Please send e-mail to: usenet (dot) post (at) aaronoff (dot) com

         To identify everything that starts up with Windows, download
                 "Silent Runners.vbs" at www.silentrunners.org

                                  **********


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message, you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
2.  Rob Wickham [msft]  
View profile   Translate to Translated (View Original)
 More options 7 July 2005, 17:51
Newsgroups: microsoft.public.security.baseline_analyzer
From: "Rob Wickham [msft]" <rwick...@microsoft.com>
Date: Thu, 7 Jul 2005 09:51:58 -0700
Local: Thurs 7 July 2005 17:51
Subject: Re: MBSACLI 2.0 /xmlout Parsing Script
Andrew, this is excellent.  There is a recent post from another user looking
for something like this.

Slightly OT: Does anyone have existing scripts that can generate a list of
computer names or individual IP addresses when given either a domain name as
input or an IP range as input?  I suspect there are such scripts being used
with the MBSA 1.2.1 batchscan.js samples, but I'd like to confirm this with
anyone who's done it already.

--
Rob Wickham [msft]
This posting is provided "as is" with no warranties, and confers no rights.

"Andrew Aronoff" <NOSPAM_WRONG.ADDR...@yahoo.com> wrote in message

news:lutoc1hmhs2lib90n9c8g3q36rlfpk2qck@4ax.com...


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message, you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
3.  SixDoubleO  
View profile   Translate to Translated (View Original)
 More options 7 July 2005, 23:22
Newsgroups: microsoft.public.security.baseline_analyzer
From: "SixDoubleO" <SixDoub...@discussions.microsoft.com>
Date: Thu, 7 Jul 2005 15:22:01 -0700
Local: Thurs 7 July 2005 23:22
Subject: RE: MBSACLI 2.0 /xmlout Parsing Script
Andy,

Thanks for the script.  I am in the middle of writing something similar,
although I use kix.  But I will take a look at your script.  

One question, though.  How do I deploy Window Update Agent to all my
workstations?  I'm certain that not all of them have it.

PS - Is it just me, or is this newest MBSA a complete step in the wrong
direction?  


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message, you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
4.  Nelson Araujo [MSFT], CISSP, MCAD  
View profile   Translate to Translated (View Original)
 More options 8 July 2005, 01:32
Newsgroups: microsoft.public.security.baseline_analyzer
From: "Nelson Araujo [MSFT], CISSP, MCAD" <nels...@online.microsoft.com>
Date: Thu, 7 Jul 2005 17:32:49 -0700
Local: Fri 8 July 2005 01:32
Subject: Re: MBSACLI 2.0 /xmlout Parsing Script
Andy,

To deploy Windows Update Agent on your computers just scan them with MBSA
2.0, with the option to Configure computers enabled. But please make sure
you have the requirements to remotely scan MBSA on the target computer (like
firewall settings) before doing that as MBSA will not be able to penetrate
XP firewall (or 3rd party vendors).

Let me know if I can help more.
--
Regards,

Nelson Araujo, CISSP, MCAD
Software Development Engineer
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

"SixDoubleO" <SixDoub...@discussions.microsoft.com> wrote in message

news:C930F401-1D9E-4A40-B714-E364D46F7495@microsoft.com...


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message, you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
5.  Andrew Aronoff  
View profile   Translate to Translated (View Original)
 More options 8 July 2005, 02:00
Newsgroups: microsoft.public.security.baseline_analyzer
From: Andrew Aronoff <NOSPAM_WRONG.ADDR...@yahoo.com>
Date: Fri, 08 Jul 2005 03:00:52 +0200
Local: Fri 8 July 2005 02:00
Subject: Re: MBSACLI 2.0 /xmlout Parsing Script

>How do I deploy Window Update Agent to all my workstations?

When you run my script on a workstation that doesn't have Windows
Update Agent 2.0, MBSACLI.EXE will fail to download the .CAB file, the
script will detect a tiny .XML file and it will offer to send the
default browser to the Update Agent 2.0 download location. That's one
way to get it.

The other way is to download it here:
http://go.microsoft.com/fwlink/?LinkId=43264
and use your preferred method of rolling out a hotfix.

>Is it just me, or is this newest MBSA a complete step in the wrong
>direction?  

That makes two of us.

regards, Andy
--
                                  **********

       Please send e-mail to: usenet (dot) post (at) aaronoff (dot) com

         To identify everything that starts up with Windows, download
                 "Silent Runners.vbs" at www.silentrunners.org

                                  **********


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message, you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
6.  Rob Wickham [msft]  
View profile   Translate to Translated (View Original)
 More options 8 July 2005, 05:29
Newsgroups: microsoft.public.security.baseline_analyzer
From: "Rob Wickham [msft]" <rwick...@microsoft.com>
Date: Thu, 7 Jul 2005 21:29:56 -0700
Local: Fri 8 July 2005 05:29
Subject: Re: MBSACLI 2.0 /xmlout Parsing Script
Regarding a "step in the wrong direction", can you be specific about your
concerns?  Is it the fact that there is now a client-side component required
for update scanning, or something else?

--
Rob Wickham [msft]
This posting is provided "as is" with no warranties, and confers no rights.

"Andrew Aronoff" <NOSPAM_WRONG.ADDR...@yahoo.com> wrote in message

news:85hrc195l2r177uav28mqn95vvucqhnehe@4ax.com...


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message, you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
7.  SixDoubleO  
View profile   Translate to Translated (View Original)
 More options 8 July 2005, 06:13
Newsgroups: microsoft.public.security.baseline_analyzer
From: "SixDoubleO" <SixDoub...@discussions.microsoft.com>
Date: Thu, 7 Jul 2005 22:13:02 -0700
Local: Fri 8 July 2005 06:13
Subject: Re: MBSACLI 2.0 /xmlout Parsing Script
Sure!

To get full functionality from the mbsacli.exe utility, it must be
physically installed on the workstation.

The new tool seems to focus around an administrator running it
manually/interactively, directed at a large number of workstations.  This is
not how I do things.  Everything I do is lights-out and occurs at the
workstation.  In my particular environment, I have about 1400 workstations
that I cannot necessarily guarantee will be turned on or even AT the office
at a specified time.  So my strategy is to scan (and update) these machines
right at logon....it's the one time I get a "captive audience" so to speak.  
So the Gui/reporting/console type functions are of no use to me.  

The new tools relies on the WUA component and MSI 3.1.  So I have to deploy
these components to the workstation before I can even scan it.  I don't like
this.

It just seemed that HFNetChk/MBSA 1.2 was better suited to scripted
environments as it had no dependencies on other components.  All I had to do
was make the hfnetchk.exe and mssecure.xml files available in my netlogon
share, and away we went.  I could parse the output of hfnetchk and fire off
all needed updates automatically.  

On the bright side, I think the XML output will open up many more
capabilities for me (although I agree with others that the use of the "Update
Required=true/false" attribute is a very silly implementation).

Like I said above, the tools seems geared toward interactive/manual scanning
and not scheduled/scripted implementations.  Granted, many of us scripters
have completely circumvented the need for costly SMS systems, and maybe
therein lies the problem?

Nonetheless, those are some of my concerns.  I appreciate you taking the
time to hear them.


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message, you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
8.  Rob Wickham [msft]  
View profile   Translate to Translated (View Original)
 More options 8 July 2005, 21:15
Newsgroups: microsoft.public.security.baseline_analyzer
From: "Rob Wickham [msft]" <rwick...@microsoft.com>
Date: Fri, 8 Jul 2005 13:15:12 -0700
Local: Fri 8 July 2005 21:15
Subject: Re: MBSACLI 2.0 /xmlout Parsing Script
Thanks for expressing these issues.  MBSA 2.0 is a next-generation tool
using the next-generation scanning of WSUS.  The bonus is that a WSUS server
or connection to Microsoft Update is not required, and we've kept in the /HF
scenario of not needing to fully install the MBSA setup package just to scan
for updates.  The ability to extend detection for new products without the
need to change the detection engine on the client was also a significant
point of interest for our users.  Next we needed to deliver a new scanning
engine that can go all the way back to Windows 2000 SP3, and still use a
common, public client API and backend catalog of detection logic was a
challenge.

We think it was the best tradeoff we could make however, and we made MBSA
2.0 very flexible about how to deploy key components like WUA.
Historically, it takes about 8 months to ship new detection engines in MBSA
and we no longer have to wait that long based on the capabilities of WUA.  A
newly shipped Microsoft product can have a security update hosted by
Microsoft Update with no changes to the scanning engine on the client, or in
MBSA 2.0.  Being able to respond quickly like this is good.

Finally, even older versions of MBSA required components like remote
registry and file sharing, so although there are new components of Windows
required short-term, long term these will simply be a part of the OS without
the need for out of band deployment and ongoing management.

The RestartRequired='true' | 'false' attribute is interesting because it
tells you that the update only needs the computer to be rebooted in order to
provide the intended security protection.  Without this, the installation
package would probably be run over and over until the reboot happened and
you can integrate this added level of detail into your scripts and same some
cycles on the client computers.

If you have more questions about the xml attributes, please don't hesitate
to ask.

--
Rob Wickham [msft]
This posting is provided "as is" with no warranties, and confers no rights.

"SixDoubleO" <SixDoub...@discussions.microsoft.com> wrote in message

news:7433B208-B821-453E-9D10-A1B8A5647A74@microsoft.com...


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message, you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
9.  Mike Chan [MSFT]  
View profile   Translate to Translated (View Original)
 More options 10 July 2005, 19:16
Newsgroups: microsoft.public.security.baseline_analyzer
From: "Mike Chan [MSFT]" <mc...@online.microsoft.com>
Date: Sun, 10 Jul 2005 11:16:41 -0700
Local: Sun 10 July 2005 19:16
Subject: Re: MBSACLI 2.0 /xmlout Parsing Script
just to add a little more color as well...

the agent upgrade that MBSA attempts it not specific to MBSA. It is a
required upgrade of a windows component (for AU, WU, MU, WSUS, MBSA, etc)...
so MBSA is only delivering something that will be included in future updates
and service packs as well. This was the only way we could deliver consistent
scanning between all our tools.

also, if you have the latest agents on the clients, you should be able to
script around mbsacli.exe, wusscan.dll and wsusscan.cab without a full
install simliar to what you have been doing before.

--
Mike Chan
Technical Product Manager (MBSA)
Security Business and Technology Unit
Microsoft Corporation
"Rob Wickham [msft]" <rwick...@microsoft.com> wrote in message
news:erLS$m$gFHA.3868@TK2MSFTNGP14.phx.gbl...


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message, you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
10.  Torgeir Bakken (MVP)  
View profile   Translate to Translated (View Original)
 More options 12 July 2005, 15:51
Newsgroups: microsoft.public.security.baseline_analyzer
From: "Torgeir Bakken \(MVP\)" <Torgeir.Bakken-s...@hydro.com>
Date: Tue, 12 Jul 2005 16:51:01 +0200
Local: Tues 12 July 2005 15:51
Subject: Re: MBSACLI 2.0 /xmlout Parsing Script

Rob Wickham [msft] wrote:
> (snip)
> If you have more questions about the xml attributes, please
> don't hesitate to ask.

Hi,

I would like to see more documentation on the "Check ID" and it's
associated attributes (Grade/Type/Cat/Rank).

And a specific question for those:

When running Mbsacli.exe /xmlout on a computer that is connected
to a WSUS server, I get two different sections in the xml file:

Check ID="500" Grade="5" Type="5" Cat="1" Rank="1" Name="Windows
Security Updates"

and

Check ID="500" Grade="2" Type="5" Cat="1" Rank="1" Name="Windows
Security Updates"

where the Grade="5" version lists the WSUS related patches, while it
looks like the Grade="2" version lists all updates related to all
relevant updates found in wsusscan.cab (available at Windows Updates).

So am I correct to say that Check ID="500"/Grade="5" is WSUS relevant
updates, and Check ID="500"/Grade="2" is standard AU/WU relevant
updates?

--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scriptcenter/default.mspx


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message, you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google