Fixlet Remediation History By Computer Name

Reporting
21

(imported comment written by pcaprio91)

Lee,

How can I edit this report to be able to export it to a PDF file, instead of Selecting Printable Version on left for Printing?

22

(imported comment written by Lee Wei)

pcaprio,

There is no easy way to add PDF export to the report.

The easiest would be to Print to a PDF Converter.

So you are basically printing, but the output is a PDF file.

Lee Wei

23

(imported comment written by SystemAdmin)

Lee Wei

{quote:title=JasonO}Lee Wei,

No good deed goes unpunished…

This report is one of my favorite reports, and I’ve been trying to get the report to work for a computer group. I can’t get the report to do what I want. I think it’s my lack of javascript that’s holding me back.

Any pointers towards getting this to work with a group would be greatly appreciated.

Jason

Hi Jason,

Good job for trying to tackle this. I suspect this has less to do with JavaScript, and more on the Session Relevance. I edited the relevance to pull computer names from a computer group.

Please see the attached Web Reports and see if it is close to what you need.

Lee Wei{quote}

Greate Report,

We ran into an issue where I needed to find out where a certain patch was deployed to,

How hard would it be to add to the above report another filter field like a certaiin patch by date by group

so search a patched group for say “MS09-062” only…

24

(imported comment written by Lee Wei)

Haha,

This is turning to be a Frankenstein of a report.

If you guys are game, I am happy to help where I can.

Here is the modified report, now titled:

“Fixlet Fix Date by Computer Group with Date and Fixlet Name Search”

Hope it works for you.

Lee Wei

  • Removed the attachment from this note and posted a new one below
25

(imported comment written by rmnetops91)

All of these are great. Thanks!

26

(imported comment written by SystemAdmin)

Well, for a Frankenstein report, this report incredible,

thank you again

***** Someone should compile these professional looking reports into a single forum *****

  • so everyone has easy access to this type of resource *****
27

(imported comment written by SystemAdmin)

Lee Wei

Haha,

This is turning to be a Frankenstein of a report.
If you guys are game, I am happy to help where I can.

Here is the modified report, now titled:
“Fixlet Fix Date by Computer Group with Date and Fixlet Name Search”

Hope it works for you.

Lee Wei

The report only seems to run in the BigFix Session Relevance Tester"

from the Bes Reports website the output says “Processing…”

it actually never produces any data

the error is:

Error: fixletname is not defined

Source File: http://bigfixserver:52312/webreports?page=Report&ReportID=165

Line: 434

using XP SP2 / Mozilla Firefox 3.5.7

28

(imported comment written by Lee Wei)

mamacher,

Thank you for spotting the error, there is a bug in the report.

I have fixed it.

Please let me know if it does not run.

The latest report is here:

http://forum.bigfix.com/viewtopic.php?pid=33477#p33477

Lee Wei

29

(imported comment written by SystemAdmin)

Works Great…

Thank You

30

(imported comment written by rmnetops91)

I found a possible bug in this report. We noticed a patch showed applied on a few particular systems, when it really wasn’t. It was in fact a fixlet that was part of a baseline, submitted as an “offer” that was relevant to these particular systems. In other words, the report included it in the results as installed, when really it was only relevant as an offer.

The fixlet shown as installed in the report was: MS09-055 Cumulative Security Update of ActiveX Kill Bits - Windows Server 2003 SP2 (Superseded)

Interestingly, that same fixlet in the actual offer action status, doesn’t say “(Superseded)” next to it, but it does in the report results.

31

(imported comment written by Lee Wei)

A fix or an applied patch is defined as:

  1. The Relevant Flag of the Fixlet evaluation is False.

  2. The Last Become Nonrelevant field has a time stamp. This is the date/time when the client reported the fix.

So you can test the Fixlet and Computer combination in question by running the following relevance:

(name of computer of it,

relevant flag of it,

(if (exists last became nonrelevant of it) then (last became nonrelevant of it as string) else (“Not applied”)),

name of fixlet of it)

of results from (bes fixlets whose (name of it = “fixlet_name”))

of bes computers whose (name of it = “computer_name”)

The report will have a filter where “Relevant Flag = False” and “Exists Last Became NonRelevant”.

Lee Wei

32

(imported comment written by RobertKurt)

I’m new to IEM (Bigfix), so bear with me if you can. I’ve done a lot of work in SQL, and I’m trying to figure out a couple of things.

First, I’m trying to figure out a way to join information from the computer and content tabs in Bigfix Web Reporting.

after I can get that,…

Second, I’m trying to be able to create a report that will show:

Computer(name), fixlets remediated, fixlets applicable, percent compliant, work group(eventually another local field will be used in place of this)

The results will be pulled into a spreadsheet, grouped by work group, so that each computer can be seen as far as its compliance, the work group’s compliance avg, and then, the work group’s complaince averages are shown in a pretty graph.

Any help would be GREATLY APPRECIATED!!!

Thanks,

Robert

33

(imported comment written by rmnetops91)

I “think” I understand what your saying. Can you think of any scenarios where a fixlet might be “Relevant Flag = False” and “Exists Last Became NonRelevant”, but didn’t actually get “installed”.

34

(imported comment written by Lee Wei)

Not really, the scenario you described should not have happened.

What constitutes “Installed”?

It should be shown in the Fixlet relevance, with all the different statements.

  • If the relevance is TRUE, the patch is missing. Relevance Flag = true, and not installed
  • If the relevance is FALSE, the patch is not required, or already installed

So we should be able to reconcile that way.

35

(imported comment written by Kenz91)

Why aren’t reports like these exportable?

36

(imported comment written by Lee Wei)

Kenz,

You have correctly noted that the “Export to CSV” link in Web Reports is for the built-in reports.

Custom reports will have to provide their own export functionality.

For the moment, I suggest:

  • Click on the “Printable Version” link to run the report with minimal frills.
  • Do a Control-A to select the entire report.
  • Paste-Special with Text only into Excel.

Lee Wei

37

(imported comment written by Lee Wei)

There is a related report that filters by a single Computer, rather than a Computer Group:

http://forum.bigfix.com/viewtopic.php?id=5445

Lee Wei

38

(imported comment written by SystemAdmin)

Hey,

Does this report also pull non-windows results?

if not, is there a report similar that could pull both windows and non-windows fixlet history.

thanks,

Baraq

39

(imported comment written by Lee Wei)

Baraq,

If you look at the report, there is a clause that limits the content to “Patches for Windows (English)”.

display name of site of it contains 
"Patches for Windows (English)"

You can change that to include other sites of interest.

For example, replace that with

name of site of it as lowercase contains 
"patches"

This will pull all Fixlets in any sites with the word Patches.

Lee Wei

40

(imported comment written by mgardner28)

I made changes like you suggested above and they work fine. I would like to pull all Fixlets from only sites
"Patches for Windows (English)“
and
"Update for Windows Applications”
.

If I change the relevance to be this: and display name of site of it contains “Patches for Windows (English)” or “Updates for Windows Applications” it just sites at processing forever.

I’m obviously not doing something correctly. Any suggestions?

Thanks,

Mark