I have a policy that uses monitor sets to email me when free space on the c: drive is below 10%. I would like to create a exception group for computers that I don't want to be alerted to this condition. I am not sure how to do this and am looking for ideas.
My first guess would to be modify the view that you have assigned to it. If you create a copy of the original and then within the advanced filters do a NOT THISGROUP or NOT COMP1 AND NOT COMP2 AND NOT COMP3.
Sorry, I'm rushing this response. Hope it makes sense!
I agree with Rshaw - you can certainly get deeper into this with the use of machine groups for assignment or go further in detail to run a procedure, rather than sending an email, that checks for Custom Field exclusions.
You might want to give my blog a read - it deals with the need to control when and where policies get applied, which, in turn, deploy the monitors.
We have a custom field which is basically "NoTenPercent" and the general policy to apply the 10% monitoring looks for "workstations where the NoTenPercent field isn't YES" (I'm simplifying this a bit). If we get a machine where we want to bypass that, there's an agent procedure whose job is just to apply that flag to the field. (And another to "undo" that in case we want to go back to 10% monitoring later.)
I'm intrigued that anyone still does "10%" as an across-the-board monitoring threshold for disk capacity. I just dumped a set of calculated thresholds from our Smart Monitor, and not one common disk size uses a calculated threshold of 10%. The sub-100G systems actually trip at a tad over 11%, but once you cross 100G, the threshold we use drops to barely over 9% and declines steadily from there to just over 3% at 8TB.
With around 2800 workstations in our MSP practice, we had just 10 disk space alerts last month, and 40% of those were from a company we onboarded that month, where the alerts were generated before the daily maintenance tasks took effect. As far as servers go, we had 31 alerts last month across 384 agents, but these have an average of 3.4 volumes per agent, so that's really 31 alerts against 1305 volumes. Looking at these tickets, each one was resolved either through removal of old data (iTunes on workstations was #1), or - for most servers - increasing the storage to accommodate the growth that had occurred. Not one ticket was closed as a false alert or "NTF". As the server disk volumes are increased, the thresholds automatically reduce accordingly, so there's no manual effort related to monitoring disk capacity.
Of course, we have exceptions - a set of kiosk systems with an override to deal with their almost maxed out 40G HDDs, and the two Video Recording systems that manage the disk utilization within 200MB of total capacity that needed the calculated threshold to get set below this level, but that's a small fraction of the environment - about 12 volumes in total with threshold overrides.