2

Setup:

Server - WSUS 3.0 SP2 running on Windows Server 2008 R2 (I use WSUSPackagePublisher as a GUI for the WSUS API for importing/creating non MS updates/catalogs)

Workstations - Windows 7 Pro 64-bit, nothing special going on, just a bunch of domain joined machines

Update policy - Download and notify for install. We don't use deadlines, we're small enough that we can bother users who don't install updates in a timely manner, and most users use the "Install Updates and Shut Down" option when they leave for the day or for the weekend.

Issue: For the most part, when updates are downloaded to machines and ready to install, the "Install Updates and Shut Down" option becomes available to users, even for custom updates. However, I have 3 custom updates that aren't triggering that, or so it would seem, and as they're out of band with other updates that do trigger this option, I've seen relatively low installation for the past 2 weeks (roughly 5% instead of 95% after this time period). For these updates, in WSUSPackagePublisher, I've checked the option "Requires Network Connectivity" (source code out of date, but this bit may not have changed much since the last source code post).

My question is this: when making custom updates, what are things that would prevent the "Install Updates and Shut Down" option for those updates?

EDIT: Alright, it seems that by removing the "Requires network connectivity" flag made the updates available via the "Install Updates and Shut Down" method. This may end up in a few machines on my network failing to install the updates if the computer is taken offline first, I'll just have to deal with that possibility for now. Original question still stands, what defines the criteria for an update being able to be installed using the "Install Updates and Shut Down" method?

2
  • 1
    Do these updates actually require a restart? Aug 1 '14 at 21:17
  • No, but users usually won't go out of their way to install updates through the UI, and they might not install if the users are in the programs that the patch applies to.
    – austinian
    Aug 7 '14 at 15:26
0

In my experience the Install Updates and Shut Down shutdown option is only available when updates are available (and downloaded) and at least one of the pending updates requires a reboot.

Of course we all know that's so commonly the case it's unusual to a have machine with pending updates that wouldn't show the Install Updates and Shut Down option, but it does happen occasionally.

5
  • This is not the case, in my experience thus far, as long as the update is downloaded and ready to install, Install Updates and Shut Down becomes an option. It is only recently that I ran into an issue with updates not following this behavior, specifically if the update is flagged as requiring network connectivity or having the ability to accept user input. I've been looking for documentation on how the windows update agent deems updates as installable via "Install Updates and Shut Down", I just haven't found any yet.
    – austinian
    Aug 9 '14 at 17:34
  • Agreed on updates requiring user input not triggering the install & shut down option. I'm not familiar with the 'requires network connectivity' flag. Where are you seeing that? Aug 9 '14 at 18:52
  • It's a property you can set in an update. Here's the WSUS API documentation on the property: InstallationBehavior.RequiresNetworkConnectivity msdn.microsoft.com/en-us/library/… I'm probably going to be able to roll out a GPO to cache the files offline so that this won't be an issues for future updates.
    – austinian
    Aug 9 '14 at 19:00
  • Is this property exposed in any Microsoft-standard GUI? Or is it accessible only through programming? Aug 9 '14 at 19:07
  • I don't use a Microsoft GUI to add updates, so I have no idea.
    – austinian
    Aug 9 '14 at 19:41

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.