(imported topic written by Macideus91)
Sitting here watching BigFix run it hit me like a train…wouldnt it be nice to be able to see the number of fixlets per machine while in Computer View? SO we can see what machine just added 20 fixlets to the total of needed fixlets without going one by one to find out who the problem child is…
just thinking
Mike
(imported comment written by Lee Wei)
Sounds interesting. You can add a Retrieve Property to return the information you need.
Here are some examples.
You probably don’t want this because it returns all relevance Fixlets, Tasks, Analyses and Baselines for all sites.
number of relevant fixlets of sites
Here is an example of one that will pick out only relevant stuff in the Patches for Windows and Updates for Windows Applications sites
number of relevant fixlets of sites whose (name of it =
"Enterprise Security" or name of it =
"Updates for Windows Applications")
This is probably a useful form that will count only relevant Fixlets - no Tasks or Analyses.
number of relevant fixlets whose (not exists values of headers
"X-Fixlet-Type" of it or (value of headers
"X-Fixlet-Type" of it as lowercase !=
"task" and value of headers
"X-Fixlet-Type" of it as lowercase !=
"analysis")) of sites whose (name of it =
"Enterprise Security" or name of it =
"Updates for Windows Applications")
Lee Wei
(imported comment written by nberger91)
We have similar broken down by severity, works well -
number of relevant fixlets whose (value of header “x-fixlet-source-severity” of it as lowercase = “low”) of site “http://sync.bigfix.com/cgi-bin/bfgather/bessecurity”
(imported comment written by SystemAdmin)
Is there a way to make this property not show Globally Hidden Fixlets?
(imported comment written by SystemAdmin)
Can someone help me determine why the following statement is returning ‘0’ for all my computers? I’m trying to create a retrieved property to indicate how many OS patches are required for each system.
number of relevant fixlets whose (not exists values of headers “X-Fixlet-Type” of it or (value of headers “X-Fixlet-Type” of it as lowercase != “task” and value of headers “X-Fixlet-Type” of it as lowercase != “analysis”)) of sites whose (name of it as lowercase starts with “patches for”)
(imported comment written by Lee Wei)
Tim,
The reason is a historical one.
Many many years ago when BigFix first started creating content (Fixlets), we worked only on Windows patches and named the site “Enterprise Security”.
So your statement will return nothing on Windows computers. Try the following instead.
number of relevant fixlets whose (not exists values of headers “X-Fixlet-Type” of it or (value of headers “X-Fixlet-Type” of it as lowercase != “task” and value of headers “X-Fixlet-Type” of it as lowercase != “analysis”)) of sites whose (name of it as lowercase starts with “enterprise security” or name of it as lowercase starts with “patches for”)
There is also another option, which is to get the information on the server side, and do the reporting and tallying with data already reported from the clients. The Session Relevance example would be:
(name of it, number of relevant fixlets whose (display name of site of it as lowercase starts with “patches for”) of it) of bes computers
Note that on the Server side, there is an additional property call “Display Name”, which is used to provide an alternative name, such as “Patches for Windows (English)” for “Enterprise Security” and also localized languages.
Lee Wei
(imported comment written by SystemAdmin)
Lee, I just tried the clause you listed in QNA and it also returns 0 as the result, but the computer I’m running the query on has not had Tuesdays patches applied yet so I would expect it to show something. To double check the results, I tried it again on a different computer and got the same result, my console reports that the second machine needs MS12-018, MS12-019, MS12-020 (KB2621440), MS12-020 (KB2667402).
I was trying to create a single retrieved property to tell me how many “OS Vendor” patches were required for each system. We have a wide variety of systems here, Windows, Mac, Linux, Solaris, etc. Since I can’t even get it to work under my Windows Client (v8.1.634.0), I’ll revisit the issue after I get everything upgraded to v8.2.
(imported comment written by Lee Wei)
The above client relevance statement will only work under the “client context”. The Fixlet Debugger and QNA on UNIX/Linux will not work.
On Windows and using the Fixlet Debugger, you want to switch to the “client context”, meaning the statement is sent to the actual TEM Client for evaluation, rather than by the Fixlet Debugger itself.
In the Fixlet Debugger, go to Menu–>Debug–>Evaluate Using–>Local Client Evaluator
Lee Wei