I have a patch schedule which I use for testing updates on a handful of test PCs. In the past, I have been able to force the schedule to run immediately. I do this by either setting the scheduled time to run in the very near future or hitting Run Now, or both. Since the upgrade to 6.4, this has not been working consistently for me at all.

For the patch schedule in question, the Delay Run is set to 0, End After is blank. I am using "run Every day at X:XX".

In the past setting this time to as little as 2 minutes in the future would work. Today I have tried setting it for up to an hour from now (that is, set it to run at 11:00 when hitting the save button at 10:00). Two hours later, the job has not run.

Clicking "show all" shows the correct computers selected for this patch schedule. If I click run now, I can see the status shows scheduled, and the date column shows the current time. If I check this again after the schedule time has passed, it still states scheduled, but the date has changed to the time specified in the schedule. However, the status never changes from scheduled. In the Patch Schedules list, it shows as pending even an hour or more later.

Last night before leaving the office, I set this Patch schedule to run a detect job at 8:00 am. When I came in at 9:00, it had completed. How far in advance do I have to set a schedule in order to get it to run? I really need to be able to run multiple detect jobs rapidly for testing purposes.
4 Comments   [ + ] Show Comments


  • Have you tried forcing an inventory update after scheduling the patch job?
  • I have tried this. If I hit the force inventory button on that PCs inventory page, I can see the inventory updates. (the last inventory time changes, at least.) However, this has no impact on the Patch Schedule running. It does eventually run, but it takes several hours (4 or more) after the scheduled time.
    Moreover, with the job is set to detect and deploy, it deploys a set of patches and sometimes reports several "not patched" patches remaining. Shouldn't it continue to detect and deploy until this gets to 0?
  • Hi, did you finaly get a solution for that?
  • Mostly. We had multiple script schedules (set up by a previous tech) which were running far too frequently and would sometimes cause Kace to be unable to handle additional requests. We reduced the number and frequency of scheduled scripts, and most of the time patch schedules and other tasks are very responsive. Every now and then there is still a little hiccup, but these usually resolve on their own pretty quickly.
Please log in to comment

There are no answers at this time


Answer this question or Comment on this question for clarity