Settings and activity
10 results found
-
55 votes
Ahmet Hayirli
supported this idea
·
An error occurred while saving the comment -
11 votesAhmet Hayirli
supported this idea
·
-
2 votesAhmet Hayirli
shared this idea
·
-
381 votesAhmet Hayirli
supported this idea
·
-
749 votesAhmet Hayirli
supported this idea
·
-
83 votes
We plan to expand our AV integrations in the near future. Thanks for your feedback!
Ahmet Hayirli
supported this idea
·
-
21 votesAhmet Hayirli
supported this idea
·
-
1,619 votes
Congratulations 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!
Ahmet Hayirli
supported this idea
·
-
2,306 votes
Hi,
Thank you for your valuable suggestion. We recognize this is an important request in IT, however we won't be implementing this idea in the immediate future, it has been added to our list for future consideration.
We continuously review user feedback to inform our development priorities, so your idea remains on our radar.
Best regards,
The Atera Team
Ahmet Hayirli
supported this idea
·
-
1,491 votesAhmet Hayirli
supported this idea
·
We already have a script that reliably shows which user caused the failed logon and from which source (logon type / origin) the failed attempts came from.
We have attached this script to the threshold, but its execution and output are not shown in the device tasks.
As a result, every time an alert is triggered, we still have to manually run the script on the affected device in order to quickly see which user and which source caused the failed logins.