We have a patch policy with a schedule using group targeting. In the console, the group shows 59 devices. 12 of the devices have not been seen in greater than 5 days.
When the multi-action group is generated, 36 devices are shown as targeted. What could be the reasons why not all of the 59 are targeted?
I think I did read somewhere on this that the relevance for the group is re-evaluated on each device. But, I’d expect each device to consistently maintain that relevance.
The target group relevance:
(version of client >= “18.104.22.168”) AND ((exists true whose (if true then ((Exist settings “CLO_STAGE” whose (value of it as string as lowercase = “Prod” as lowercase) of client) AND (Exists true whose (If true then (exists (operating system) whose (it as string as lowercase contains “Win” as lowercase)) else false))) else false)) AND (not (exists true whose (if true then (member of group 127975 of site “CustomSite_SEC_-2d_General”) else false))))
group 127975 is an exclusion group that is currently empty (relevance for this group is set to false) right now.
I would think that even devices not seen in 5+ days would be targeted. They just might miss the action since they were powered on. Are devices excluded from the target due to relevance of the individual components (not relevant for the any of the patches in the policy).
Do any of the WebUI logs show this detail? I did look in …\BigFix Enterprise\BES WebUI\WebUI\logs but it didn’t seem to explain how the targeting logic was done. I didn’t try verbose… wanted to check here first. Thank you!