- or
No existing idea results
- ~ No ideas found ~
4717 results found
-
Bitlocker Keys
If you could see the bitlocker keys on a device through atera that would be great, especially if you have taken over a new client, and someone has set each of these or the end user has forgotten which account it's recorded with. Or the old IT support company may no longer want to help? You would only need view access.
2 votes -
Add the Ability to Restrict Access to Specific Ticket Templates
Add the ability to restrict which users/departments can use specific Ticket Templates. For example, in previous systems, we had HR submit Onboarding/Offboarding tickets and used the data in the ticket to conduct other actions. We do not want any user to be able to submit an Offboard ticket, only members of the HR team.
1 vote -
Separate AnyDesk Attained / Unattained Setting For Different Sites
Allow admin to set the AnyDesk to set an attained or unattained connection option for different sites or groups. instead of a universal setting for the whole company. The idea is to allow you unattained access to the server farm but also need attaining mode for any user computers.
1 vote -
Automtion Profile Schedule
I need some tasks to run every 15 min, the minimum right now is every 1 hour.
Please add options to create custom interval in minutes2 votes -
disk activity alert time setting
We have been seeing some computers recently hit 100% disk activity and stay that way for several minutes. Occasional spikes may not be a problem, but when a computer hits 100% disk activity and stay that way for a while, we want to be alerted.
The current settings do have the percentage, but having a time frame like the other alerts would make this trigger actually usable. As it is, we had to turn it off because too many little spikes were triggering alerts that we have to manually remove. Being able to set the threshold to something like disk activity 95% or higher for 5 minutes, instead of just the percentage would make this much better.
We have been seeing some computers recently hit 100% disk activity and stay that way for several minutes. Occasional spikes may not be a problem, but when a computer hits 100% disk activity and stay that way for a while, we want to be alerted.
The current settings do have the percentage, but having a time frame like the other alerts would make this trigger actually usable. As it is, we had to turn it off because too many little spikes were triggering alerts that we have to manually remove. Being able to set the threshold to something like disk…
5 votes -
For the customer that uses WFH, if the computer is offline, it doesn’t tell him that it is turned off. It would be nice to show the user the
For the customer that uses WFH, if the computer is offline, it doesn’t tell him that it is turned off. It would be nice to show the user the status and also being able to connect it (wake on lan)
6 votes -
Documentation Management
Are you struggling to keep track of your customers info (i.e., files, addresses, passwords)? Interested in a documentation management integration?
1,260 votes -
Customizable Step by Step Task Automation
I would like the ability to create a step by step automation to control the order of which tasks/scripts get installed and insert reboot/shutdown tasks as needed. The automation would complete when all tasks have been completed in order. Having the ability to stop or continue on a task failure would be helpful as well. This would be similar to the automation of a Task Sequence in SCCM.
15 votes -
Ability to assign ticket to customer, not contact
I want to be able to assign a ticket to a customer without choosing a contact.
31 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 we manage on subsets of computers. In PDQ, to manage 3rd party software we simply created a dynamic collection containing "devices with software 'xyz' installed", which we could then target for automated 3rd party software updates and patches.Take for example our deployment of Visual Studio Code and AutoCAD Inventor. There's maybe 30 users in our company that require VS Code on their computers, and about 40 that require AutoCAD inventor. These are not mutually exclusive lists; there are some users who require both VS Code and AutoCAD Inventor on their computer, and many others that need only one or the other.
We have "overlaps" like this all across our 3rd party software deployments.
I've worked with Atera Support on this and they offered the solution of using folders for 3rd party patch automation - but unfortunately, as an agent can only be a member of one folder at a time, this doesn't help our "overlaps" discussed above.
For the time being we’ve been able to achieve a “good enough/close enough” solution with Atera using the following:
1.) Create 3rd party software bundle and automation profile
2.) Use custom views in the Devices tab to create our “dynamic collections”
3.) Assign Step 1 automation profile to the devices in this viewIt’s Step 3 that gives us the trouble, as the automation profile is assigned to devices in the view, rather than the view itself. When we perform Step 3, it only applies to the devices that were in that view at that specific date/time the automation profile was assigned.
This means that, if we were to repurpose a device and it no longer needed the 3rd party automation profile from step 3, it would still have this automation profile assigned until we remove it manually. Likewise, new devices coming in do not pick up the automation profile either – even though they are dynamically added to the saved view. I think if we had the ability to assign an automated profile to a saved view, rather than the devices in the view at that point in time, that would make Atera even more powerful and beneficial to us.
Thanks for considering!
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…6 votes -
Calendar (Calendly) Scheduler
The service allows customers to easily schedule appointments with our technicians for either an in-person visit or remote repair. Similar to Calendly.com, customers can choose from the available free times in our technician's calendar to set up a convenient appointment. Once the customer selects a time, both parties will receive a calendar invite to confirm the appointment. This process ensures a smooth and efficient scheduling experience for our customers.
8 votes -
Passwords
Notes under passwords needs to be expandable. Most account have addition information and PIN's etc.
Example belowAcc#
PIN#
Serial #
Product key#
Main contact#3 votes -
Ticket Automation Rules - "ticket created" email - stop email loops
The current "Ticket Created email" automation rule works well most of the time. However, when we need to get a third-party support company involved, they often have an equivalent system that sends an automatic "Ticket Created" email, that creates a new Atera ticket, and sends back a "Ticket Created" email, ad infinitum. In our case we had 18 new tickets created in the seven minutes until we noticed the loop. If someone had not been looking at the Unattended queue, it could have been many more.
My idea is for Atera to be able to identify a "Ticket Created email" loop,and add the new incoming "Ticket Created" email from the third-party system to an already created ticket, and NOT send a Ticket Created email.
A possible way of identifying this loop is multiple emails in a short period from a particular email address, with a subject that is the same, except for an increasing number (ie their ticket number)Note: this is specifically for occasions where we have not previously dealt with that third-party support company. Obviously once we have dealt with a third-party support company, we then know that that particular company sends out "Ticket Created" emails, and we can add their email address to the "Ticket Created email" automation rule as an exception.
The current "Ticket Created email" automation rule works well most of the time. However, when we need to get a third-party support company involved, they often have an equivalent system that sends an automatic "Ticket Created" email, that creates a new Atera ticket, and sends back a "Ticket Created" email, ad infinitum. In our case we had 18 new tickets created in the seven minutes until we noticed the loop. If someone had not been looking at the Unattended queue, it could have been many more.
My idea is for Atera to be able to identify a "Ticket Created email"…
4 votes -
set a script-based check run interval
Be able to set the 'run interval' of a script-based check. We are running into issues battery life on laptops and hitting api limits
3 votes -
Need a device filter for assigned threshold profiles
Need a device filter added for assigned threshold profiles. We need to easily filter devices to see which may not have a threshold profile assigned at all. Or that do not have the correct threshold profiles assigned. And then be able to add them via a multi check box.
3 votes -
Custom Assets View
Custom Assets
Should be able re-organize which fields shows in the dashboard, instead of the default Name, Type, Folder and Contact.
Also an option for the date field to have an alert. For example if you are tracking support services renewals for the customer, it should alert you when renewal is within 30 days.
15 votes -
Auto install default remote with Agent
Maybe this is a bug, but I notice on the Android Mobile app (using a fully updated Google Pixel 6a) if you have not run the remote connection from a PC initially, the option to Connect on mobile is greyed out. After connecting at least once to trigger the install it works on mobile as expected.
Maybe this is how it is supposed to be, but it would be nice if the default remote got installed fully when the agent does. Often times when out remote and installing new agents, it is nice to quickly verify full connectivity from mobile before leaving site without having to check from a desktop/laptop first. Perhaps there is a script that will automatically do this (we use Splashtop RMM as our default)
Maybe this is a bug, but I notice on the Android Mobile app (using a fully updated Google Pixel 6a) if you have not run the remote connection from a PC initially, the option to Connect on mobile is greyed out. After connecting at least once to trigger the install it works on mobile as expected.
Maybe this is how it is supposed to be, but it would be nice if the default remote got installed fully when the agent does. Often times when out remote and installing new agents, it is nice to quickly verify full connectivity from mobile…
5 votes -
show device count on customers
The customers table should show how many devices each customer has, and optionally how many are online. Bulk onboarding agents is more painful than it needs to be without this.
3 votes -
Create ticket trigger under ticket automation rules for patching
Trigger for generating a new ticket if patches are applied manually through devices tab by a technician. Seeing as this is a manual action by a technician and not done through automatic patch management it would warrant a ticket being generated for a specific agent/contact with a relevant time entry.
4 votes -
Technician Role permissions
Roles within Admin need to have the ability to have more control of what features each group has.
Under RMM, the "Edit Device" feature is too strict. We want to be able to allow certain technicians to edit device names but not be able to delete them.Setting that can be turned off so that no technicians have the ability to delete anything.
13 votes
- Don't see your idea?