KACE Product Support

No. Your best bet is to make a duplicate of the label for this specific deployment and modify the filter criteria.

Andy's right about the best solution, but there's a quicker one that I use only for temporary, quick-n-dirty fixes:

Create a new label, what I like to call a "compound label": a label that refers to other labels. The new label's logic is all machines that have your original label but not machine X. Use this new label for your MI or script.

There are down sides to this, of course. First, if you change the name of your original label, even a little bit, you break this compound label that depends on it. Second, the compound label might not be applied correctly until machines have done two check-ins: one to get your original label, and the second to get the compound label.

If you intend something supportable, then you're better off with the permanent solution Andy suggested: editing your original label's SQL to include and exclude exactly what you mean. Sande

Thanks, for detailed suggestions. I think there should be a option in KBox for Exclution of some machine.