Settings and activity
83 results found
-
12 votes
An error occurred while saving the comment -
59 votes
David Yoder
supported this idea
·
-
9 votesDavid Yoder
supported this idea
·
An error occurred while saving the comment David Yoder
commented
Other scenarios include:
Installing applications that require company specific information. Examples would include things like backup agents, anti-malware agents, Outlook extensions, etc. Associating scripts with a customer would eliminate the chances of incorrectly installing the wrong thing, and would really help to organize the scripts.
-
379 votes
An error occurred while saving the comment David Yoder
commented
I agree. There are so many times when I'd like to work on a particular endpoint and I'll ask the end user to turn it on - but I then need to have the end user send me an email or something to let me know the endpoint is ready for me. This is cumbersome and shouldn't be the case with an RMM platform. I should be able to go to a device and create an alert the next time that device's availability changes from offline/unavailable to online.
David Yoder
supported this idea
·
-
2 votesDavid Yoder
shared this idea
·
-
4 votesDavid Yoder
shared this idea
·
-
53 votesDavid Yoder
supported this idea
·
An error occurred while saving the comment David Yoder
commented
10 minutes ago I received an alert for "7 failed login attempts during a time period of 5.00 minutes". That's all the alert text says. If I go to the endpoint, the alert section there reads the same thing.
Naturally, I want to know more about the event log messages that triggered the alert. So I go to Manage -> Event Viewer to see more information. I navigate to the Security log and load up 500 events. I quickly find out that 500 events isn't enough, so I load up 1000 events and scroll all the way down but I still can't see the time and events I need to.
This endpoint is a file server with ~50 users connected to it, so an alert that's 10 minutes old has more than 1000 events logged and is unsearchable in Atera.
So now I connect to the endpoint interactively and load up a prebuilt filter in the Windows Event Log to see what I need to. Why not save time and bypass Atera's tools completely?
The fix for this would be to include some context about the alert. Show me the event log messages that triggered the alert and the context surrounding them.
-
19 votesDavid Yoder
supported this idea
·
An error occurred while saving the comment David Yoder
commented
I'd also like to throw in my feature request here too because I think it falls right in line with this one: https://atera.uservoice.com/forums/936306-ideas-and-feedback/suggestions/45844654-event-monitoring-improvement-v2
-
132 votesDavid Yoder
supported this idea
·
-
11 votesDavid Yoder
shared this idea
·
-
19 votesDavid Yoder
supported this idea
·
An error occurred while saving the comment David Yoder
commented
This is becoming more important on a regular basis for me. New clients are often very surprised that there is no prompt or warning before letting me onto their system. I understand their concern. I think informing the end user of remote interactive connections is far more important than the inconvenient message box Atera added to the agent install process.
An error occurred while saving the comment David Yoder
commented
N-Able had a really nice way to remotely connect to endpoints. In my case, I specified a timeout of 15 seconds and then it automatically connected me, but during those 15 seconds the end user was asked if they wanted to allow or reject the remote connection. Something similar in Atera would be great.
-
66 votes
Hi,
Great news! Your idea has been approved and is planned for implementation.
We appreciate your contribution and will keep you informed about the progress and expected release date, as well as here in the portal.
Best regards,
The Atera Team
An error occurred while saving the comment David Yoder
commented
Here's a good use case:
If I have a client that has my full package, I'll want to make sure they have my anti-malware package in addition to the RMM agent. To do this, I'll want to make a group that automatically adds computers which do not have the anti-malware software installed. Now when an endpoint becomes a member of this group I want Atera to run a script that I specify (this would be to install the anti-malware software). This way, I don't have to worry about whether endpoints have the software because it's being actively deployed precisely when it's required. Set it up and forget it.
This is such a big component of automation in the RMM space that so many overlook.
An error occurred while saving the comment David Yoder
commented
These groups can then be used to bill for devices when generating invoices.
An error occurred while saving the comment David Yoder
commented
Atera has a bunch of monitoring points and data it collects about an endpoint. I'd like to use that data to create dynamic groups. Essentially what I'm looking for is a way to create a group based on the filters available on the Devices page. When an endpoint meets the criteria of the group (or Device page search criteria), it should automatically become a member of the group I defined. When that same endpoint no longer meets the criteria of the group, it should be removed. These groups should be treated like the folders that are currently available, in that they can have Thresholds and IT Automation Policies applied to them, but these groups should NOT be tied to customers only - that should be specified in the group criteria.
David Yoder
supported this idea
·
-
4 votes
An error occurred while saving the comment David Yoder
commented
Here's a great example of why this in important, and many of you have probably see this in your own environments...
I recently turned on Atera's prebuilt Event Log monitors to watch for the event IDs associated with installing and uninstalling applications. I quickly found out that without being able to filter what actually triggers the alert, these were far too noisy. But more importantly, Atera is gathering the wrong information sometimes.
Event ID 1033 is one of the IDs for installing new software when the event source is "MsiInstaller". But because Atera is blindly looking for event IDs alone, it's also getting event ID 1033 from the "Security-SPP" event source which has nothing to do with installing software. So if you've created or tried to create tickets from these notifications, you'll need to weed out the ones that are irrelevant. This isn't just inconvenient, it's actually supplying you with incorrect data.
David Yoder
shared this idea
·
-
6 votesDavid Yoder
shared this idea
·
-
25 votesDavid Yoder
supported this idea
·
-
1 voteDavid Yoder
shared this idea
·
-
24 votes
Hi,
We wanted to let you know that your idea is currently under review by our product team. We are evaluating its alignment with our product roadmap and its potential benefits to our users.
We appreciate your patience during this process and will update you and the public status of this suggestion once a decision has been made.
Best regards,
The Atera Team
David Yoder
supported this idea
·
An error occurred while saving the comment David Yoder
commented
I would like to be able to specify whether a device is Active or Inactive. Furthermore, I would like this setting to be changed automatically based on the Last Seen date. If a managed device has not been seen in say 45 days, it should be changed to Inactive and not show up as a managed device on my monthly invoices to a client.
This is sort of a pain point for me. There are some devices that companies have as backups or are less frequently used. In this case, I can't bill them for a device that hasn't checked in even once during their billing period. Right now I have to manually adjust the managed device numbers on invoices generated in Atera to match what they actually have in production. This could all be solved simply by marking a device Inactive and excluding it from billing.
-
2 votesDavid Yoder
shared this idea
·
-
7 votesDavid Yoder
shared this idea
·
-
4 votesDavid Yoder
shared this idea
·
So honestly, this is a major problem with most RMM providers. It's almost like they don't use their own product to manage their own infrastructure :-)
The best way around this I've found is to use git. I setup my own git server (Gitea) that I use to store my scripts in a public repo. The script that gets uploaded to Atera (or whatever) is literally 2 lines. The Atera scripts just invokes the script from the repo. This has really improved life for me since changes can be made without touching Atera at all - I can update the scripts directly from VS Code and have them run live. I can revert to an earlier version, diff the versions to see changes, etc. And it's portable - so if I decide to move to another RMM provider, it's very little work to get the scripts moved over.