I actually wasn’t looking for power inspectors because I was pretty sure I could figure out something that would work using WMI or IOREG, but if those inspectors you just listed work well, that could be perfect.
I am basically documenting something that I plan to do, hoping that if anyone has something similar already, or tips, like these power level inspectors, they’ll add it here.
As for the FixletDebugger & QnA, I don’t mean to say I would be adjusting how the FixletDebugger or QnA work themselves. I mean that I would adjust the way the BESClient works based upon the fact of QnA/FixletDebugger running on the system as a signal that the person currently logged into that system is doing BigFix related testing and may desire that the BESClient go into an aggressive mode to enable testing to happen much more quickly.
Often I will have the QnA/FixletDebugger open on a system when I am testing things through the console. I will write something in the client tools, then put it in the console, then go back and forth until I get something working… then close QnA/FixletDebugger.
When QnA/FixletDebugger is open I may want CommandPolling to happen every 5 min, and I may want the Max CPU of the client to be 25% or so, and I may want the Report_MinimumInterval to be every 30 seconds… but when QnA/FixletDebugger are closed, I may want CommandPolling to be once an hour, Max CPU to be under 5%, and Report_MinimumInterval to be every 5 min, etc…