Server Management Suite

 View Only
  • 1.  Patch Management - How do I restart a Windows node after the policy has completed

    Posted Nov 04, 2010 03:25 PM

    Hi All,

    I've Staged, Created the Patch Policy, and assigned it to several Targets and not to override the Maintenance Window.

    After the patches have been applied I want the node to reboot. I'm not sure how I would schedule a job or task to do this after the policy or policies have been applied. 

     

    Adrian



  • 2.  RE: Patch Management - How do I restart a Windows node after the policy has completed

    Posted Nov 04, 2010 03:42 PM

    1. Go to - Settings->Agents/Plug-ins->Software->Patch Management->Windows->Default Software Update Plug-in Policy

    And set there Reboot options you would like to use: "On schedule" or "At the end of software update cycle".

    2. Refresh configuration on the client/clients.

     

    All the future updates which require reboot (after successful installation) will trigger the reboot of the client according to the settings you've selected.

     

    Regards,

    Robert



  • 3.  RE: Patch Management - How do I restart a Windows node after the policy has completed

    Posted Nov 04, 2010 06:59 PM

    Hi Robert,

    Thanks a lot for the response and the walk-thru.

    I already have my settings set for 'At end of...', but I have experienced nodes rebooting the following week (thankfully only my Dev/Test/QA environments) when their maintenance window opened.



  • 4.  RE: Patch Management - How do I restart a Windows node after the policy has completed

    Posted Nov 05, 2010 12:27 PM

    1. "Override Maintenance Windows" unchecked  in the SWU policies

    2. Reboot at the end of the update cycle enabled

    3. "Maintenance Window" turned on and configured

     

    Then:

    1. Updates will be installed on the clients when MW is opened (active) there

    2. Reboot should be performed at the end of the update cycle

     

    If you're observing different behavior then we'll need more information: configuration(more details)/logs/etc.

     

    Regards,

    Robert