Settings and activity
10 results found
-
55 votes
Ahmet Hayirli
supported this idea
·
An error occurred while saving the comment -
12 votesAhmet Hayirli
supported this idea
·
-
2 votesAhmet Hayirli
shared this idea
·
-
383 votesAhmet Hayirli
supported this idea
·
-
757 votesAhmet Hayirli
supported this idea
·
-
85 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,648 votesAhmet Hayirli
supported this idea
·
-
2,317 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,498 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.