Has anyone seen a case where all patching tasks go through the stages of detecting>downloading and then mostly all end up at error?

Generally 90% + of all our patching tasks fail, we have spoken to support and updated to latest but at the moment our security team are not happy and we are getting close to getting rid of the appliance all together and finding a system that can support patching. Group I am looking at is 80 laptops. only patching adobe/chrome/firefox and apple. we handle windows patches with a WSUS as its more succesful than the kbox.
1 Comment   [ - ] Hide Comment


  • I have all my tasks set to 120 minute End After, because like it would take 2 hours to patch adobe... Have increased this to 180/3 hours to see if this is just an inefficiency problem with the speed kbox moves at
Please log in to comment

Answer this question or Comment on this question for clarity


What sort of errors are you seeing?  There is usually an error number associated with it.
Answered 02/03/2015 by: jknox
Red Belt

  • It just says 'error' when looking at the patch schedule. If i drill down into a system (using mine as a good test) and that just shows error as well? Where would I get the error number?
Please log in to comment
Hmm, thats a high error rate. I haven't experienced anything like that. Are you still working with support on the issue?

Are the laptops staying on and connected to the network for the duration of the patch cycle?
Answered 02/03/2015 by: getElementById
Third Degree Blue Belt

  • Yes still working with support. Yup, 80 machines I would expect an error rate of 5-10% to allow for users dropping off or disconnecting. But this runs at lunch time so shouldn't be this high
Please log in to comment
Do your patches require reboots? For reasons unfathomable, if the target machine reboots in order to complete a patch the patching process does not resume after it boots back up.
Answered 03/11/2016 by: csctim
White 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.