We have recently being having issues where when servers reboot for Windows updates the Atera service doe snot start up in a timely manner, this results in constant alerts for the servers and unable to access them to resolve this issue.

We set the startup type of the agent to "Automatic (Delayed Start)" however when the service is started again it appears to overwrite this setting and reverts to simply "Automatic" which means we are back to square one.

I appreciate that other Atera users prefer the Automatic startup type for speed however for us it is simply not reliable enough.

What I would propose is the ability to customize the service startup type at an organization level to allow Atera users to retain maximum control of their setup.

I would envisage this being in the main Admin area for the agent or potentially even being part of an IT Automate policy so that it can be customized on a more granular level for each custom/set of devices.