(imported topic written by CCupit91)
We have been using the following relevance to return the numbers of failures of fixlets
number of results whose (status of it = bes action status failed and relevant(computer of it, (source fixlet of action of it))) of bes actions whose (name of source fixlet of it starts with “MS07”)
However this does not appear to return any results for actions created as part of a baseline. Can you suggest how I would go forward to return the results of both actions and baselines? (The full script returns a lot more data than the line above but it’s been simplified).
Chris
(imported comment written by BenKus)
Hi Chris,
The “bes actions” inspector does return all actions (including those in a multiple action group), but the issue with your relevance is that the sub-actions in a baseline do not have a “source fixlet”. The reason for this is to avoid an issue where agents would not take actions if they couldn’t find the source Fixlet (so we are avoiding the issue where a baseline has a Fixlet that no longer exists which causes the baseline to fail).
This behavior can be changed with a BES Advanced Deployment Option in BES Admin. Here is the documentation for this setting:
includeSFIDsInBaselineActions
If set to “1”, causes console to include source fixlet IDs when emiting baseline actions. Emiting these IDs is not compatible with 5.1 clients, and is not usually neccessary. Certain customers wish to emit these ids because of existing specially crafted targetting constraints that use the client’s ‘source fixlet of current action’ inspector to conditionally execute actions.
Note that once you set this setting, it applies to all baseline actions created from that point on.
Ben