Atera Agent Startup Speed
Currently the Atera agent on Windows is configured as a service that has a startup type of "Automatic (Delayed Start)". This means that after a reboot, it can take the agent more than 5min to show up as online in the console.
I don't know about everyone else, but I like to work quickly and this is a real holdup. There are times that I'll be connected via Splashtop and it will quickly reconnect upon reboot. However, other times Windows may have pending updates to install, in which case Splashtop will disconnect because it times out waiting for the agent to come back online. When this happens, I know that I'll need to wait at least 5min longer than when the endpoint is actually back online.
Right now I can mitigate this by using my AV console, because it starts up as soon as the endpoint does. I'm thankful that my AV console allows me to run scripts - I have one that (re)starts the Atera agent so I can get connected again shortly after the endpoint is back online. But I feel like this is so unnecessary - the AteraAgent service on Windows can easily be switched to the "Automatic" startup type and allow us to reconnect much faster.
David Yoder
shared this idea
-
Adrian Rhodes
commented
Good morning David,
We actually have the inverse problem to yourself, we require the Atera service to be delayed as some of the servers we support fail to start the service in a timely manner and we end up having to remote on to them using alternate methods to start the service.
I have logged a separate idea on here suggesting the ability to customize the startup type at a company level or via an IT Automation policy for more granular control.
I find it odd that we seem to have the exact opposite issue with the software as I would expect consistency across the platform.
Kind regards,
Adrian Rhodes