Error trap runner service

I am trying to deploy BIOS upgrades through PDQ. Every one of them 'fails' with a message 'Runner service died unexpectedly'. This is actually a success since the BIOS update forces a reboot. How do I error trap this behavior so it shows as a success?



Date Votes
  • You may be better served by creating a dynamic collection to contain the computers with an old version of the BIOS and use that collection to determine which machines still need the update.

  • I appreciate that suggestion, and I will be doing that to determine which computers to apply the update to, however applying the update would still result in an 'error' in the logs. I assume you are suggesting to just let the sever think it was an error as collection membership will drop the successful ones?


Please sign in to leave a comment.

Didn't find what you were looking for?

New post