Does anybody use the new 5.4 patching detection function
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.
-
How are you handling this each month for patching? Running a detect schedule , or is the kace box handling this for you? - dlankford 11 years ago
Answers (3)
lowers the patching space dramatically
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.
Comments:
-
good to know, I thought I made a mistake because it was much quicker than I had expected - Nico_K 11 years ago
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.
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.
