PowerShell CLI 1.1 - Use Cases - Kill a number of tasks

Starting Situation

• A number of tasks might be running in JobScheduler that should immediately be killed.
• This could happen
  • due to some misbehaving scripts that cause a large number of job starts.
  • due to a business requirement for an emergeny stop.

Use Cases

Kill all tasks

C:\PS> Get-JobSchedulerTask | Stop-JobSchedulerTask

• The Get-JobSchedulerTask cmdlet retrieves all running tasks.
• The list of tasks is piped to the Stop-JobSchedulerTask cmdlet.
• Depending on the system load the killing of tasks might take some seconds. Repeatedly executing the Get-Task cmdlet should prove that no further tasks are running.

Kill tasks for any jobs that are located in a folder

C:\PS> Get-JobSchedulerJob /some_folder/some_subfolder | Get-JobSchedulerTask | Stop-JobSchedulerTask

• The Get-JobSchedulerJob cmdlet retrieves jobs starting from the specified directory. Any subfolders of that directory are included unless the -NoSubfolders parameter is specified.
• The Get-JobSchedulerTask cmdlet retrieves all running tasks for the list of jobs.
• The list of tasks is piped to the Stop-JobSchedulerTask cmdlet.

Kill tasks for any jobs of a job chain

C:\PS> Get-JobSchedulerJobChain -JobChain /some_folder/some_job_chain | Get-JobSchedulerJob | Get-JobSchedulerTask | Stop-JobSchedulerTask

• The Get-JobSchedulerJobChain cmdlet retrieves the specified job chain.
• The Get-JobSchedulerJob cmdlet retrieves jobs for the resulting job chain(s).
• The Get-JobSchedulerTask cmdlet retrieves all running tasks for the list of jobs.
• The list of tasks is piped to the Stop-JobSchedulerTask cmdlet.

See also

• The Stop-Task cmdlet supports a number of actions to kill (sending SIGKILL) and to terminate (sending SIGTERM) signals to processes, For details see How to Terminate Tasks.