329 results found
-
Patch schedule calendars integration to be able to exclude dates from patching.
Patch schedule calendar integration to be able to exclude dates from patching. Some companies have blackout dates where no changes are allowed. Also be nice to see the actual schedule of patching in a calendar form.
3 votes -
Create ticket trigger under ticket automation rules for patching
Trigger for generating a new ticket if patches are applied manually through devices tab by a technician. Seeing as this is a manual action by a technician and not done through automatic patch management it would warrant a ticket being generated for a specific agent/contact with a relevant time entry.
3 votes -
Winget Within NTAuthority/SYSTEM
Winget within NTAuthority SYSTEM space, will help simplifying removal of packages that are un-needed also to stop the CMDLET from being an unknown item within the SYSTEM admin enviroment.
3 votes -
Ability to "Create VBScripts"
No Option for "Scripts"
Below our case already shared with Bill Frankel and your Support Team:
Basically we would like to have the ability to create VBScripts and distribute them to the devices we want them on it.Below one example of how we use the VBScripts to be able to distribute and push the script (before via Ninja without any issue) to All workstations and servers. We normally upgrade the version of the Dental Software that the practices use (PMS and Xray Software) and after the upgrade the install will push the icons by default, so we nee to…
1 vote -
3rd party patch management automation dynamic grouping
We came to Atera from using PDQ Inventory/PDQ Deploy and were admittedly spoiled rotten with how well that solution worked. This is in the scope of what PDQ refers to as "dynamic collections" - and this is something Atera would benefit hugely from, should they choose to go after this. I tried to keep this brief, and failed miserably - my apologies in advance, and gratitude to anyone that reads to the end ;)
For full context this video does a good job outlining dynamic collections in PDQ: https://www.youtube.com/watch?v=wVWzNhZHPV4
Here's the scenario:
We have ~50 3rd party software titles that…4 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 -
Date\time settings configurable to non-US standard
The old scheduler was in 24H format, the new scheduler goes back in time and is only configurable in freedom units. (AM/PM)
Can you please give the option to use a modern standard, or make it configurable? The same goes for the date notation. In Europe we work with day/month/year, not month/day/year.
6 votes -
Delete IT Automation profile in bulk
Delete IT Automation profile in bulk
3 votes -
Automtion Profile Schedule
I need some tasks to run every 15 min, the minimum right now is every 1 hour.
Please add options to create custom interval in minutes1 vote -
Interactively chain scripts with choosing/passing results to the next script
I want to call a script e.g. get-outlookplugins and this one gives back the information about the installed plugins. The last line in the script could be something like:
[[Atera.Invoke ScriptName Enable-OulookPlugin.ps1 PluginName=$ResultSet]]
It should then call the Script Enable-OutlookPlugin.ps1 and give the resultset or an value preselected for the variable PluginName.
For this drop-down selection for script variables would be very helpful.I often use scripts to get an information needed in the next script. Maybe the chain or invoke can be enabled/disabled by runtime if atera sees that the script invokes another one. So in this example the…
2 votes -
Variables field is missing when creating script, only shown when editing a script
The headline says it all
2 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.
10 votes -
Run a script after a reboot is done.
Run a script after a reboot is done.
5 votes -
Set Program to uninstall upon next use
It would be great to have the ability to select a program from the device inventory to uninstall even if the device is currently offline. The task would que for the next time the device is available.
8 votes -
Updates from phone app
The ability to push Windows updates from the cell phone app.
4 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…
9 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 -
Push policies for microsoft
Using Intune for pushing software deployment. They are better integrated with Microsoft. Easier to push policies.
6 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 -
Granulating the "Run on Offline Agents" Option for Automation Profiles
We believe it that it would be more flexible and efficient if you could have each automation profile have its on "Run on Offline Agents" range. As of now, it is one option for all of them. There are certain profiles/scripts that you would want to run on offline for longer periods of time than others. And also there might be some profiles that you do not want to run on offline agents at all. Making it so you can individually control that range with each profile would greatly improve efficiently and effectiveness.
1 vote
- Don't see your idea?