I’m trying to create automatic computer using the following “Relevance Expression”:
if (exist (computer name) of ((names of computers of it ) of results whose (status of it = bes action status failed) of (bes action whose (id of it is 124354)))) then (true) else (false)
I want to create a computer group with computers that reported failed status for action 124354. What is wrong with my expression? Is it possible to do that? The relevance work in web reports, I just have to change “computer name” words to real computer name.
It works in Web Reports because you are using something called, “Session Relevance” in your relevance string. Session relevance is relevance that only the BigFix server can evaluate. A client cannot evaluate results of bes action.
If you run this in Fixlet Debugger using the local client evaluator it should fail.
What are you going to do if that action failed with the resulting automatic group?
Can you tell us what the failed item is?
It is usually best to use the original relevance or similar to determine if something still needs to happen. Also, if it is a custom action, it could tag the machine in some way.
We setup Forced Reboot 48h after patches installation and we reapply patches baseline 3 times if there was a failure. We want IEM to show a warning for a user before each reboot. Unfortunately IEM does not show any window to a user after the second failure and forces the reboot automatically. So my idea was to create 4 actions. 1st attempt - all computers, 2nd - computers that failed in the first action, 3rd - computers that failed in the 2nd action… Do you have any better idea?
You should not handle reboots in the post action dialog of the baseline or task that is actually installing something.
You should instead have something that uses the requires restart actionscript to tag the machine as needed to reboot.
You should have another action that will prompt the user to reboot if the machine is tagged as needing a reboot, but only if the uptime of the operating system is greater than X days so that you don’t constantly prompt users to reboot.
You can have another action that will reboot a machine immediately IF and ONLY IF no user is logged on when a pending restart is detected.
