Granular Splashtop / Anydesk deployment
Dear Atera Team,
Firstly, I’d like to express our gratitude for the incredible value Atera has brought to our business. Your platform has revolutionised how we operate, driving efficiencies across our workflows and empowering us to deliver outstanding support to our customers. It’s been a game-changer for us!
As enthusiastic users of Atera, we occasionally encounter small challenges where we feel there’s an opportunity to enhance the platform even further. One such area is the management of remote desktop functionality.
We have a use case where some of our customers require us to have remote access to their devices, while others specifically request that we do not. It would be immensely beneficial if Atera offered the ability to configure remote desktop settings on a per-customer basis. Ideally, this would allow us to enable or disable the remote desktop agent (e.g., Splashtop or AnyDesk) during the customer creation stage, or as part of the initial Atera agent installation process.
While we’re aware of the registry key method to disable these agents post-installation, it’s not always feasible for environments with hundreds or even thousands of devices, particularly when some are rarely online. Attempting to retrospectively disable remote desktop in such cases can take significant time and effort, which isn’t always practical.
By introducing this functionality, Atera could not only simplify compliance with individual customer requirements but also enhance deployment efficiency and reduce the administrative overhead for teams like ours.
We’re huge fans of Atera and are passionate about supporting your journey as much as you’ve supported ours. We hope this suggestion is something that resonates with your vision for the platform, and we’d love to see it come to life!
Thank you for considering this request, and please don’t hesitate to reach out if you need further clarification or details.