{"id":1891,"date":"2013-12-23T15:19:58","date_gmt":"2013-12-23T15:19:58","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/powershell\/2013\/12\/23\/automatically-resuming-windows-powershell-workflow-jobs-at-logon\/"},"modified":"2019-02-18T13:05:26","modified_gmt":"2019-02-18T20:05:26","slug":"automatically-resuming-windows-powershell-workflow-jobs-at-logon","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/powershell\/automatically-resuming-windows-powershell-workflow-jobs-at-logon\/","title":{"rendered":"Automatically resuming Windows PowerShell Workflow jobs at logon"},"content":{"rendered":"\n

PowerShell Workflow<\/span><\/a> helps IT Pros automate the long running tasks, or workflows, that can affect multiple managed computers or devices at the same time. Windows PowerShell Workflow is designed to be robust and recoverable. The features that are built into Windows PowerShell allow you to restart the target computers and, if the workflow is not yet complete, to reconnect to the target computers automatically and continue with the workflow commands. You can even restart the computer that is running a workflow, which allows you to run the workflow on the local computer, or include the local computer in the list of target computers. As you might know, a PowerShell workflow job is suspended when the local machine restarts as part of the workflow job <\/span>execution, among other reasons, like user-initiated reboot. In this case, IT Pros need to resume the suspended jobs manually after machine restart. <\/span><\/p>\n

This blog post shows how one can automatically resume the suspended workflow jobs at user logon using <\/span>PowerShell Scheduled Tasks cmdlets<\/span><\/a>.<\/span><\/p>\n

For reference: In PowerShell Workflow, every user gets a unique workflow job store path based on <\/p>\n