I am correcting an existing half-automated patch solution in our Kace K1000 environment, just a question regarding multiple applicable patches for the same application, e.g. this print screen:

Will it get stuck in a loop attempting to install 121 > 131 > 121 > 131, or is the kbot clever enough to see that Update 131 is the newest available for Java 8 (in this label) and will completely skip any older patches?

The reason why I ask is; our current configuration inactivates superseded patches automatically and we want to remove this feature so tested patches can keep installing even if they are flagged as superseded.
In our scenario Update 141 was recently released and sent to User Acceptance Test for 20 days, this also inactivated Update 131 so no computers are installing update 131 anymore.

Long story short:
Is it safe to deploy multiple active patches for the same application?

Thanks alot,
Erik S

0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity


KACE should have enough common sense to only deploy the latest update on the client. But I would make sure you are on a 7.2 agent for the most reliable performance
Answered 08/03/2017 by: Hobbsy
Red Belt

Please log in to comment
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.