We have over 5,000 machines in our K-12 district, and most can't wake on lan due to prior settings. We have patching every Wednesday at 4:30AM for any that can WOL, and then the others set to deploy upon next check-in. However, kids/teachers are hitting cancel, or browsing websites and java won't update because browsers are open. 

Is there any way to automate patching upon shutdown of machines at certain days/times? So for instance, upon shutdown every Wednesday after a certain time, or even to run a certain script upon shutdown? That way, I could push out a script that would run upon shutdown. Is this even possible?

People are just getting mad since they power on machines at 8am ready to use them for class, and it's annoying people and they aren't allowing it to patch. Even if they do patch, it uninstalls/intalls latest update, and takes time. Other than cooperation of staff (which won't happen...tech is a losing battle in our district), patching is proven to be quite hard, especially with laptops that are being powered on at random times throughout the day/week.

Any input or thoughts is appreciated!

Answer Summary:
0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity



I dont see a way that would currently be possible in the K1000.  In 5.4 you can limit the number of times they can snooze before the patch job is forced though.  You could also just force the installation of the patches but allow a snooze on the reboot.  Then the patches would be fully applied on the reboot.

This may also be something you want to bring up on the uservoice as a feature request:  http://kace.uservoice.com/forums/82699-k1000

Answered 01/18/2013 by: WhitzEnd
Seventh Degree Black Belt

  • This is currently a feature request on user voice. Apply your votes! http://kace.uservoice.com/forums/82699-k1000/suggestions/2558401-additional-end-user-options-for-patch-installs
  • This would be awesome, too bad I already burned up my uservoice points...
  • Voted. Thanks!
Please log in to comment