Receiving alerts after Reboot or Patch Reboot Maintenance Window

Last Modified

Mon Mar 09 15:53 GMT 2020

Description

  • When some servers reboot for a maintenance window, they will report service errors on startup.

Environment

  • N-able N-central all versions

Solution

  • When a Reboot Window is triggered, it is cleared once the reboot is successful. The window duration is to allow the device to successfully INITIATE the reboot. The device will NOT remain in downtime for the duration set upon the reboot window, but rather only until the agent itself is able to check back in. Therefore, you may receive alerts shortly after the reboot occurs, if the device did not reboot quickly enough.
  • The Windows Agent maintenance service by default is set to a delayed startup. This service is responsible for starting the Windows Agent service, and this can help hold off the agent starting back up and checking back in until more of the device's services are back up and running
  • However, on some servers like Exchange, even the delayed startup can happen before all the services have completed starting up and can result in failure notifications.
  1. An alternative is to apply a Scheduled Downtime Window for the duration of the Notification Blackout time that you wish.

    Click All Devices > devicename > Settings > Maintenance Windows > Add > Downtime.

    For more information on adding a device level downtime window, see: https://documentation.n-able.com/N-central/documentation/Content/Devices/Devices_Downtime_Maint_window.htm
  2. Consider raising a Feature Request to: https://me.n-able.com/s/ideas