6 Replies Latest reply on Aug 13, 2013 12:54 PM by Lawrence Garvin

    Server rebooted even when no restart option was selected in Solarwind patch manager task

    kmalik

      Hi , we recently had a problem where

      During patch install via Solarwindpatch manager with 'No pre-reboot/Post-reboot" option selected ,we found one server got rebooted automatically. On checking we found the restart source "MSiInstaller". Description: "Windows installer initiated a system restart to complete or continue the configuration of  "MSXML 6 Service Pack 2 (KB2758696) ".

      Please can you let us know why this behaviour? Due to this we cannot even patch install the servers and schedule restarts later.

        • Re: Server rebooted even when no restart option was selected in Solarwind patch manager task
          Lawrence Garvin

          The best approach here is to review the WindowsUpdate.log from that server so that we can determine exactly what was the scenario and context of this update installation and subsequent restart.

           

          If you can copy the entries for the day of the installation/reboot into a separate text file and upload here, I'd be happy to review the logfile.

           

          Also, if you could clarify your statement.... did you have both NO Pre-Reboot and NO Post-Reboot selected in the Update Management task? Was this the only computer targeted by this task, or were other computers also targeted by this task. If others were included, what was their behavior?

          • Re: Server rebooted even when no restart option was selected in Solarwind patch manager task
            antwesor

            kmalik wrote:

             

            Hi , we recently had a problem where

            During patch install via Solarwindpatch manager with 'No pre-reboot/Post-reboot" option selected ,we found one server got rebooted automatically. On checking we found the restart source "MSiInstaller". Description: "Windows installer initiated a system restart to complete or continue the configuration of  "MSXML 6 Service Pack 2 (KB2758696) ".

            Please can you let us know why this behaviour? Due to this we cannot even patch install the servers and schedule restarts later.

            I would be guessing, but it sounds like you have deadlines approved. Deadlines would override the 'No pre-boot/Post-reboot' option in Solarwinds Patch Manager.

              • Re: Server rebooted even when no restart option was selected in Solarwind patch manager task
                Lawrence Garvin

                While I'm inclined to agree that deadlines might be involved, the more practical case is that using Patch Manager's Update Management task would not invoke those deadlines. The only plausible scenario in which that could occur is if the approval-and-deadline had been created within the time frame of the client's last successful detection (such that the client did not yet know about the update approval or deadline) and the deadline had expired by the time the installation task was launched.

                 

                The Update Management task would have forced the WUAgent to execute a detection (to validate the requested update deployment) at which time it would have discovered the update with the approval and now-expired deadline, launch a download, install the update, and reboot.

                 

                Of course, whatever the case is, the WindowsUpdate.log will tell us exactly what did happen. :-)

                  • Re: Server rebooted even when no restart option was selected in Solarwind patch manager task
                    antwesor

                    LGarvin wrote:

                     

                    Of course, whatever the case is, the WindowsUpdate.log will tell us exactly what did happen. :-)

                    True, the best course of action is to wait for the WindowsUpdate.log results to see exactly what did happen to that server.

                    • Re: Server rebooted even when no restart option was selected in Solarwind patch manager task
                      kmalik

                      Thanks Garwin,

                       

                      PFA the windows logs of the day the issue occurred.

                      Yes there were other servers too that were being patched but this issue

                      affected this server.

                      No Pre-Reboot or Post-Reboot option was selected.

                       

                       

                       

                      The windows event logs registered the event as shown in the attached doc

                      file.

                       

                       

                       

                      Thanks & Regards,

                       

                      Kuntal Malik

                       

                      Platform Services - Infrastructure Team

                      CPA Global

                       

                      Direct Dial: +91 120 406 7383

                      Email: Kmalik@cpaglobal.com

                      India

                      Office Hours:09:00-18:00 IST

                       

                       

                       

                       

                      From:

                      LGarvin <solarwindscommunityteam@communications.solarwinds.com>

                      To:

                      kmalik malik <kmalik@cpaglobal.com>,

                      Date:

                      08/10/2013 12:23 AM

                      Subject:

                      Re: - Server rebooted even when no restart option was

                      selected in Solarwind patch manager task

                       

                       

                       

                       

                      thwack

                      Server rebooted even when no restart option was selected in Solarwind

                      patch manager task

                      created by LGarvin in Patch Manager - View the full discussion

                      While I'm inclined to agree that deadlines might be involved, the more

                      practical case is that using Patch Manager's Update Management task would

                      not invoke those deadlines. The only plausible scenario in which that

                      could occur is if the approval-and-deadline had been created within the

                      time frame of the client's last successful detection (such that the client

                      did not yet know about the update approval or deadline) and the deadline

                      had expired by the time the installation task was launched.

                       

                      The Update Management task would have forced the WUAgent to execute a

                      detection (to validate the requested update deployment) at which time it

                      would have discovered the update with the approval and now-expired

                      deadline, launch a download, install the update, and reboot.

                       

                      Of course, whatever the case is, the WindowsUpdate.log will tell us

                      exactly what did happen.

                      Reply to this message by replying to this email -or- go to the message on

                      thwack

                      Start a new discussion in Patch Manager by email or at thwack

                       

                       

                       

                      ********************************************************************************

                      The information in this message is confidential and may be legally

                      privileged. It is intended solely for the addressee; access to this

                      email by anyone else is unauthorised.

                       

                      If you are not the intended recipient: (1) you are kindly requested

                      to return a copy of this message to the sender indicating that you

                      have received it in error, and to destroy the received copy; and (2)

                      any disclosure or distribution of this message, as well as any action

                      taken or omitted to be taken in reliance on its content, is prohibited

                      and may be unlawful.

                       

                        • Re: Server rebooted even when no restart option was selected in Solarwind patch manager task
                          Lawrence Garvin

                          A couple of observations, but no real conclusions that can be drawn.

                           

                          The DOCX file attached, with EventLog images, is from machine JSY-WFEVP02. It shows an installation of MSXML6 at 7:22am that required a system restart.

                          Nothing else can be determined about this machine, including whether it was actually restarted, or not.

                           

                          The WindowsUpdate.log attached is from machine JSY-WFEVP01. It shows installation of 24 .NET4 Security Updates from 6:30am to 8:19am, then placing the machine in a Pending Reboot state.

                          That Pending Reboot state was then deferred by the logged on user at 9:53am, 10:38am, 11:44am, 12:46pm, 1:34pm ... and that's where the logfile dies.

                           

                          There's no evidence in the provided information that Patch Manager had anything to do with the installation of the MSXML6 update, nor how that machine (JSY-WFEVP02) was actually restarted.

                          The WindowsUpdate.log is for a different machine.

                          1 of 1 people found this helpful