What is the best way to determine whether a patch is installed?
My coworker and I are at odds as far as the best way to scan for a KB article update. He is in favor of checking the file version of the affected files that are updated. I am in favor of checking for the KB article by number. Both seem to have their pitfalls. For the file version check, since the value is a string, you can't just say "greater than" because that doesn't mean the same thing to a string so any other patch or sp that updates that file, the scan becomes invalid. In the KB number check, if the patch gets superceded or replaced, then the scan fails. Does anyone have a better way than either process or more reasons one is better than the other ? TIA!
July 13th, 2012 3:58pm

Let Microsoft's scan engine (SCCM/WSUS) decide... Run the following VBScript (call it CCM_UpdateStatus.vbs) and examine the resulting .csv... Usage: CCM_UpdateStatus machinename --- On Error Resume Next Dim strComputer Dim objWMIService Dim propValue Dim colItems Dim objFSO Set objFSO = CreateObject("Scripting.FileSystemObject") Set objFSOOutputFile = objFSO.OpenTextFile("C:\Temp\CCM_UpdateStatus_" & WScript.Arguments.Item(0) & ".csv" , 2, True) Set objWMIService = GetObject("winmgmts:{impersonationLevel=impersonate}!//" & WScript.Arguments.Item(0) & "\Root\ccm\SoftwareUpdates\UpdatesStore") Set colItems = objWMIService.ExecQuery("Select * from CCM_UpdateStatus",,48) For Each objItem in colItems objFSOOutputFile.write ",Article," & objItem.Article objFSOOutputFile.write ",Bulletin," & objItem.Bulletin objFSOOutputFile.write ",Status," & objItem.Status objFSOOutputFile.write "," & vbCrLf Next objFSOOutputFile.Close
Free Windows Admin Tool Kit Click here and download it now
July 13th, 2012 4:38pm

Let Microsoft's scan engine (SCCM/WSUS) decide... Run the following VBScript (call it CCM_UpdateStatus.vbs) and examine the resulting .csv... Usage: CCM_UpdateStatus machinename --- On Error Resume Next Dim strComputer Dim objWMIService Dim propValue Dim colItems Dim objFSO Set objFSO = CreateObject("Scripting.FileSystemObject") Set objFSOOutputFile = objFSO.OpenTextFile("C:\Temp\CCM_UpdateStatus_" & WScript.Arguments.Item(0) & ".csv" , 2, True) Set objWMIService = GetObject("winmgmts:{impersonationLevel=impersonate}!//" & WScript.Arguments.Item(0) & "\Root\ccm\SoftwareUpdates\UpdatesStore") Set colItems = objWMIService.ExecQuery("Select * from CCM_UpdateStatus",,48) For Each objItem in colItems objFSOOutputFile.write ",Article," & objItem.Article objFSOOutputFile.write ",Bulletin," & objItem.Bulletin objFSOOutputFile.write ",Status," & objItem.Status objFSOOutputFile.write "," & vbCrLf Next objFSOOutputFile.Close
July 13th, 2012 4:42pm

SCCM SUP & WSUS client is smart enough to work all of that out for you so no need to create any more work for yourself. Also sounds like you have a buggy patch somewhere in your sup deployment package. You can rebuild your SUP distribution package again and this time exclude all expired and superceded updates. If you dont want to do this, check the windowsupdate.log on a client looking for the id of the update that is failing in the scan result, then find this in your updates source folder open it up and you should see the kb number on the .exe file and then you can just remove the one update from your deployment package, update list and management list.
Free Windows Admin Tool Kit Click here and download it now
July 13th, 2012 5:28pm

SCCM SUP & WSUS client is smart enough to work all of that out for you so no need to create any more work for yourself. Also sounds like you have a buggy patch somewhere in your sup deployment package. You can rebuild your SUP distribution package again and this time exclude all expired and superceded updates. If you dont want to do this, check the windowsupdate.log on a client looking for the id of the update that is failing in the scan result, then find this in your updates source folder open it up and you should see the kb number on the .exe file and then you can just remove the one update from your deployment package, update list and management list.
July 13th, 2012 5:32pm

Do you use the compliance reports that are built in to SCCM or are you thinking these are valid? http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
July 13th, 2012 10:10pm

Do you use the compliance reports that are built in to SCCM or are you thinking these are valid? http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com
July 13th, 2012 10:15pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics