locked
Deadlines don't seem to be working... RRS feed

  • Question

  • Howdy,

    I'm trying to setup our WSUS to run automatically to patch and reboot our test servers.  I approved the patches yesterday and set a Deadline on them of 11AM and 12PM today for my two WSUS groups.  However, it's now after that time and the machines have either not installed patches at all, or have installed but not rebooted.  Can anyone help me figure out why this isn't work?

    I checked one test server and verified it show sup in my first group in WSUS.  I checked Windows Update and it shows the available patches but they have not installed.  I verified the patch shows as approved for Install and with a deadline of 11/15/2018 at 11AM.

    I don't understand why they didn't install like they were supposed to.  Any guidance would be great.

    Here's the windows update log for the 11AM timeframe when the dead is set to take effect.

    2018/11/15 11:00:27.0786754 1128  4776  Agent           WU client version 10.0.14393.2515
    2018/11/15 11:00:27.0788454 1128  4776  Agent           SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
    2018/11/15 11:00:27.0788896 1128  4776  Agent           Base directory: C:\Windows\SoftwareDistribution
    2018/11/15 11:00:27.0792104 1128  4776  Agent           Datastore directory: C:\Windows\SoftwareDistribution\DataStore\DataStore.edb
    2018/11/15 11:00:27.1142889 1128  4776  Shared          UpdateNetworkState Ipv6, cNetworkInterfaces = 0.
    2018/11/15 11:00:27.1143073 1128  4776  Shared          UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
    2018/11/15 11:00:27.1147161 1128  4776  Shared          Network state: Connected
    2018/11/15 11:00:27.1170406 1128  4776  Misc            LoadHistoryEventFromRegistry completed, hr = 8024000C
    2018/11/15 11:00:27.1197377 1128  5380  Agent           Initializing global settings cache
    2018/11/15 11:00:27.1197384 1128  5380  Agent           WSUS server: http://wsusserver:8530
    2018/11/15 11:00:27.1197391 1128  5380  Agent           WSUS status server: http://wsusserver:8530
    2018/11/15 11:00:27.1197397 1128  5380  Agent           Alternate Download Server: NULL
    2018/11/15 11:00:27.1197405 1128  5380  Agent           Fill Empty Content Urls: No
    2018/11/15 11:00:27.1197410 1128  5380  Agent           Target group: SAN-Odd
    2018/11/15 11:00:27.1197416 1128  5380  Agent           Windows Update access disabled: No
    2018/11/15 11:00:27.1201172 1128  5380  Agent               Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2018-11-16 15:02:34, not idle-only, not network-only
    2018/11/15 11:00:27.1240624 1128  5380  Agent           Initializing Windows Update Agent
    2018/11/15 11:00:27.1241232 1128  5380  DownloadManager Download manager restoring 0 downloads
    2018/11/15 11:00:27.1241618 1128  5380  Agent           CPersistentTimeoutScheduler | GetTimer, returned hr = 0x00000000
    2018/11/15 11:00:27.1265437 1128  4776  Shared          UpdateNetworkState Ipv6, cNetworkInterfaces = 0.
    2018/11/15 11:00:27.1265511 1128  4776  Shared          UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
    2018/11/15 11:00:27.1266128 1128  4776  Shared          Power status changed
    2018/11/15 11:00:27.1499908 1128  7744  Shared          Effective power state: AC
    2018/11/15 11:00:27.1499922 1128  7744  DownloadManager Power state change detected. Source now: AC
    2018/11/15 11:11:32.5860975 1128  5108  Agent           Earliest future timer found:
    2018/11/15 11:11:32.5861070 1128  5108  Agent               Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2018-11-16 15:02:34, not idle-only, not network-only
    2018/11/15 11:11:33.5968722 1128  4776  Agent           Earliest future timer found:
    2018/11/15 11:11:33.5968832 1128  4776  Agent               Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2018-11-16 15:02:34, not idle-only, not network-only
    2018/11/15 11:11:33.5992176 1128  4776  Misc            CreateSessionStateChangeTrigger, TYPE:2, Enable:No
    2018/11/15 11:11:33.5992202 1128  4776  Misc            CreateSessionStateChangeTrigger, TYPE:4, Enable:No
    2018/11/15 11:11:33.6013835 1128  4776  Handler         CUHCbsHandler::CancelDownloadRequest called
    2018/11/15 11:11:33.6801357 1128  4776  Shared          * END * Service exit Exit code = 0x240001

    • Edited by Kelemvor33 Thursday, November 15, 2018 7:24 PM
    Thursday, November 15, 2018 7:21 PM

All replies

  • looks like you are doing this on Win10/WS2016 ?

    things are a little different, in the modern OS versions (compared to old OS versions..)

    check this article to understand some of the changes which may be affecting your scenario:

    https://blogs.technet.microsoft.com/wsus/2013/06/10/managing-updates-with-deadlines-in-an-era-of-automatic-maintenance/

    e.g. is there a timezone issue? 
    "In WSUS, when you set a deadline, it is interpreted in the time zone of the WSUS server, not the time of the target computer. "

    or, check the event logs related to USO and other scheduled tasks, look for other relevant events


    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Friday, November 16, 2018 6:03 AM
  • I've read that page multiple times.  And it's from 5 years ago...

    The time is set correctly.  The deadline just didn't cause anything to happen.  I have 2012R2 and 2016 machines.

    This is exactly what I have setup:

    What to do:

    • Using Group Policy, set your target machines to check for updates but do not automatically install them.
    • When you want to deploy an update at a particular time, set the deadline for when you want the machine to install updates and restart.
    • You can use groups in WSUS to set different approvals and different deadlines for different groups of machines.

    Friday, November 16, 2018 2:10 PM