- or
No existing idea results
- ~ No ideas found ~
4971 results found
-
Feature that allows you to send pop-ups/notifications to end points screens
This will allow the IT-Dpt to notify users of things, say the office's antivirus is being changed to another. Just send a pop-up to the screens to remind them to keep their machines on when they leave so the IT-Dpt can use scripts while they're out of the office so no one's work gets disrupted :)
6 votes -
custom software bundles
I have several clients that don't have an AD environment. I am trying to install specialized software not available to the public or that is not on chocolatey. I would like to ask for the ability to create custom software packages with arguments that can be set to install using policies.
Like assign backup Policy that will install my backup on the box and allow me to manage it with the vendor.
Policy that will install a package when agent is installed.
2 votes -
Reports/Dashboard with all the available patches
Reports/Dashboard with all the available patches
2 votes -
Ability to disable the IT Automation Profile directly in the main view,
Ability to disable the IT Automation Profile directly in the main view,
2 votes -
Alerts if a device goes offline and stays there for a certain time
It would be nice to be able to receive an email alert when a device goes offline and stays there for 30 days, for example.
Upon receiving these emails, one could specifically investigate why the device is offline.2 votes -
Agent Renaming
Provide a way to bulk edit Agent Names and Relation for a bunch of agents - perhaps in spreadsheet style.
2 votes -
Let us choose which endpoints are excempt from Remote Access (AnyDesk) deployment
By default AnyDesk get pushed to all endpoints (including servers which have the Atera Agent installed). While this is nice for user Machines - it's less then ideal for servers... Give us the option to exclude machines from AnyDesk Deployment. Or better yet: let us choose on which machines (machine type) we want to install anydesk
8 votes -
Extra information on IT automation landing page
The "Patch Management and IT Automation" landing page only has 1 info about Last Modified date and time. Please include extra info about When was the last time it was run and next time it will run. Similar to Windows Schedular, that way you can have a quick glance on how your IT automation profiles are configured and their health.
1 vote -
Ticket Checklist
The ability to add a checklist to a ticket that prevents the ticket from being closed until everything has been ticked off.
285 votesHey all,
We're considering the development of this feature in the coming months and would love to hear how you'd like to see checklists implemented in Atera.
If you'd like to discuss your needs, please schedule some time for a call here:
https://yakov-atera.youcanbook.me/
All the best,
Yakov
-
Patch Management Exceptions (Product Family Control)
Currently when adding exceptions within a patch management profile you must add the exceptions on a per patch basis. However, we are running into instances were certain servers should not receive specific product updates automatically day one (e.g., SQL, and PowerShell).
It would be nice to have a feature that acts as a wild card exception for any related patches to a product existing or future so we don't have to update the policy prior to every maintenance window.
1 vote -
Remote Live View
Kaseya has this feature that allows an admin to view the user's screen without actually remote controlling in. This allows an admin to check if the user is actively working.
5 votes -
Script-based Threshold Item
The new script-based threshold item is a really great addition, but it highlights an important component missing from Atera - inheritance.
When applying thresholds to endpoints, it's necessary to have thresholds inherit monitors from upstream thresholds. Right now in Atera, only one threshold can be applied to any endpoint at a time. What we need are thresholds that can build upon each other and overwrite values based on where the value changes.
For instance, I'd like to configure a top level (default) threshold to apply to everyone, but then get more specific with thresholds at a customer, and even more specific with thresholds on folders. Application of thresholds is pretty straightforward and goes like this: apply the closest threshold to an endpoint, then apply the next closest threshold and discard any monitors that are already applied to the endpoint, then keep moving up the chain until you reach the top level threshold.
This way, we can get really creative and automate much more than we currently can.
Here's an example. Most of us have an anti-malware solution which has an installer per customer. If inheritance was implemented we could set a threshold profile for the customer that only contains a single script-based monitor to check for the presense of the anti-malware solution, if it isn't found then attach an auto-healing script to the monitor to get it installed. This would then leave the rest of the monitors at a higher level threshold profile undisturbed so they can continue to work on the endpoint as required. Now we don't have to clone threshold profiles to monitor the things we need - that becomes a nightmare to manage when you need to update them.
The new script-based threshold item is a really great addition, but it highlights an important component missing from Atera - inheritance.
When applying thresholds to endpoints, it's necessary to have thresholds inherit monitors from upstream thresholds. Right now in Atera, only one threshold can be applied to any endpoint at a time. What we need are thresholds that can build upon each other and overwrite values based on where the value changes.
For instance, I'd like to configure a top level (default) threshold to apply to everyone, but then get more specific with thresholds at a customer, and even more…
9 votes -
Backup Option with Backblaze B2 Storage
Backblaze B2 storage, by far, is a much better value per GB and an easier sell for customers than Acronis and Axcient. These are the current B2 integrations https://www.backblaze.com/b2/integrations.html
Please add yourself to this list and come up with an option, if technically feasible.
8 votes -
Monitor Carbonite Status
Atera needs to be able to monitor Carbonite status.
2 votes -
Ticket time blocks
Add a feature/option where we can set a mandatory minimum amount for something like on-site support. For example, set it to where each ticket gets billed at one hour minimum, then at 15-minute increments thereafter. Quite a few MSP's, and other small shops have a mandatory minimum of an hour per ticket in their contracts, even if it takes them 20 minutes to fix an issue. That way, they can have more standardized billing practices.
1 vote -
Display interface for SNMP
Display interface for the SNMP: memory use,
5 votes -
report - software inventory - devices without / missing software filter
report - software inventory - devices without / missing software filter
17 votes -
Multiple threshold profiles on device
Add ability to add multiple threshold profiles onto device
e.g. one for device monitoring (disk space, cpu usage) and add another for monitored events or services
129 votesNice! The feature you requested is being reviewed by our product team. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
-
Get Foldername from api
Get the Foldername in addition the to FolderID from /api/v3/agents
6 votes -
Value parsing in OID values
It should be possible to parse specific parts of OID values. Some manufacturers return strings with units in them e.g. "12 PERCENT". Parse the value of that string and cast it to easy comparable data types.
3 votes
- Don't see your idea?