Handling unexpected errors in relevance

Content Authoring
1

(imported topic written by steelcastle)

I have some automatic groups being created and am finding that some computers do not get placed into these automatic groups because of errors in relevancy. Here is an example of a relevance that checks a windows OS for WMI:

if

(
exists

wmi)

then

true

else

false

I have some few clients that generate errors because of issues with wmi, this error generation on one client shows this:

Error: The expression could not be evaluated: Windows Error 80041001: Generic failure

So there is a problem with wmi that needs addressed on the problem client. The consequence to this is that the computer does not go into the automatic group. Is there any way that I can trap an error to put into another automatic group for me to seek out and address these computers?

2

(imported comment written by BrianPGreen)

Yes. If you can identify the problematic relevance, then I think the group definition for the “Bad Computers” computer group could be something like:

not exists true whose ( )

For example, if the relevance that is causing the “Generic Failure” is “exists wmi”, then your group definition can be:

not exists true whose ( exists wmi )

3

(imported comment written by steelcastle)

Thank you! That worked great!

Interesting that you can use “false”:

not exists false whose (exists wmi)

and get the same result.