352 results found
-
Scheduled automation on next start-up in case of failure
It would be fantastic if, within automations, we could have a checkbox option, for instance, to launch certain scheduled tasks during the next startup if the scheduling couldn't take place due to the agent being offline, as many RMM platforms already offer. Nowadays, with the rise of remote work and mobile workstations, it's even harder to schedule certain tasks at a fixed time.
2 votes -
Triggers for the automation profiles
Run the profile when the script threshold hits, The script is checking if a reboot is required, if so, the automation profile will run. Regardless of the schedule/
2 votes -
Script Category Permissions
Add options to control access to scripts, possibly by choosing which script categories can be accessed against roles in Atera. This would allow technicians to be given access to scripts relevant to their job role but not higher-level scripts which they should not be able to access or run.
5 votes -
disk management exclude drive
Ability to exclude drives in disk check and defrag automation.
11 votes -
See authors of scripts
I would like to see who has created a particular script.
3 votes -
set 32 vs 64 bit behavior on software bundles.
We would benefit from the ability to install 32 bit versions of software onto machines running a 64 bit OS. Currently this can be done machine by machine via script, but this is tedious.
2 votes -
option to disable bitlocker when rebooting after patching
When rebooting a windows machine after patching check if the machine has a bitlocker encrypted boot drive and disable bitlocker encryption.
Optional (and maybe harder, so maybe don't bother):
Have an option to set -RebootCount (for how many reboots bitlocker should be disabled) or set it to >1 as some updates reboot multiple times and check after reboot if patching is done and re-enable bitlocker.Alternatively:
Have an option to start a script at the beginning of the patch process so we can do is ourselves with Powershell's Suspend-BitLocker cmdlet.2 votes -
IT automation profile failure alerts
It would be great if we can add a threshold around patch management to send alerts out if patches are failed to apply, or if the automation task does not run for some reason
19 votes -
Make Ticket Source editable
Ticket source is a field we can't change at the moment. However, it does show up in the Ticket Summary Report.
All tickets manually entered ticket are now classified as a Phone call. As we also use tickets to track projects, or enter them when someone walked to my desk the widget on the Ticket Summary dashboard will contain incorrect statistics.
Please make the Ticket Source field editable, so we can enter our own values.
1 vote -
Queue scripts individually for offline machines for when they come online
The ability to queue scripts individually from the machine page for offline machines to be executed when they next check-in/come online.
9 votes -
Queue for the 3-rd party updates in the IT Automation profiles
With Kaseya: if you are doing a schedule of patching, if it is all on the same time, you can spread the entire patching into 60 minutes. If there is 60 devices, it will spread it automatically, so behind the scene it will do the deployment, we don’t need to create different profiles.
1 vote -
Change how exclusions operate
If in the Task area under OS Patch MGT a box is unchecked do not show any available patches anywhere ever. If unchecked here I shouldn't have to exclude them anywhere and I should not see them anywhere.
By them showing it appears as if things are missing when in reality they were never wanted. In my case it is Hardware updates, we do not want this automated as it has caused major issues in the past running these automatically so we prefer to send these manually if needed.
2 votes -
Fix issues with Atera automation when using WSUS server
Most of our automated scripts fail because of "Unable to fetch information from agents." errors. Most of these agents are online and available during script run.
Atera should be able to run an automated script without reporting failure when WSUS is in use.
2 votes -
Queue Scripts to run in order
It would be great to be able to queue scripts in an automation profile to run one after the other rather than all at once. This would allow for running "close software" before an edit to the software is made or allowing for the first script to complete a task that is needed for the second script to run.
7 votes -
offline and failed
I do daily patching on my devices. Since not all devices are always online at the time the report ist generated, it would be nice to see a difference in the generated report between a device, where the installation failed and those, which were just offline.
3 votes -
Ability to use parameters in software bundles
I'd like to be able to set parameters per software within a bundle.
5 votes -
Patch Automation Profiles - assign patching by the server not the whole client
Would like to select some but not all servers for patching, and set different time schedules for different servers for the same client which you cannot currently do - it's all or nothing and this does not work for many clients
1 vote -
Improved Hard Drive Monitoring
It is crucial that my company and I are able to monitor the health of our clients hard drives, and currently the only option is a S.M.A.R.T. alert, which doesn't seem to function in my experience. An improved version of this or a drive monitor script / display on the device dashboard would be perfect.
7 votes -
Company Wide Policies
We have moved from Ninja to Atera and the difference in Policies is a bit disappointing.
With Ninja we could have company wide policies applied to "Servers" or "Workstations" and a Mac, Windows and Linux option.
However, we don't seem to have an option like that with Atera, instead we have to make sure to manually apply server polices to servers and workstation policies to workstations.
Each Policy would also give us the option to setup alerts and scheduled tasks/script which doesn't seem to be in Atera.
For example, we have a 2 main policies set for all servers. "Scheduled…
8 votes -
Deploy certificates through Chocolatey/Homebrew
Deploy certificates through Chocolatey/Homebrew
1 vote
- Don't see your idea?