NO limits organizations to ONE Agent Policy per Target type?
I am new to NO, and I like it but some of the choices I am being forced to make are a bit crazy.
I want to test if a software is installed, and if not, trigger an install of it. Agent policy seems like the place to do that, but if I create this as a standalone policy, I am forced to choose between it and the default Windows Workstation Policy?
In other words, I have to cram all agent conditions etc into ONE policy?
That sucks because the "if not, install it" will get triggered by any of the other conditions.
I suspect I should be accomplishing this some other way, like a single script that detects + installs purely in conditions, but that is not ideal either.
How crazy/stupid am I being here?