Hopefully that subject line will get some attention. So here is my situation and then my question. I have patching set up to be pushed to the production machines once a week. The user is prompted for a reboot (if necessary) three times. That gives them the opportunity to clean up and save anything that they might be doing. After the third prompt is ignored then it's an automatic reboot. That's company policy and we can't get around that. Machines can't go X number of days without being patched. Now, I have a group of engineers that are in to some serious number crunching. They have programs with millions of lines of code and some of their stuff takes three and four days to run to a solution. One of their jobs was killed by a mandatory reboot.

Is KACE smart enough to detect a flag or an IF statement that says if unnamed process is running, then postpone due patches X amount of time? Can a smart label be set up within patching to do that? Does anyone have an example of a label or script that does something similar to that?

Thanks for the help.

0 Comments   [ + ] Show comments


Please log in to comment



I think your best way to handle this on your engineering machines is to have them on a patch schedule that has automatic reboot suppressed (manual or smart label assignment is your choice). Then for the same label have a K script that looks for the running process before rebooting the machine. I had a smart label configured to look within another smart label for machines with an uptime greater than 1 day. Machines matching that criteria that did not have a logged in user would reboot by K script to finish patching. This is how I prevented machines from going greater than 1 day without a post-patching reboot that wouldn't disrupt anyone's work. I hope this helps. Below is a link to the thread on how the smart-label was set. I hope this helps.


To directly answer your question, I do not think that you can create a smart label that looks for a running process or service, but a script can.

Answered 07/07/2015 by: GeekSoldier
Red Belt

Please log in to comment