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.

Does PDQ Deploy support continuing with a package deployment after a required reboot

I have a package that requires a reboot between a few of the steps, is this currently supported?

I saw another community post from 2013 that said it wasn't, but that the feature might be implemented (https://support.pdq.com/hc/en-us/community/posts/211672447/comments/216070327).

As that was from 2013, any chance support for it has been added yet?

0

Comments

4 comments
Date Votes
  • Throw in a Reboot Step. It's definitely supported. I can't remember which level that is supported at though. It might be only Enterprise licensed, or Pro licensed. Check the Compare Versions chart, it might be listed on their website.  But yes, you definitely can.

    1
  • The Reboot step is available in Pro and Enterprise mode.

    1
  • Thanks Colby, I kinda figured you'd pop in to set me straight. I just couldn't remember!

     

    You'll want to use a Reboot Step Josiah, as it keeps the PDQDeployRunner service happy on the target machine. 

     

    You could do a Powershell step too, but a Reboot Step is definitely my recommended way

    Restart-Computer -Wait

    That will wait indefinitely for the computer to come back online checking for WMI, WinRM, and Powershell availability before moving on.

    You could target something specifically, especially if you know that you can remotely talk to a machine via WMI, or WinRM. That looks like this:

    Restart-Computer -Wait -For WinRM/WMI/Powershell 

    (Pick one from that list)

    1
  • Ok thanks, I saw the reboot step but I wasn't sure if it was meant specifically for the end of a package or if it could be used in the middle of one as well.

    0