Is there a way to force a patch schedule to continue trying to install a patch that fails? I know you have setting for retry times, but to give you an example, we see the patch download failure error a lot and a lot of times just running the patch schedule again will fix it. However, I don't want to run the patch schedule again for 200 clients when say only a handful of them did not receive the patch.

It seems tedious to set up a whole new patching job just to run for the machines that fail.

Any ideas?
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Only machines that require a retry of the patches in the schedule are going to retry. Any ideas on why the download fails so much? Remote machines? Could a replication share help here?
Answered 03/01/2011 by: GillySpy
Seventh Degree Black Belt

Please log in to comment