locked
SCCM 2012 - Reboot after Udpdate Installation RRS feed

  • Question

  • Hello all

    i have an Problem with autimatic update our Windows Servers via SCCM 2012
    After Installing updates the Servers wont reboot automatically during maintanance window.

    i have Setup this in the autmatic deployment rule and also in the Client Settings, but after installing an few updates i willonly get an message from sccm Agent to reboot System.

    Does anyone have an idea what could be the problem

    Thanks
    Thorsten

    Tuesday, July 30, 2013 3:23 PM

All replies

  • Within the ADR and the update deployment that it subsequently creates, there are two check-boxes to suppress reboots on servers and workstations. Have you verified that these are *not* checked.

    Jason | http://blog.configmgrftw.com

    Tuesday, July 30, 2013 4:26 PM
  • Hi Jason
    i have checked theseare bot unchecked.

    is it possible the Problem of the Business hour Setting since updates will also be installed longer then maintenance Slot is Setup?

    Thanks

    Regards
    Thorsten

    Tuesday, July 30, 2013 5:47 PM
  • No, the update process always accounts for a reboot at the end and will always allow enough time to reboot the system within the MW.

    Note that many updates in Windows 7 and newer do not actually require a reboot.

    Have you checked WindowsUpdate.log and rebootcoordinator.log on the client systems?


    Jason | http://blog.configmgrftw.com

    Tuesday, July 30, 2013 5:50 PM
  • SO Server Shows message for reboot first over Windows update Feature and after that over sccm Agent but didnt do this and still installing updates outside maintenance window.
    Tuesday, July 30, 2013 6:13 PM
  • Sounds like you have other things going on that we need a lot more detail about.

    Although first, I would recommend disabling the Windows Update Agent via Group Policy.

    How did your configure your MWs? Are you sure they are applicable to the systems you are "testing" on?

    There is another check-box in the ADR and resulting deployment to ignore MW -- have verified that is not checked?

    Have you checked the logs I asked about?

    How about MaintenanceCoordinator.log?

    This blog post should help: http://blogs.technet.com/b/csloyan/archive/2010/10/24/maintenance-window-calculations-explained.aspx


    Jason | http://blog.configmgrftw.com

    Tuesday, July 30, 2013 6:21 PM
  • I will check the logs tomorrow since i am at home now.

    Is it really necessary to disable Windows update Agent? What Service will install updates instead? Only SCCM Agent?

    Tomorrow i will post screenshot from MW Setup and hope it helps!

    Regards
    Thorsten

    Tuesday, July 30, 2013 6:31 PM
  • Good morning,
    I have found some new Details:)

    I think the maintenance window is working but now i have the Problem that updates will be installed putside them:
    Teh Systems begin to install update at 08:30 but didnt stop at the end time and also makes the reboot.

    Did this Information help?

    Wednesday, July 31, 2013 6:53 AM
  • Please answer Jason's questions then:

    How did your configure your MWs? Are you sure they are applicable to the systems you are "testing" on?

    There is another check-box in the ADR and resulting deployment to ignore MW -- have verified that is not checked?

    Have you checked the logs I asked about?

    How about MaintenanceCoordinator.log?



    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, July 31, 2013 7:23 AM
  • Hi
    the Settings for MW are the following
    i have created an query against an active Directory Group where the Server is member of.
    on this query i have an device collection and Setup maintenance windows

    This will for test run every day from10-12

    The Server begin at 10 install updates but wont stop on 12

    The ADR Settings i have checked

    What informations did you Need from logfiles?

    Wednesday, July 31, 2013 8:19 AM
  • Hi
    the Settings for MW are the following
    i have created an query against an active Directory Group where the Server is member of.
    on this query i have an device collection and Setup maintenance windows

    This will for test run every day from10-12

    The Server begin at 10 install updates but wont stop on 12

    The ADR Settings i have checked

    What informations did you Need from logfiles?


    Wednesday, July 31, 2013 8:25 AM
  • Hi
    So update to my Situation. MW is working now and Installation will stopped after endtim eis reached.
    One additional question that i have.

    Now my Server delivers an message about System restart that is needed but MW is ended.

    Why shouldnt this been done during MW?
    IS it possible that there are too many updates to be installed?

    Will restart be done before beginning next Windows uopdate Installation?

    Wednesday, July 31, 2013 12:58 PM
  • Yes, disabling the Windows Update Agent is a good thing to do -- no that does not mean disabling the service. For more info, check out

    http://blog.configmgrftw.com/?p=88

    and

    http://blog.configmgrftw.com/?p=89


    Jason | http://blog.configmgrftw.com

    Wednesday, July 31, 2013 1:12 PM
  • It is possible that the MW is too short for all updates to be installed. The restart behavior is defined in the Deployment ('User Experience' tab).

    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, July 31, 2013 1:17 PM
  • OK so what happend if MW is too short for all updates? What happens with restart for example?
    Will this then be done on next MW?

    Wednesday, July 31, 2013 1:42 PM
  • The blog I posted above covers this. Basically, it always accounts for the reboot first at the end of the MW.

    Jason | http://blog.configmgrftw.com

    Wednesday, July 31, 2013 2:23 PM
  • Thanks Jason

    which one did you mean:)
    This is the last open Point i have why reboot at end of MW didnt run

    Wednesday, July 31, 2013 2:27 PM
  • Sorry, this one: http://blogs.technet.com/b/csloyan/archive/2010/10/24/maintenance-window-calculations-explained.aspx

    Jason | http://blog.configmgrftw.com

    Wednesday, July 31, 2013 2:39 PM
  • Thx

    i have Setup Settings in Agent but no restart
    Any other additional Setting?



    I have the following message in rebootcoodinator.log
    Including grace period 5400 seconds, the system restart turnaround time is 6000 seconds
    Wednesday, July 31, 2013 2:44 PM