331 results found
-
Patch pre download
Pre Patch Download. It would be nice if you could schedule the download of patches prior to the patch profile running. Some updates are large and this can greatly increase time to run patching. An option to download the patches prior to the patch installation would help improve readiness of patching and avoid conflicts with other scheduled tasks.
4 votes -
windows update bandwidth
Windows update bandwidth delivery optimization feature. There is no way to currently cap said bandwidth through the Atera Agent. This would be a good feature to have when you have misconfigurations with jobs kicking off over 1000 agents simultaneously only to find out there is no way to see status of said jobs or kill jobs or cap ceiling during business vs non business hours. Also, have the option to pull OS updates via local WSUS server instead of Atera if possible would be a good thing to have.
4 votes -
Allow Ticket Automation to Remove Assigned Tech
Currently when creating ticket automation rules, under the "Set Field Value" for Technician, you a forced to assign a technician either by name or through Auto-assignment. However, in some instances automation rules for setting the tech to unassigned would be very useful.
4 votes -
Endpoint Patch Management - Third Party Software
Updating third Party Software via Chocolatey by Endpoint Patch Management.
It would be nice if we'll be able to update third party software next to windows updates by the endpoint patch management.4 votes -
3rd party patch management automation dynamic grouping
We came to Atera from using PDQ Inventory/PDQ Deploy and were admittedly spoiled rotten with how well that solution worked. This is in the scope of what PDQ refers to as "dynamic collections" - and this is something Atera would benefit hugely from, should they choose to go after this. I tried to keep this brief, and failed miserably - my apologies in advance, and gratitude to anyone that reads to the end ;)
For full context this video does a good job outlining dynamic collections in PDQ: https://www.youtube.com/watch?v=wVWzNhZHPV4
Here's the scenario:
We have ~50 3rd party software titles that…4 votes -
Updates from phone app
The ability to push Windows updates from the cell phone app.
4 votes -
Add agents directly under the IT Automation profile
Add agents directly under the IT Automation profile
4 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.
4 votes -
Startup Automation
The ability to run scripts or automation processes on system start or user login would be amazing. For example, running a script on a system to fix an issue that reoccurs on startup.
4 votes -
Ability to set the agent to run patches when the computer comes online
I would like a way to mark an offline agent/computer to run patches when it comes back online or have it run patches when it has been online for x minutes.
We have field users that are not online very often or are only online after hours and are not getting patched as they should.4 votes -
Saved Script Variables
Ability to store script variable options and have these available as dropdown selection boxes instead of plain text boxes when running the script.
4 votes -
Implement WSUS
Please implement the update retrieval via WSUS so that Atera can download the updates from the central server. This reduces the download traffic.
4 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…
4 votes -
Automated Patching Reports
A report to show which client machines don't have a patch policy applied.
4 votes -
So that new functions can be used after almost every update for the automation profiles, the profiles must be recreated and reassigned to al
So that new functions can be used after almost every update for the automation profiles, the profiles must be recreated and reassigned to all customers/devices
This was already the case when the scheduling setting was changed and also for the "Windows local update" switch
unnecessary additional work for us as a system house.
Simply adapt the database model or better program it
4 votes -
place file on client device from secure atera environment.
i would like to store customer specific files in atera and push them automatically to a specific location on the client. (for example: every new laptop should have an RDP file on the desktop containing the specific customer information about the RDP server.)
I would like to able to automatically copy the files from the secure atera environment to a folder. (place this file on %userprofile%\desktop / c:\users\public\desktop etc. etc.)
4 votes -
Reboot device summary
There needs to be an easier way to see which devices require a reboot. I can't check the tooltips next to hundreds of devices only. The tooltips are too cumbersome!
4 votes -
5 minute snooze capability on after patch reboots.
It would be great if the user's could snooze the reboot after patches. Currently it just tells them it is going to reboot and does it. They have no time to save their work.
4 votes -
Critical Service Keep-Alive
The ability to nominate a collection of critical services that the agent should automatically try to restart if they are ever stopped. Perhaps with a configurable number of retries before raising a critical alert.
4 votes -
Allow multiple-choice variables in scripts
Instead of only supporting fill-in-the-blank/text-box variables, it would help to be able to supply a pre-populated list of options the technician can choose from.
Providing a list the tech can choose from would eliminate the chance of a typo messing up a script, or otherwise choosing an invalid/wrong value.
This means we can possibly condense a dozen or more script variants into one script with a drop-down menu.
4 votes
- Don't see your idea?