364 results found
-
Patch Management
Atera needs to have a single pane of glass view of the overall compliance for a device of ALL updates for a device.
Under Devices the "Available Patches" should include ALL Security & Critical updates for both Microsoft Windows or Server and include Critical Updates for 3rd Party Patching.
11 votes -
The "Windows Insider Pre-Release"-Updates should not be suggested to be installed.
The "Windows Insider Pre-Release"-Updates should not be suggested to be installed. In productive systems this is a no-go for us.
2 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 -
[RMM Patch & Automation][IT Automation] Run on next schedule
Can the Atera Automation be configured to follow the set schedule time and if the device is offline to not execute the automation until the next schedule time ?
The problem: Atera Automation will proceed as soon as the device is back online and I want to avoid that. I want the Atera automation to wait until the next scheduled time. User may be in a webinar or web meeting and not a good time for the PC to re-start or shutdown, etc.2 votes -
Align OS Patch Approval levels with OS Patch categories
OS Patch Approval settings should be at the same level of granularity as OS Patch Management, i.e., provide the ability to set postponement for Security Updates, Definition Updates, Update Rollups, etc. independently rather than just at the Critical vs Noncritical levels.
1 vote -
Attach files to script
Would like an option to add files to a script, the other RMM we worked with had this option.
7 votes -
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 -
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.
9 votes
- Don't see your idea?