Scripting Question

K1000 - Force client to update patches outside of scheduled window?

03/01/2016 5219 views
As a school district, we need to be cognizant of when we can have the patching windows open when it comes to Testing Season (state assessment tests).  Ideally, if we had to turn off the schedules, we would still like to pull out shared devices (student laptops) and force the patching.  Is it possible to have a client check-in to the server via a command/script that will check to see if there are any patches available and update if needed?  I was thinking that one of the runkbot switches would facilitate the patching procedure, but it doesn't appear so.  Is there another executable other than runkbot that we can trigger to launch or is it solely on the server that initiates all the patching?
0 Comments   [ + ] Show comments


All Answers

Your patch schedule on the K1000 is the driving force here. How is that set up? Mine are set to a specific day and time. If that window is missed, no patching takes place. In your case, you could make a label that excludes the devices you don't want to patch and set the patch schedule so that it runs every X hours or (and I haven't tested this but it should work) set a schedule with a certain time but check the "Run on next connection if offline" box. 
Answered 03/02/2016 by: rockhead44
Red Belt

  • Currently, it's setup to do it every day between 11 and 3. We previously had the window between 1-3 but we were getting a lot of suspended patches that we increased the window to give it more time. As far as we can tell, right when the window opens, if the client is online, we're not seeing any indication that patching is starting. It could be between 1/2 hour to 2 hours before we get any prompt that Kace would like to patch the client. It doesn't make sense for us to go to a school on a day when school gets out early and lay out 60 laptops and hope that all the laptops receive the patches magically before the window closes or our work shift ends and have to do it all over again the following week. We'd like to force the hand and make it run immediately. The "Run on next connection if offline" will not kick in if the scheduled window isn't open.

    I don't think we have a problem making a separate schedule for just these carts, I just don't think it's going to be that instant patching we're looking for when we have that rare brief time when no students are using the laptops. With 5 techs covering 25 schools and each doing 1 school a week, we need to make sure that all the patching gets done that day.
    • "It could be between 1/2 hour to 2 hours before we get any prompt that Kace would like to patch the client."
      What if you force a check-in as soon as the clients connect? Do you have a lot (100+) of custom inventory rules? Or like 500+ device smart labels?
  • Check out my question regarding the delay on patching, it may help: http://www.itninja.com/question/getting-the-k1000-to-patch-immediately-during-patch-schedule#answer-98877
    • Thank you! I'll see if making those modifications help improve the responsiveness of patching.
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ