1

Closed

Compliance Checking

description

Hi,
 
Thanks for this handy tool. This may not be a "bug" so to say, but when I run the "Update Compliance" for computers and return one of a number of colums with status = "Not Installed" and others with status = "Not Applicable" then the compliance status = "Not Applicable". I was expecting the compliance status in this case to be "Not Installed".
 
I reason that it is because the update is not approved in my WSUS? Would you agree it should be the way I am expecting it or?

file attachments

Closed Jul 19, 2014 at 1:34 AM by AngryTechnician

comments

AngryTechnician wrote Aug 30, 2011 at 8:59 PM

I think your expectation is right: Not Installed is the more notable status here, so should be returned as the overall status.

This is down to my possibly flawed thinking when deciding how to rank the different status types in order to reconcile them. The overall status should reflect the 'worst' state of any of the machines. Rethinking this, Not Applicable should really be considered the best status, since if an update doesn't apply, the machine is considered up to date without any action needed.

At the moment, the rankings are as follows (higher rank indicates a more desirable status):

Installed = 6
InstalledPendingReboot = 5
Downloaded = 4
Unknown = 3
Failed = 2
NotApplicable = 1

My proposed change would be as follows:

NotApplicable = 6
Installed = 5
InstalledPendingReboot = 4
Downloaded = 3
Unknown = 2
Failed = 1

Does this seem sensible?

wrote Aug 30, 2011 at 9:03 PM

Vegas205 wrote Sep 2, 2011 at 1:33 PM

Hi,

Thanks for your quick response. Yes, the proposed change seems to be the correct logic.

Regards,
Tony

AngryTechnician wrote Sep 5, 2011 at 9:04 PM

This change has now been committed as change set 8329. It will make its way into the next beta release, which will probably be after I sort out [workitem:282].

AngryTechnician wrote Sep 5, 2011 at 9:05 PM

([workitem:282] is the Export function issue; apparently wiki links don't work in issue comments.

wrote Jan 4, 2012 at 8:19 PM

Vegas205 wrote Jan 4, 2012 at 8:19 PM

Hi Again,

After checking on this item after the BETA 3 release it seems to still fail for me. Is the BETA 3 file version 0.2 ??? Attached is my screen shot. Thanks.

AngryTechnician wrote Jan 6, 2012 at 8:14 AM

Beta 3 is still listed as version 0.2 in the binary; I forgot to increment the version number. I have reproduced this (again) and will try to take a look at the weekend.

AngryTechnician wrote Jan 7, 2012 at 8:39 PM

OK, I'm pretty sure I have actually this correct now. I'd managed to confuse myself with the change in ranks but your test case is showing the compliance status as Installed now, and I've run several more tests for other scenarios that are also working correctly.

Beta 4 is now published with this fix, and the version number has been updated this time.

wrote Jan 7, 2012 at 8:40 PM

Vegas205 wrote Jan 9, 2012 at 8:56 PM

Looking good so far now with BETA 4. The compliance checking seems to be working as expected. Looks like export is working for me as well which was one of my other bug posts. Thanks alot for a useful tool to extend some functionality to WSUS.

wrote Feb 14, 2013 at 1:12 AM

wrote May 16, 2013 at 6:14 AM

wrote May 16, 2013 at 6:14 AM

wrote Jun 14, 2013 at 7:58 AM

wrote Jul 19, 2014 at 1:34 AM