Hi,

 

I have noticed that approximately 50 systems have rebooted more than twice after April 2013 patches were deployed by KACE 1000.  I have checked the patch logs and did not find anything abnormal.  Is this a normal behavoir?

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

2

It depends on the patches being deployed and whether or not a reboot is required for them.  My understanding is that Kace is trying to move towards a patching module more similar to how a WSUS would work in terms of the number of reboots required. The typical way that a schedule works in the K1 is that it will deploy until the first reboot is required instead of how a WSUS would work where it "stacks" the patches together to do one reboot that several patches need.  A detect and deploy could easily cause several reboots but you do have the option in the schedule to change the reboot behavior to prompt the user, force reboot or no reboot. 

Answered 05/02/2013 by: Timi
Seventh Degree Black Belt

Please log in to comment

Answers

0

I believe a lot of times if a patch fails it will try again and ask to reboot after the next attempt.  You can change how many times it attempts to install in the detect and deploy.

Answered 05/06/2013 by: WGM_Jeff
Fourth Degree Black Belt

Please log in to comment
0

Also if your patch job is both a Detect *and* Deploy it will keep rebooting the system until all patches are completely installed. A standalone Deploy job should not cause the system to reboot.

Answered 05/06/2013 by: mpace
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity

Share