358 results found
-
Granular reboot policy after patching
Post-patch reboot policy options for approving a specific time/day window for reboots after a patch has been installed. Some customers have a strict policy for patching and rebooting their endpoints. I am currently using a different RMM and considering a switch to Atera, but this one function is quite important for 2 of my customers and I don't currently see a way to tell your agent that post-patch reboots are only allowed to happen between 10AM and 4PM on Sat or Sundays...
Any way to get the type of granularity added?
2 votes -
Regarding the “Configuration policy”, it would help us a lot if after each Windows Update notification the message indicated how many attemp
Regarding the “Configuration policy”, it would help us a lot if after each Windows Update notification the message indicated how many attempts you still have to cancel this action. and also let the last message indicate that “this process cannot be canceled next time and your laptop will reboot automatically”. Please improve that
2 votes -
Lite WSUS Internally (Atera agent)
You will be able to make a computer, through Atera, a lite WSUS to download the updates and use that WSUS as a repository for the LAN.
1 vote -
1 vote
-
Patch installation progress
It would be amazing to see the same sort of information in Atera that Windows Settings shows when installing updates. Not only would it be great to see which patch is installing, as another customer mentioned, but even better would be seeing the progress of the installation such as a percentage status, like Windows shows.
5 votes -
Granular Schedule under IT Automation
it would be beneficial to be able to schedule IT Automation to run every 5,10,15.. minutes. Right now the best is once a day. If you need it to run more often like every 5 minutes you need to create hundreds of schedules.
2 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.
5 votes -
Include Atera automated activity in Recent Processes
Recent Processes should include any automated activity that Atera does like patches and when it forces a reboot.
7 votes -
Exclude patch configuration on customer
When connecting a configuration profile to a customer sometimes you want to disconnect the profile to one system.
Only way to archive this at this moment is by not selecting the customer and then per device selecting the profile. Imaging a cusomer with 50 systems and one exeption. You have to manual connect the profile to 49 systems....1 vote -
select by wildcard of unwanted patches, like *java* & >"4.5" on specivic devices
We are using a java based tool for connecting PIN paying devices. The tool is build on a specific version of java, any other version will brake the interface. So it woul be cool if we could select blocking based on a partial description of the patch.
1 vote -
Make it possible to do a csv export of installed updates on a device
In case of a ransomware attack the insurance company can request a prove of proper device maintenance, especially when device is no longer running.
At this moment we have to do a manual copy&paste of screen shots, pretty time consuming1 vote -
Scripts to prompt for input
Have scripts to prompt for input. for example, if I wanted to create a new local user and add to the administrators group. I would run a script but have it prompt for the username and/or password.
I have a script created and I can either have a set password for all my clients, BAD, or edit the script for each client I would like it ran on, not ideal.
1 vote -
Improving code reusability and batch flow control on scripts
In order to avoid code duplication between scripts and improve reusability and flow control on business-logic, it would be very interesting to have the possibility to make calls between scripts to other existing scripts. I mean, for instance, make calls on a powershell script to another existing powershell scripts:
switch(some-needed-conditional){
"if - A": [Call-to]::Atera-script-1
"if - B": [Call-to]::Atera-script-2
"if - C": [Call-to]::Atera-script-3}
2 votes -
Apply IT automation profiles to a group of specific devices
Be able to create groups or searches of specific devices (Like only server OS or only workstation OS), and automatically apply IT automation profiles to those devices.
29 votes -
Software Inventory Report To Show Software Installed and Patched By Atera
Software Inventory Report To Show Software Installed and Patched By Atera
It would be extremely useful to see which software is having the patching managed by Atera and which isn't. an additional column with green ticks for software managed and a warning icon of some description for software that is unmanaged.
Software unmanaged by Atera's patching for both Windows and Mac would have the option/button to have Atera reinstall the software so that it becomes managed by Atera's patch management process in the future.
Adding a Select All Unmanaged Software button that selects checkboxes against the appropriate software could allow…
12 votes -
Add the possibility to also copy the schedules when cloning a patch management task.
"I propose the enhancement of the patch management task cloning feature to include the option of copying associated schedules. Currently, when I create a new client, I clone a predefined task named AAA - TEMPLATE with its preconfigured schedule. I have to manually recreate the schedules each time. It would be highly beneficial to extend the cloning functionality to include schedules, allowing for a more efficient and streamlined process. This enhancement would save time and effort by maintaining consistency in default update policies while providing flexibility for clients with unique scheduling preferences."
3 votes -
Log Report for attempts / retries for offline device
We understand that the 'Run on offline' setting will keep the profile in the queue based on the set time. However, we would like to see Log Reports to sho if any attempts have been made. Currently, we can only view report logs for scheduled reports and not a way to check for attempted actions.
1 vote -
Use Local Time Zone for Automation Profiles
The ability to schedule automation profiles to run based on a device's local time rather than using the General Time Zone setting. For example, an OS patching automation profile that runs at 11am will run at 11am across every country/location regardless of timezone difference. Currently, the limitation is that if the profile is run at 11am and your selected timezone in Atera is set to '(UTC) - Dublin, Edinburgh, Lisbon, London', then this creates a problem where the profile runs in the middle of the night for users in Australia, which then means they won't get patched at the right…
50 votesCongratulations on helping shape Atera! The feature you requested is currently being considered for development. Please be patient as the process can take a while or even stall to make way for other features. We’ll update you once it’s been implemented and released!
-
Create tickets from Vulnerabilities / Vulnerability alerts
Allow tickets to be created and assigned from vulnerabilities associated with devices or sites. Eg - If there is a critical update for Microsoft, alert technicians and allow a ticket to be created and assigned to a technician so status of remediation can be monitored and managed.
7 votes -
Patch labels expanded
Expand on the options for patch approval to include "Manually approved" and "Automatically Approved" so you can see which updates have pushed out without your review.
Additionally being able to put patches "On Hold","To review" or "Pending Approval" rather than having to exclude them until you've been able to test and review them in your environment.2 votes
- Don't see your idea?