Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Marking deployments as successful in the target history

Hello everyone!

Here's the problem: in the package schedules we set up targets via AD groups and this works great, but sometimes we need to mark a machine in the target history as finished because we know that the software is already present on that machine.

I found the following blog article: It describes that the target history is stored in the ScheduleComputers table. As I was looking at this table, it occurred to me that it might be possible to change the value in the SuccessCount column to 1, which could perhaps mark a deployment on this computer as successful without actually installing anything.

So, what I'm thinking is that I would run a command through the SQLite console that would look something like this:

update ScheduleComputers set SuccessCount = 1 where ScheduleId = 90 and PackageId = 50 and Name = '';

I'm looking for insights on whether this approach is viable or if it might cause issues with the database. Any advice or shared experiences would be greatly appreciated!

Thank you!



1 comment
Date Votes
  • Possibly an unhelpful reply as I can't answer regarding the SQL command. But I'm curious why you'd deploy a package to a group that wouldn't need the software?

    My approach as a non-database administrator, would be to make a child dynamic group that filters from the parent group and then adds a filter that looks at computers that do not have the software installed. Then target this dynamic collection for your schedule.

    With the database approach, it sounds like you'd need to know which computers did or did not have the software to only modify the value for computers that had the software. Since PDQ checks for software that's installed, I think it can take care of that for you.

    Otherwise, it would make sense that you create an entry in the DB for the computer that says the schedule was already successful and that would prevent future attempts.