Target History contains unsuccessful entries


I do a have schedule for a software update that triggers on heartbeat and every 4 hours (because users can defer the installation). I just realized that there are still much more old installations of that software than targets being tried by the schedule, so I had a look at the Target History and saw a lot of entries that were not successful. The schedule is configured so that unsuccessful targets should not be put on that list, so how did that happen?



1 comment
Date Votes
  • You probably want to uncheck the Stop deploying to target once they succeed.  Even if you have a new version of the software, the schedule won't apply to those machines because they were successful ONCE...even if it was 9 months ago.


Please sign in to leave a comment.

Didn't find what you were looking for?

New post