"Tonne" <Tonne@discussions.microsoft.com> wrote in message
>> Tonne wrote:
>> > Im trying to detect pending hugh priority updates using the API:
>> > Set objSearcher = CreateObject("Microsoft.Update.Searcher")
>> > Set objResults = objSearcher.Search("Type='Software' and
>> > IsInstalled=0")
>> > Set colUpdates = objResults.Updates
>> > count = 0
>> > titles = ""
>> > For i = 0 to colUpdates.Count - 1
>> > If colUpdates.Item(i).MsrcSeverity = "Critical" Or
>> > colUpdates.Item(i).MsrcSeverity = "Important" Then
>> > count = count + 1
>> > titles = titles & vbCRLF & colUpdates.Item(i).Title
>> > End If
>> > Next
>> > If Count > 0 Then
>> > Wscript.Echo count & " pending updates:" & titles
>> > Wscript.Quit 2
>> > Else
>> > Wscript.Echo "No pending updates"
>> > Wscript.Quit 0
>> > End If
>> > But MsrcSeverity only indicates security risc and I cannot find any
>> > other
>> > property that is helpful.
>> > Is it possible?
>> Start here: http://msdn.microsoft.com/en-us/libr...99(VS.85).aspx
> Been there. I believe I have read all topics but to no avail.
I believe the challenge revolves around the concept of "HighPriority"
updates.. and this concept is really unique to the WU/MU environment and is
designed to target the consumer's state of mind. This is really a
presentation value that makes a distinction between "HighPriority" which is
offered by default to all AU/WU/MU clients, and "Important", which is really
a classification for optional updates - but Microsoft doesn't want to really
use the word Optional, or else the update will be completely ignored. At
least by calling them "Important", some consumer will look at them and try
to make an informed decision.
Within the catalog metadata, though, what you'll want to extract to get the
equivalent of "HighPriority" updates is done by Update Classification. In
general, "HighPriority" includes all SecurityUpdates, all CriticalUpdates,
and *some* UpdateRollups or Updates classifications. Unfortunately, a
specific definition of the terms "HighPriority" and "Important" (or
"Optional") is hard to come by.
To that end, though, in a corporate/organizational setting, you probably do
want to script your tool against the Update Classification, including all
Security Updates (or maybe Security Updates that are only Critical and
Important) and Critical Updates (which contains bug fixes for defects that
can affect system stability or product functionality).
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin