- or
No existing idea results
- ~ No ideas found ~
5051 results found
-
Different default template for tickets created by technicians
It would be nice to have different default form templates for tickets created in the user portal vs. created in Atera by a technician without the tech having to remember to change the template. This would give the ability to add more technical fields automatically when the ticket is created by a tech. It would also allow more customization of ticket automation rules based on whether the ticket was created by a user or by a technician.
1 vote -
Option for old design (for quicker access to all information)
The new design sucks. It takes at least one additional click to see information that was visible right away. I like the customization, but I lose time because 80%+ of the stuff I need now takes longer. Please give the option to keep using the old design.
3 votes -
Update Chocolatey Script to a newer version
Actually Atera is using an old script (Chocolatey 1.1.0) there is for example an issue with the Chocolatey Package for Sonos S2 Controller. So it would be nice, to get an updatet Version.
217 votes -
Add "device name" column to devices table
Add true "device name" column option so that we can list devices by both Atera/friendly name and the PC name.
I renamed a computer in Atera to be more easily identified, but the devices table only shows the custom name. It would be helpful to have them side by side.
1 vote -
patching chrome, find all devices that need that patch and add hock deploy to all
Patching chrome, find all devices that need that patch and add hock deploy to all those devices. This can be used for any patch or cve vulnerability
1 vote -
Fully Deploy Coro Cybersecurity
It would be great to deploy Coro Protection with all necessary permissions to both Windows and Mac devices. Coro is an up-and-coming Cybersecurity Platform that may be a good partner fit for Atera since it is one of the most affordable but effective platforms on the market.
A distribution solution for Coro that includes the activation of necessary permisions, run at start, and removal of existing security app would be great.
1 voteHi,
Thank you for your valuable suggestion. While we won't be implementing this idea in the immediate future, it has been added to our list for future consideration.
Additionally, we offer many solutions that cover Coro offerings.
Best regards,
The Atera Team
-
A precise control over the device reboot from Configuration policy
A precise control over the device reboot from Configuration policy
What we need:
We need to be able to specify a deadline for automatic PC restart and application of updates. Similar to the setting in Group Policy, the deadline time frame can be between 2 and 14 days. After the deadline has passed, devices restart regardless of active hours. Currently, it is between 15 to 180 minutes.What we have in Atera through configuration policy:
• Disable auto-restart with logged-on users
• Restart outside of active hours
• Restart after selected time period
o 15 – 180 minutes
• Allow end users to control device restarts
o Prompt users to restart their devices
o Force restart option after a certain number of prompts
o Option to customize the toast messageWhat we have in MS Windows server Group Policy:
• Turn off auto-restart for updates during active hours
o the PC will not automatically restart after updates during active hours
• Always automatically restart at the scheduled time
o A restart timer will always begin immediately after Windows Update installs important updates, instead of first notifying users on the login screen for at least two days
o The restart timer can be configured to start with any value from 15 - 180 minutes
• Specify deadline before auto-restart for update installation
o 2 – 14 days past the default (7 days) restart date
o Restart can happen inside active hours
• Specify deadlines for automatic updates and restarts
o Updates will be downloaded and installed as soon as they are offered and automatic restarts will be attempted outside of active hours
o Once the deadline has passed, restarts will occur regardless of active hours, and users will not be able to reschedule
o Set a grace period for feature updates and quality updates to guarantee users a minimum time to manage their restarts once updates are installed
o Option to set device to delay restarting until both the deadline and grace period have expired
• Specify Engaged restart transition and notification schedule for updates
o Control the timing before transitioning from Auto restarts scheduled outside of active hours to Engaged restart, which requires the user to schedule
o The transition period can be set between 0 – 30 days from the time restart becomes pending
o Specify the number of days a user can snooze Engaged restart reminder notifications (1 – 3 days)
o Specify the deadline in days before automatically scheduling and executing a pending restart regardless of active hours (2 – 30 days)
• No auto-restart with logged on users for scheduled automatic updates installations
o Only notify the user to restart the computerA precise control over the device reboot from Configuration policy
What we need:
We need to be able to specify a deadline for automatic PC restart and application of updates. Similar to the setting in Group Policy, the deadline time frame can be between 2 and 14 days. After the deadline has passed, devices restart regardless of active hours. Currently, it is between 15 to 180 minutes.What we have in Atera through configuration policy:
• Disable auto-restart with logged-on users
• Restart outside of active hours
• Restart after selected time period
o 15 – 180 minutes
• Allow…3 votes -
Deploy MSI File if it's not installed
When deploying a MSI file through Atera using IT Automations, I need an option where Atera checks if the software isn't already installed before deploying it. I'm currently forced to update all of my servers everyday whether it's needed or not.
6 votes -
Tags via API
Get / amend Ticket tags via API. It would be great if we were able to view/amend/add the tags associated with Tickets
1 vote -
Categorize tickets based on threshold profile that generates them.
Have 2 thresholds for a single company, but have the ability to treat tickets from one threshold differently to another. Ie state the name of the threshold profile and act accordingly.
We want to do this to treat tickets from a new subset of servers differently to the existing servers.
5 votes -
software
Software dashboard where you can see a list of all software on devices that need updating and have the option to update all at once, like you can with the patching dashboard. It would also be great to have an end of life / support section where we can view this info.
1 vote -
Implement a Copilot/Autopilot Feature that automatically closes alerts if resolved or creates c
Here's an idea to enhance automation:
Idea: Implement a Copilot/Autopilot Feature that automatically closes alerts if resolved or creates critical tickets if unresolved. This feature would streamline alert management, reduce manual intervention, and improve response times for critical issues.
1 vote -
passkey support for bitwarden
Currently Atera does not allow registration of a passkey using the Bitwarden password manager browser extension. The passkey is saved to bitwarden, but immediately after Atea reports the device registration failed with "Device registration error | Atera". Could not attach a screenshot.
6 votes -
custom field/form: checkbox with dependencies
When creating Custom Forms, would be nice to have the dependencies option for "checkbox" whe creating a custom field for a custom form.
Example:
1. Is this change request part of an existing project?
Check box option is Yes or No.
Dependencies would now be an option if choosing "Yes"
Text Box 1: to enter project name
Text Box 2: Ticket number of project.4 votes -
Built-In Virtual Display Adapter/Driver - all remote tool capable
I am finding a need for a built in virtual display adapter/driver with the Atera agent that can be utilized by any remote tool for headless machines or machines with their monitors turned off.
This would be especially helpful in many scenarios and avoid on site support or alterations to enable remote capabilities.
1 vote -
MSP Version: All settings per customer
Atera is sold as an MSP tool, but is completely unsuitable for this.
In particular, EVERY setting must be able to be specified per customer, e.g. whether Anydesk, Slashtop or TeamViewer should be installed. This is a given if you want to sell something as an MSP version...
4 votes -
Ability to import MIB files
It would be important to implement the import of Mib (Managed Information Base) files to Atera
It would be very useful to improve a lot the use of SNMP.
Now you work with individual OIDs, if you could import a specifoic MIB per device it would be fabulous.6 votes -
3rd software party report
The reports for patch status and patch deploy does not include 3rd party software status. This is a super essential and not sure why this is not already implemented years ago. We aren't atera users but considering atera but many basics things are missing in atera and a let down
5 votes -
Merge tickets automatically if they include RE: or FW: and ticket contact is recipient or cc'd
When someone creates a ticket via email and cc's someone else, the other person usually replies back and we then have a second ticket created with RE: or FW: infront of the subject line, as the cc'd person did not receive the ticket created response with ticket # etc. there should be a way to have the system automatically detect this and merge it into the correct ticket
30 votes -
Scheduled reports to have customers name on them, as well as changes to default..
When reports are scheduled they are received with no indication of who the report is for, no specific customer name in the email subject or body. Also, the report is default and has no custom options set as to thresholds for computers. There needs to be a way to show the customers name and keep custom options for thresholds.
5 votes
- Don't see your idea?