Currently it does not show if another technician is logged into a device via Active AnyDesk Session. It would be awesome if the UI could have an indicator like AnyDesk icon changing colors if a technician is already remotely connected to a device.

With the customer devices there is a check box in front of each device, I would also like this if you are in the customer folders to be able to mark them directly and edit them.

Allow branding of the remote agent with both name and logo if possible. Also incorporate into the agent a ticket creation area.

Currently we can not connect to any PC in network if that PC does not have internet connection. due to which we have to use another tool to remote.
just for one purpose we are forced to use two different remote tool which does not make sense.

It will be great , if Atera add this feature in future release.

Delete Agents / Machines which haven't reported back to Atera for a specific amount of time.

For example, if a machine doesn't dial into Atera for 5 months, it will be deleted from Atera automatically.

It would be ideal to have it a system wide setting, client setting, or folder setting.

Please add a way to copy a folder instead of just single file at a time

Have permission request for remote connection based on technicians and not based on devices. Some technicians would require to ask for permission when remoting into the customer's computer.

I have issues with 3 out of 10 units having issues with enrollment requiring a registry wipe and service restart on those devices.

I'd like to automate this by being able to either check the ATERA directly or by caching this on my own hosted service as a proxy.

Unfortunately, the AgentId found on the device is hashed and therefore I cannot test it against the Agent API to check if it has indeed reported in.

I would like to be able to ensure that the Atera Agent has all the access that it requires to aspects of the macOS via an MDM but this needs a bundle ID which requires the agent to be signed.

I'm quite surprised that the agent isn't already signed to be honest.

It will be a good thing to know which contact is attached to an agent, by using API.
Actually, we could only know, for an agent, wich customer.
Some things like that aren't exist on API.

The Atera Agent installs Homebrew for you on your Client Mac's however, currently this is inaccessible from either Terminal or Scripts. If you want to install software just now that requires password authentication, this just isn't possible from Atera, unfortunately. If we could utilise Homebrew from Terminal or Scripts, we can get around the authentication issue. This would be very useful.

Alternatively, if Atera can provide a method of including credentials during Software or Software bundle installations then this would resolve the issue.

This may seem finicky but I've been asked recently. Is there a way to verify that the agent updates haven't been tampered with like they were with other MSP agents ( Kaseya... ). Some of my customers are getting a little antsy about having an agent on their servers and workstations. I think it would be helpful if there was a way to visibly show them that the agent updates were scanned and safe.

Appreciate any insight on this. :)

There are times where splashtop is not needed and it would be nice if the installer had the option to not install it rather than remove it from all clients.
Also sometimes privacy policies on certain computers do not allow IT administrators to install remote connection software.

Is it possible to run Splashtop from the PSAtera command line? At the moment I can get agent information from PowerShell but I cannot start remote sessions to customers' pc.

For internal reporting, we would like to list all the agents having a specific Windows service running or having a specific windows role (like hyper-v).

Change name directly agent when clicking on it.

Could you include a descriptor with the MAC address in the agent? For devices with multiple interfaces, I cannot tell which address is associated with which interface.

Our customers have old computers we have to support. For example an old server running an old software that can't be installed anywhere else. They need it for archive. We must have Atera on this in order to monitor it, inventor it etc. Like Screenconnect, please keep support for older OS.

Calculate device time difference from current actual time (per time zone). The difference could be in positive and negative minutes that should be visible in devices, reports and alerts.
Many services do relay on stable time and therefore is it very important for us to see the offset in Atera and even have an alert if difference is more than +/- some minutes.