Ability to differentiate Automation Profiles based on OS
Our company runs several policies/Automation Profiles on client workstations, but profiles like reboots should not be applied to servers just because they are included in the client assignment.
We have found over the last month that manually excluding servers tends to result in missing a server or two, and still having an issue.
We propose that policies and Automation Profiles be set up with the option to exclude types of endpoints, like servers, from being added when creating or running a policy and/or Automation Profile.
We understand that Atera currently query for "some registry keys that are server only" when being installed, and this is what tells Atera what endpoint is what.
I don't know if querying what type of OS is running is easier to help differentiate (W10 v W Server 2016 Standard, for instance).
WNC Support
shared this idea
-
Rei Sato
commented
To add to this, would like to specify OS (Windows, macOS, Linux) to which profiles should apply, as powershell scripts for example only work on Windows.
According to the tech it should just "fail" when run against other OS's, but since the Automation profile screen has tabs to select which OS a policy should apply against, expanding this feature is requested.