Product Ideas Portal

Got an idea for a new feature? Maybe a tweak to make something work even better? Wish there was an integration with another product to make you even more productive? You've come to the right place.

The Product Ideas Portal lets you submit whatever product feedback you have, good, bad, ugly, and anywhere between.

Want to stay anonymous? Don't worry, no email address or name fields are shared on the public portal. You can create an account which lets you vote on other people's ideas and receive updates when your idea's status changes.

To learn more about how an idea becomes a feature, check out this infographic.


16 Vote

Change the Defendpoint client install logic in a way that it will perform the update after the next reboot BEFORE user logon (machine startup phase) and force the reboot after the update is complete.

Problem:

The current Defendpoint client installer is updating around 30000 clients in our enterprise environment. Since around summer 2018 the installation logic changed in a way that a reboot is pending after the update is complete. Without the reboot certain Defendpoint rules might not be triggered.

Forcing the reboot after the update is not possible, because the user will most likely be at work (approx. 95% of our computers are laptops and are only turned on during business hours), and a reboot will delete any unsaved data. To avoid that we are not forcing the reboot immediately but latest after 6 hours.

However this is still not a great user experience, because in that 6 hours the Defendpoint client is not 100% reliable.

 

Suggested solution:

Change the Defendpoint client install logic in a way that it will perform the update after the next reboot BEFORE user logon (machine startup phase) and force the reboot after the update is complete. This will prevent the user from any further interaction and greatly enhance the overall user experience and at the same side avoid a timeframe where the Defendpoint client waits for the reboot and is not working correctly.

  • Guest
  • May 29 2019
  • Future consideration
  • Attach files
  • Guest commented
    16 Jul, 2019 10:28am

    Your suggestion is exactly, what we did, to make DefendPoint updates possible in an enterprise environment.
    Found a nice positive side effect: No reboot is needed anymore, as no software conflicts with DefendPoint update in this state.

    It would really be great to get this neccessary solution from BeyondTrust, instead spending time developing workarounds ourselves...