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.

Reboot Aborted

I have a task setup to simply reboot any computer in the Reboot Required collection. The package has the option set to Always run for the logged on state. I have the schedule to set to deselect the option to stop deploying once succeeded. The issue I am having is more that ⅔ of the targets are reporting back with a status of failed and the error aborted. I know for a fact that ⅔ of the computers here did not have a user abort the reboot at 8:00pm on a Friday night. Double clicking on any of the failed workstations doesn't reveal any additional information. Any ideas as to why I am seeing so many failures?

0

Comments

2 comments
Date Votes
  • Same thing is happening to me. And it's not consistent. I deployed a package with a reboot step to 8 servers recently. 7 failed on the reboot step (aborted), however 4 of the servers DID in fact reboot.

    Looks like it's time to eliminate the reboot step, and instead perform the reboot as a script function, because I can't trust the PDQ reboot function.

    0
  • If you haven't already, please update to Deploy 17.2.0.0.

    If that doesn't help, please contact support@pdq.com.

    0