Skip to main content

Feature request to fix Console to Endpoint communication after unexpected reboot or network disruption

  • 6 August 2024
  • 1 reply
  • 25 views

I have noticed that if a Windows endpoint unexpectedly reboots or there is a network disruption while processing a worklet or worklets, the Console will lose the ability to communicate to the endpoint for around 24 hours. That's how long it takes for the back end console maintenance to run and reset things. Even removing the device from the console and reinstalling the agent has no effect. The device is still stuck on stupid in the console. We would love to have a feature to reset the communication immediately so we can continue to work on systems without having to tell users they now have to wait until tomorrow for what they need. Even if its an api feature, that would be fine. 

Is this causing anyone else headaches? We use worklets to push software to endpoints and are in there daily doing that. I don't know that this would bother customers that are just using Automox for Windows updates. If others are having problems though, maybe Automox can help us out. I am tired of opening tickets on this. 

Hey @David_Mitchell !


I got this feedback submitted to your CSM as well as to our Product Team.

For real time Roadmap updates you can always check https://discover.automox.com/c/roadmap or reach out to your CSM.

 

Additionally, I recommend registering for our Monthly Roadmap Webinar where you can ask questions and see what features are in flight: https://www.automox.com/register/automox-product-roadmap-webinars

 

 


Reply