none
"No auto-restart for scheduled Automatic Update installation" missing in GPO settings

    Question

  • Many persons are talking about a Windows Update setting named "No auto-restart for scheduled Automatic Update installation".

    However, we have only "No auto-restart with logged on users for scheduled automatic updates installations".

    I guess this functionality has been removed in Windows 2008...

    Other people have asked the same question than me on this Technet forum.
    But their question has been redirected to an article which does NOT give the answer,
    and the question has been locked...

    Does anybody know why this setting is missing
    and if it is possible to bring it back?

    Friday, April 29, 2016 3:45 PM

Answers

  • Finally found a way to achieve this:

    1. Create a GPO to deploy a scheduled task:
      Computer Configuration\Preferences\Control Panel Settings\Scheduled Tasks
    2. The scheduled task launches the following Powershell command:
      Program/Script: C:\Windows\system32\WindowsPowerShell\v1.0\powershell.exe
      Arguments:
      –Noninteractive –Noprofile -Command &{Import-Module -Name PSWindowsUpdate;Get-WUInstall -UpdateType Software -IgnoreReboot -AcceptAll -Verbose|Out-File -Force -FilePath C:\Temp\WindowsUpdate.log}

    This works fine for me.
    All servers have installed updates and are in a pending reboot state.

    The PSWindowsUpdate module can be downloaded here:
    http://www.powershellgallery.com/packages/PSWindowsUpdate

    Tuesday, July 05, 2016 7:54 AM

All replies

  • Does anybody know why this setting is missing
    and if it is possible to bring it back?

    I don't exactly *know*, of course, but I *think* that MSFT don't want systems running with updates installed and reboot pending for weeks on end. This breaks all sorts of things, btw - many operations query the restart pending state and refuse to proceed if there indeed is a restart pending.

    If you want it back, you can start a thread on UserVoice (or search and upvote if there already is one).


    Evgenij Smirnov

    msg services ag, Berlin -> http://www.msg-services.de

    Windows Server User Group, Berlin -> http://www.winsvr-berlin.de

    Mark Minasi Technical Forum, reloaded -> http://newforum.minasi.com

    Friday, April 29, 2016 4:47 PM
  • Hi Luc,

    Do you want it back?

    The policy No auto-restart with logged on users for scheduled automatic updates installations is the same withNo auto-restart for scheduled Automatic Update installation.

    The only difference isAutomatic Updates notifies the logged-on user that the computer will automatically restart in five minutes to complete the installation. A local administrator can change this setting by using local policy when No auto-restart with logged on users for scheduled automatic updates installations set to not configure. And instead of Automatic Updates will notify the user that the computer will automatically restart in 5 minutes to complete the installation whenNo auto-restart for scheduled Automatic Update installation is set to not configure.

    For more information, you could compare the two articles below.

    Configure Automatic Updates by Using Group Policy

    https://technet.microsoft.com/en-us/library/cc720539(v=ws.10).aspx

    Configure Automatic Updates using Group Policy

    https://technet.microsoft.com/en-us/library/dd939933(v=ws.10).aspx

    Best Regards,

    Jay


    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, May 02, 2016 1:02 PM
    Moderator
  • Hi Luc,

    Are there any updates?

    Best Regards,

    Jay


    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, May 06, 2016 2:43 AM
    Moderator
  • Hi Jay,

    If I understand well, the No auto-restart with logged on users for scheduled automatic updates installations setting means that if there is no logged on user, then the server will restart anyway.

    This behavior is good for workstations with interactive users.

    But in case of servers, we are talking about service unavailability.
    The fact that nobody is currently logged on the server does not mean there are no connected clients.

    The automatic restart happens somewhat randomly because it is entirely depending of the duration of the updates installation. And currently you can only delay this automatic restart, and only if somebody is interactively logged on.
    We want to keep total control on the restart time, because we want it to happen at a time with no or minimal impact for customers.

    Friday, May 06, 2016 9:03 AM
  • Hey hi..

    To manage critical server reboots, Your best option is to use download and notify and then use a script initiate installs/reboots based on the needs. I follow this method for more than 2K servers.

    Auto Download the update and don’t install them.

    If you have SCCM - You can suppress the reboots for servers.


    Devaraj G | Technical solution architect

    Friday, May 06, 2016 12:14 PM
  • Hi Devaraj,

    I was thinking the same and planing to:

    • deploy a daily scheduled task via GPO
    • which uses the PSWindowsUpdate module with the Get-WUInstall cmdlet associated to the -IgnoreReboot parameter

    How are you achieving this on your side?

    Thursday, May 12, 2016 12:56 PM
  • Finally found a way to achieve this:

    1. Create a GPO to deploy a scheduled task:
      Computer Configuration\Preferences\Control Panel Settings\Scheduled Tasks
    2. The scheduled task launches the following Powershell command:
      Program/Script: C:\Windows\system32\WindowsPowerShell\v1.0\powershell.exe
      Arguments:
      –Noninteractive –Noprofile -Command &{Import-Module -Name PSWindowsUpdate;Get-WUInstall -UpdateType Software -IgnoreReboot -AcceptAll -Verbose|Out-File -Force -FilePath C:\Temp\WindowsUpdate.log}

    This works fine for me.
    All servers have installed updates and are in a pending reboot state.

    The PSWindowsUpdate module can be downloaded here:
    http://www.powershellgallery.com/packages/PSWindowsUpdate

    Tuesday, July 05, 2016 7:54 AM