Skip to main content

generating a compliance summary report based on an authorization list

i hope someone doesn’t respond to this post and say… hey it was already done – right here!  i searched for awhile and couldn’t find any canned reports someone had done to display security update compliance by machine based on an authorization list.  i’m no sql expert, and my skillz at writing sql queries are not m@dd by any stretch of the imagination.  however, i was able to finagle what appears to be decent output.

here’s a screen capture of the query output we’ll be working with:

image

 

this report contains links that will generate another report of the specific updates used in the calculation of the summary:

image

 

background

the reason why we find this report immensely useful is because it limits the data set based on your authorization list.  when you execute the report, you will have to provide two things:

  • a collection id – which set of machines do you want to look at?
  • an authorization list id – which authorization list do you want to check against?

this way, when you look at compliance numbers, they are based on the things that you authorized for your environment and not just the massive list of things that could potentially apply to a machine.  this seems to matter in larger environments where updates are governed by their necessity and not as simple as going to windows update and running install everything!

 

installing the report

if you notice in the first report, the scope id is the 6th column of the list.  the reason it’s in there is because the second report requires it, otherwise, you’d get a return of everything that’s applicable, and not just the ones you authorized.

you can get the two report MOFs required to generate this report from system center central at this LINK.  one issue with reports that utilize drill through models is that the relationship doesn’t come through properly during the mof export.  because of this, i removed the “linked” relationship and exported them.  once you import the report mof, you’ll need to make the following changes:

  1. open the Compliance Summary Report by Collection and Authorization List report.
  2. under the Links tab, change the link type to Link to another report.
  3. select the report named Compliance Summary Report Detail by Computer.
  4. by default, the MachineName prompt will fill in with column 1.  this is valid and does not require changing.
  5. change the column id for AuthListID to 6.

image

 

that’s it!  now when you click the arrow for a computer in the main report, you’ll be able to drill through to the detailed report.

 

caveats

before you go off and try this, here are a few things to understand:

  • if the machine is failing to scan or failing to send up state messages related to the update compliance state, these will not show up in the report and will skew your numbers.
  • from technet: “Unlike other software updates state messages that are replicated up the hierarchy to the central site, state messages for deployments are replicated up the hierarchy to the site where the deployment was created. Software update deployment enforcement, evaluation, and compliance information will be missing from reports when they are run from a site higher in the hierarchy than where the deployment was created.”
  • the client version must be >= 4.00.
  • this report is defined to pull microsoft security updates only.

 

 

hope you find this helpful.  i can get a list of about 1000 machines in about 30 seconds so the return is not too terrible. :)

Comments

Popular posts from this blog

how to retrieve your ip address with powershell...

update: this is how it’s performed in powershell v3 as demonstrated here.(get-netadapter | get-netipaddress | ? addressfamily -eq'IPv4').ipaddress update: this is by far the easiest.PS C:\temp> (gwmi Win32_NetworkAdapterConfiguration | ? { $_.IPAddress -ne $null }).ipaddress
192.168.1.101
are you laughing yet?  i know you probably find this topic amusing.  it's really interesting though.  whenever you get over it, i'll do this in the standard cmd.exe interpreter and then in powershell to show you what kind of coolness powershell does.done?  okay, good.  this is an interpretation of a demo that bob wells did at our smug meeting.  hope you like it.i should tell you, it's not as simple as the title would lead you to believe.  i like doing that little slight-of-hand thing since it gives the impression that i'm painting a very easy target on my back for your criticism (though it's probably true in other ways)!  the idea is that we want to retrieve just the ip ad…

understanding the “ad op master is inconsistent” alert

i use the term “understanding” loosely.  this is by far no definitive guide on this particular alert, just a few things i have picked up in my attempt to understand it.let’s look at the context of the alert:The Domain Controller's Op Master is inconsitent. See additional alerts for details.
first of all, it gives very little information.  the only particularly useful detail is that it indicates which server is having the issue.  other than that, just a spelling error as there are no additional critical alerts to look at for details.this rule, as you know, comes from a sealed mp.  therefore, we can’t modify anything in it except the overrides.  the couple i’ve tinkered with are:interval (sec) log success event to begin with, interval (sec) is just set way too high.  the default is 60 seconds.  why on earth would anyone want to know that your op master consistency may be off, every minute?  actually, i could think of a few reasons, but really, it’s overkill.  the way the script works…

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point. even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch.I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.DETECTIONstatus messagestake a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough material to …