Guest User!

You are not Sophos Staff.

Thread Info
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 10 subscribers
  • Views 2507 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

servers not alerting when need reboot

April Beachy

We are getting alerts and also getting alerts when endpoints need rebooted.  

 

What we are not getting are alerts when servers need rebooted. I can not find where this might be turned off.  See below.  All of these are regular computers, none of the servers that need rebooted are on this list 

 

 

Actually I lie, some update happened yesterday requiring a reboot for not only our servers, but also our desktops and Sophos Central is no longer showing that alert for anyone. any idea where this may be turned off?

 



This thread was automatically locked due to age.
  • 0

    Hello  

    Alerts requiring a reboot after an update are shown 14 days after an event is received for 'reboot recommended after software update' + no event saying the system rebooted. (Alerts FAQ)

    Alerts that may have been listed are removed when these are acknowledged. You should still be able to see these events in Logs and Reports > Events > check Product Updates - Reboot recommended/Reboot required.

    If you think that some email alerts may be disabled, go to Global Settings > Configure email alerts for your settings.

  • 0 in reply to DianneY

    So you are saying that the alerts will not show until 14 days after they first say they need a reboot?

     

    Alerts are configured to show.

     

    The problem is I've got servers and that have been prompting for a reboot since Feb 11, but that is not appearing anywhere in the alerts that the servers need rebooted.

  • 0 in reply to April Beachy

    Hello  

    Yes, the first event will be "Reboot recommended after software update" is not yet an alert. This will kick off a timer, so to speak, that if there is no restart event after 14 days, then a Reboot Required alert is sent.

  • 0 in reply to DianneY

    The problem is I've got servers and that have been prompting for a reboot since Feb 11, but that is not appearing anywhere in the alerts that the servers need rebooted. they still say:

    Reboot to complete update; computer stays protected in the meantime

  • 0 in reply to April Beachy

    Hi  

    Would you please check whether the server has been rebooted anytime since 11th February?

    Regards,

    Jasmin
    Community Support Engineer | Sophos Support
    Sophos Support Videos | Knowledge Base  |  @SophosSupport | Sign up for SMS Alerts |
    If a post solves your question use the 'This helped me' link

  • 0 in reply to Jasmin

    I can verify that the server has not been rebooted for 27 days, does not appear in the alerts and Sophos states it needs rebooted.

     

     

  • 0 in reply to April Beachy

    Hello  

    Does the Events list in that Device's page in Sophos Central Reboot required? 

  • 0 in reply to DianneY

    It says: Reboot to complete update; computer stays protected in the meantime

     

    The other servers have the same symptoms that have not been rebooted.

  • +2 in reply to April Beachy

    Hello  

    Discussed this a bit with the folks here, and it was said that there are certain update events that will not trigger a "reboot required" event after 2 weeks.

    If there was a major update to Sophos Endpoint (SAV, Intercept X, etc) then these are the types of events that will eventually require a restart. 

    Occasionally an update to the Central Server Protection agent will require a reboot to upgrade a component to the latest version. This reboot will never be forced by Sophos, there is no impact to protection during the period before the reboot is completed. This also does not impact the ability for new threat detection updates to be applied to the Server. New installations will also request a reboot but likewise there is no impact to protection during the period before the reboot is completed.

    It is recommended scheduling a reboot during your next maintenance Window to ensure that you are running the latest version of all components.

Unfiltered HTML