391 results found
-
Updates from phone app
The ability to push Windows updates from the cell phone app.
5 votes -
Killing Two Ants With One Shoe
Title: Add Domain Account or specified accounts to Atera and to Shell/Scripts
Currently Atera uses system and current user for scripts and shell. Adding Domain credentials to Atera would eliminate storing passwords in clear text under scripts and make management easier for accessing domain resources - network drives etc...
With a system account - there is no access to domain network resources like drives. Yes there are work arounds using net use and possibly adding a domain account under Services.msc - Atera - Logon - domain account. What if the domain account breaks?....I mean yeah, there is a possibility to…
11 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.
12 votes -
Customer Data should be Variables for Scripting
All the data that you store for a cutomer
- customer_name
- phone #
- email domain
- etc.should be variables that can be setup to be passed to the IT Automation script variables when you run a script that has variabels
this way i can setup 1 IT Automation policy that has {[companyname]} variable... which then gets the companyname from the company that the agent is in...
this would reduce the # of IT Automation policies we need to setup from many to 1... making everything way more dynamic
2 votes -
History of all script executions with script output and script version executed
We need to be able to see all executions of a script, with the exact code that was executed and the script output. This history should be available from the Script (to see all the times it has been executed and on what devices) and from the Device (to see a history of all the scripts that have been executed on the device).
Each script execution should be saved in a separate entity with the date, time, device, script code, execution parameters, result and script output.
8 votes -
MacOS .pkg software upload support
We get MacOs in our environment here and there and have a 3rd party antivirus that needs remotely installed and if needed other PKG type applications would need to be installed as well silently. We need Atera to support .PKG file types and know how to install on a MAC via the upload script method.
Having to manually script it is very messy and requires a lot of third-party integrations and sometimes permissions need to be adjusted at the machine level locally. There needs to be more support for silent installation of applications for MacOS for us who can't guarantee…
3 votes -
Software doesn't exist
In Ninja, we could install software based on whether it existed or not. This allowed me to automatically install the software if it was uninstalled for any reason or was missing from deployment. Even was able to generate an alert to the techs
1 vote -
Delete IT Automation profile in bulk
Delete IT Automation profile in bulk
3 votes -
When using Configuration Policy, Windows Update. Wake computers to restart
Hi,
If using configuration Policy and Windows Updates with restart outside of active hours on. Have a feature to wake computer at a time outside of hours to allow them to restart to apply updates
4 votes -
Variables field is missing when creating script, only shown when editing a script
The headline says it all
2 votes -
Run a script after a reboot is done.
Run a script after a reboot is done.
5 votes -
Push policies for microsoft
Using Intune for pushing software deployment. They are better integrated with Microsoft. Easier to push policies.
7 votes -
2 votes
-
IT automation via Heartbeat Schedule
I would like to see a selection of "when device becomes online/available" added to the schedule on the IT automation page. There are many times when an oddball device is powered on for a few hours and it isn't powered on during the automation schedule window. There may be another way around this, but running the IT automation task when the device comes online would be a great feature to have.
2 votes -
Decline Windows non-critical updates
Need the ability to completely decline Windows non-critical updates. The only option is to postpone.
2 votes -
Patch Exclusion - Remove the patch from showing in the patch needed view
Please can you look at adding the functionality to remove any patch showing in the agent patch available status if the admin has removed or excluded said patches from availability. This will make the view cleaner as currently the agent machine reflects in the needing patches when actually they are up to date.
13 votes -
Windows updates installed with Atera are not synced with local client PC update history
According to Atera support, Windows Updates installed with Atera are not synced with the local Client PC update history - so no possibility for the client to check the patch level on the device. In my opinion this is a bug, not a feature.
40 votes -
Working with automation profiles via API.
Working with big amount of machines through webpage is very slowly and uncomfortable. But for now it is the only way to work with automation profiles.
Could you add an option to work with automation profiles via API?
To get all names of existing profiles, to get information about some particular profile, to get list of endpoints which are applied to it, to add some new or exclude some of them from particular profile and so on... It would be nice to work with it from PowerShell instead of waiting for loading page with each of these requests.
Thanks in…3 votes -
Overall improvement of Patch Management
This needs an overhaul and the following additional features would be an improvement.
Scheduled Device Scan for Updates
After updates have completed If a user is logged in prompt to reboot every set period of time until reboot accepted.
After Updates If a user is not logged in attempt to reboot to schedule based on local device time.
Allow local admin credential injection in order to force updates through that require a device to not just be turned on but logged in to work.
Approve or Reject updates and set priority for security and critical updates based on the CVE.
…
329 votes -
Associate scripts with a customer(s), or per customer scripts
You may have scripts that contain information that pertains to only a single customer. In order to prevent engineers from running those scripts potentially on another customer, it would be incredibly helpful to be able to do either:
A. Associate scripts with a customer(s)
B. Have scripts that can only exist with a given customerAn example of a use for this: Deployment of an external or otherwise unsupported security product that requires a customer GUID that is supplied as an argument for an MSI installer. This feature would prevent a mismatch for this scenario from occurring.
9 votes
- Don't see your idea?