Since 5.4 you are able to detect all patches (does not mean a full patching cache but having all patch signatures handy)

Does anybody use this functionality? What I need ist the following info: how long does the full detection job run on your environment?

Until 5.3 you needed patching labels. This is not needed anymore but will work in 5.4 too.

Answer Summary:
lowers the patching space dramatically
1 Comment   [ - ] Hide Comment


  • How are you handling this each month for patching? Running a detect schedule , or is the kace box handling this for you?
Please log in to comment

Answer this question or Comment on this question for clarity



We use the new method and it has been great in reducing the size of what we store. Our environment is very small so it only takes about 20 minutes to do the scan. I run the scan every 2 days and download every 4 hours. 

Answered 04/01/2013 by: nshah
Red Belt

  • good to know, I thought I made a mistake because it was much quicker than I had expected
Please log in to comment

I'll echo the comment above. We have drastically reduced our patch size with the new caching capabilities. Prior to we were consistently having issues with available drive space.

Answered 04/01/2013 by: jegolf
Red Belt

Please log in to comment

Occasionally we still run a detect all against every signature, but I've found that this can be problematic at our remote sites. For some reason it will slow everything down dramatically at a couple of them. We've been troubleshooting this for a while, but for now we've agreed that it's best not to run during business hours.

Answered 04/01/2013 by: GeekSoldier
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.