Taking Action as Master Operator

[JasonWalker]

To some degree the client does some of that…if your Baseline as a whole includes relevance like ‘windows of operating system’ then only the Windows machines evaluate the component relevance for each sub-component. You could also have top-Level baseline relevance for OS version, or for Server vs Client, etc. but that may require dividing up baselines in different ways.

[ageorgiev]

It’s been a while since I dug into this in detail but at the time that wasn’t the case. I had verbose logging for a client that was not relevant to the baseline relevance at all and you can see in the log it was still evaluating all the relevance of the sub-actions from that same baseline one-at-a-time and Support at the time told me “this is by design / expected behaviour” even though it didn’t make any sense to me. I hadn’t heard anything announced that agent processing changes have been implemented but if you are sure that’s how it is, that would be a step in the right direction…

[mesee2]

The challenge with not being an Master Operator is there are / were things you needed to be an MO to do like work with the Automation plans. Is this still a requirement, can a normal user be given the ability to work with automation plans, add, edit, schedule and not be an MO?