Help Please -- Web Reports - Patch Compliance Report

Reporting
1

I live and die by these reports, having the need to share the output with management. All of a sudden this report stopped working, does anyone have a variation of this report that they use to show patch compliance for a certain month(s). It would need to be similar to this, I really need help asap. If you could share the report, that would be great. I’m attaching the one that I’m having a problem with and would like to continue to use this one, but any report that offers monthly patch stats would be helpful. thanks, Sno.
samplehelp.pdf (158.2 KB)

2

That report hasn’t been maintained for years and I don’t know of an equivalent version (fingers crossed someone has one). So perhaps we can get this one working for you again. What errors are you running into? Have you tried using other browsers? Fiddled with any browser settings?

3

no changes to the browser, used edge, chrome and mozilla and the data just comes back incorrectly. I’ll have several dozen machines that need patching but the reports will say they’re 100% patched. I know that to be a lie. I’ve leaned on these for years and can use a fix or a similar report. Thanks.

4

Ok… so no errors but bad/stale data? Have you tried restarting the Web Reports service? You could be dealing with a caching issue.

5

Ah ich Version of Bigfix are you running? We had some issues with 11.0.4. needing Support by HCL.
In case of having Bigfix Compliance license this might also bei useful vor Patchreports.

1 Like
6

@Snojack were you able to resolve this with the service restart? Any updates?

7

Please follow this link

and set EnableCSPHeader = 0

8

No luck, still scratching my head.

9

Is your web reports server running on Windows or Linux?

The fact that the report runs but the data is wrong points strongly to a caching issue somewhere. I know its probably the first thing you did but have you cleared all of your browser cache then restarted Web Reports and tried to run the report again? If you can try that I do have another, more aggressive tactic you can try but I don’t want to start with that stuff before confirming the basics are done first.

10

Windows is the platform. We restarted the service. Still no luck yet.

11

tried that, still having issues…

12

what version of bigfix are you running? is it 11.0.4?

1 Like
13

yes, 11.0.4 is the current version we’re on…

14

@Snojack

The base object used in this report is bes fixlets. This is filtered by whose (exists results ot it). This means that the core data for the report depends on the client reporting back to BigFix the applicability of the Fixlet relevance. This includes information like:

  • first became relevant : time
  • last became nonrelevant : time
  • relevant flag : boolean
  • remediated flag: boolean

If such data isn’t present, then the client has not evaluated the fixlets for some reason. This could be due to reinstallation of the client, creating data under a new Computer ID.

It could also be the result of the client being tied up waiting for an action to finish, which would prevent the client from entering the evaluation loop. I’ve seen this behavior when using PowerShell to execute a script, but the PowerShell executable is already running something else.

If you open the computer record for one of the problem machines in Web Reports, does it show the patches in question to be either relevant or remediated?

Does the Console show the same patches to be relevant to the problem machine as Web Reports does?

15

There is a defect in bigfix 11.0.4 that does not properly return all relevant fixlets on all devices though webreports and the bigfix API(which uses webreports). We ran into this issue. We opened a support ticket with HCL and they gave us a patched version of the webreports executable. That solved the problem.

4 Likes
16

Thanks for letting the community know. This has been a thorny issue.