>From my way back memory, this used to work in WQL on CM07. probably still
>works in CM12... but yeah, it's not actually looking at updatescanstatus--it's
>looking at status messages from clients, and limiting to "only within the last
>2 days" -- you need to limit by date otherwise a statusmessage of 11423 from
>179 days ago could drop the machine into the collection.
So not exactly what you are looking for... but might be ok...
select SMS_R_SYSTEM.ResourceID
from SMS_R_SYSTEM
join sms_statusmessage on
sms_r_system.netbios_name0=sms_statusmessage.machinename
where sms_statusmessage.messageid='11423' and
datediff(DD,sms_statusmessage.time, GetDate()) <2)
Note you only get a 11423 scan failed for any reason.
On Tuesday, October 6, 2015 11:43 AM, Nick <[email protected]> wrote:
#yiv0977255558 #yiv0977255558 -- filtered {font-family:Calibri;panose-1:2 15 5
2 2 2 4 3 2 4;}#yiv0977255558 filtered {font-family:Tahoma;panose-1:2 11 6 4 3
5 4 4 2 4;}#yiv0977255558 p.yiv0977255558MsoNormal, #yiv0977255558
li.yiv0977255558MsoNormal, #yiv0977255558 div.yiv0977255558MsoNormal
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;}#yiv0977255558 a:link,
#yiv0977255558 span.yiv0977255558MsoHyperlink
{color:blue;text-decoration:underline;}#yiv0977255558 a:visited, #yiv0977255558
span.yiv0977255558MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}#yiv0977255558
p.yiv0977255558MsoListParagraph, #yiv0977255558
li.yiv0977255558MsoListParagraph, #yiv0977255558
div.yiv0977255558MsoListParagraph
{margin-top:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;font-size:12.0pt;}#yiv0977255558
p.yiv0977255558msolistparagraphcxspfirst, #yiv0977255558
li.yiv0977255558msolistparagraphcxspfirst, #yiv0977255558
div.yiv0977255558msolistparagraphcxspfirst
{margin-top:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;line-height:115%;font-size:12.0pt;}#yiv0977255558
p.yiv0977255558msolistparagraphcxspmiddle, #yiv0977255558
li.yiv0977255558msolistparagraphcxspmiddle, #yiv0977255558
div.yiv0977255558msolistparagraphcxspmiddle
{margin-top:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;line-height:115%;font-size:12.0pt;}#yiv0977255558
p.yiv0977255558msolistparagraphcxsplast, #yiv0977255558
li.yiv0977255558msolistparagraphcxsplast, #yiv0977255558
div.yiv0977255558msolistparagraphcxsplast
{margin-top:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;line-height:115%;font-size:12.0pt;}#yiv0977255558
span.yiv0977255558EmailStyle22 {color:#1F497D;}#yiv0977255558
.yiv0977255558MsoChpDefault {font-size:10.0pt;}#yiv0977255558 filtered
{margin:1.0in 1.0in 1.0in 1.0in;}#yiv0977255558 div.yiv0977255558WordSection1
{}#yiv0977255558 SCCM 2012 – Old post that I didn’t find any answers to.--- I
am also “unaware of any way to access the contents of v_UpdateScanStatus via
WQL to create the target collections ”Also“Anyone know the reasons behind not
exposing more of these diagnostic views available in SQL so they are available
in WQL for use within the console outside of reporting?” -Nick- From:
[email protected] [mailto:[email protected]] On
Behalf Of Michael Roach
Sent: Tuesday, November 4, 2014 4:19 AM
To: [email protected]
Subject: [mssms] Strategies for automating fixes for WUA issues I’m in the
process of migrating our data center to ConfigMgr 2012 R2 CU3 and am tired of
having to manually run SQL queries and copy the results into a collection
direct membership to push a remediation script for various software update
issues. For example as I migrate machines from the ConfigMgr 2007 to ConfigMgr
2012 site some of the systems are failing to update their local policy to
reflect the new Update Source resulting in a ‘Group policy conflict’ scan
error. This is easy enough to fix with a script but I’m unaware of any way to
access the contents of v_UpdateScanStatus via WQL to create the target
collections (and manually changing the SQL behind a query rule in the DB is not
something I can do here). This is just one of a dozen common issues that I’d
like to be able to simply automate away an initial remediation attempt. My
question to the group is what strategies are you employing to automate the
remediation of software update scan / client issues when Microsoft exposes the
data we need via SQL but is not making that available to us in the console via
WQL? Is there some way that I can use Compliance Items to check for scan
errors and then have the collections build off of those? Thanks! P.S. Anyone
know the reasons behind not exposing more of these diagnostic views available
in SQL so they are available in WQL for use within the console outside of
reporting?
