359 results found
-
using the Description filed to setup automation ru
it would be awesome if we can use the description field in the ticket to setup an automation rule, for example > if the description filed contain a word > assign to technician
1 vote -
API: Include Ticket # in response when I create a ticket
As it stands, if we want to use the API to create a ticket and then interact with it, we need to create the ticket and then constantly poll the API to find the ticket.
Since any API request has to involve a response from Atera servers regardless, could the Ticket# of the created ticket be included in the response?
This could be expanded to other API calls, i.e., when you create a customer, alert, contact, device, etc.1 vote -
Patch Management Notifications
Patch Management Profiles should include options to configure a custom message to pop-up for the end users. It would be nice to be able to give users a warning notice letting them know of the updates and reboot. Give the users the ability to postpone the reboot for the number the Admin allows (3 or 5 times) and after the final warning the updates are applied and rebooted.
15 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.
2 votes -
Include Script execution on ticket automation
automation that triggers a healing script upon ticket creation , offering immediate response to issues and potentially resolving them without manual intervention
5 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.
5 votes -
3rd Party Software Updates
First of all, It would be nice to have either detailed documentation on how to setup and use IT Automation and Patch Management. I have not been able to find anything that goes into fine grain detail on how to setup IT Automation and Patch Management. I have kind of had to experiment. Not a good way to learn or use a product.
Second, More needs to be done to help with updating 3rd party software, e.g. Google Chrome. I know how to create a bundle to push Software Bundles out to new devices, but I need a way to…
1 vote -
Refine Task Automation with more scope for failed devices
From what I understand from the Helpdesk I just spoke to when a automated task such as sfc /scannow or dism commands occurs or even other tasks that require a system that does not need a restart the following applies.
1. Offline devices will try to perform the task when they start>>which is fine
2. Online devices that fail for example due to "pending other operations described above say needs a restart for updates" the task will fail and NOT try again.Would it not be better to have the option on automated tasks to have a tick box for…
3 votes -
Automation Job Live Overview in the device details
Hi team,
I would love to see some live overview directly on the device detail page that shows automation jobs that are currently running on that device, as well as jobs that will be following with timestamps. This takes away the need to run the "Last process" reports and I see what is happening on my device in real time.
8 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 -
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 -
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 -
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…
16 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
- Don't see your idea?