We have our weekly Windows patch detect and deploy set for Friday afternoon, but people are consistently prompted to reboot, sometimes multiple times a day, even on the following Monday or Tuesday.  Patch compliance over approx 130 nodes is at 96%, yet we see this every week, and people are starting become aggravated.

 

Also, we're trying to push out the UltraVNC client that KACE uses, but it has caused a slew of random and immediate reboots.  We thought we found a switch in the script to prevent automatic reboots, but it's still happening, and I believe it's happening to peopl who already have it installed.

 

We're kind of overwhelmed and could use a hand.

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

1

for uvnc look at http://www.itninja.com/blog/view/kace-scripting-uvnc-version-1-0-9-6-2-and-newer

Answered 12/18/2012 by: SMal.tmcc
Red Belt

Please log in to comment
1

A few suggestions for your patch schedule issues.

I'm assuming, from what I've read, that your patch schedules use the "Detect and Deploy" method.

If you only want a single reboot, you can separate the detect and deploy cycles.  This will detect the patches needed, then, in a separate schedule, deploy them.  It will deploy until it needs a reboot, then prompt for a reboot. It will not, however, continue detecting and deploying.  The downside to this is that it will take a greater number of patch schedules to bring out of date machines up to date.

When "Detect and Deploy" is selected, KACE will patch up until it the patch it deploys requires a reboot.  Then, it reboots and starts again.  If you have "Max Deploy Attempts" set to 3, the default, I believe, and the patch fails, it will reboot the machine 3 times for that single patch. Then, it will move onto the next patch, which may require 2 reboots to install if the initial install fails.  It's rare, but this can happen. 

Second, if you select "Suspend pending tasks after X minutes from scheduled start" and give it a value, then patching tasks should quit after that time period.  My patch schedules, which run in the evening, have tasks suspended after 300 minutes from the start time.  That helps to ensure that there's no interruption the next day during working hours. 

Answered 12/18/2012 by: tshupp
Second Degree Black Belt

Please log in to comment
0

cholton,

tshupp makes some very good points.  A few questions:  What K1000 Server and Agent versions are you running?  Have you had your JumpStart Training?  Have you received any Training, specifically, on Patching?  Have you watched any of our KKEs on Patching?  r2

 

Ron Colson

KACE Koach

Answered 12/22/2012 by: ronco
Second Degree Brown Belt

Please log in to comment
0

o   KACE Kontinuing Education (KKE)

·         Attend an upcoming session, go to the Training Center at http://kace.com/kke to see the schedule and register for a session

·         Watch a previous session, http://www.kace.com/support/resources/kb/article/KACE-Kontinuing-Education-K1000-and-K2000-Recordings

Answered 12/22/2012 by: ronco
Second Degree Brown Belt

Please log in to comment
0

Submitting to KACE support.  Will post results.

Answered 12/18/2012 by: cholton
Orange Belt

Please log in to comment
Answer this question or Comment on this question for clarity
Admin Script Editor
Admin Script Editor is an integrated scripting environment available free here at ITNinja
Nine Simple (but Critical) Tips for Effective Patch Management
This paper reviews nine simple tips that can make patch management simpler, more effective and less expensive.

Share