Using Software Delivery › Delivery and Staging of Software › Pre- and Post-Job Check Processing

Pre- and Post-Job Check Processing

The pre- and post-Job Check processing features make it possible to run external executables before or after a software delivery (SD) job. You can specify an executable that should run before the actual SD job is processed and an executable that should run after the SD job, or the last SD job in a job chain, has run.

These executables are specified through the agent policies 'Jobcheck: Pre-command' and 'Jobcheck: Post-command", as follows:

Jobcheck: Pre-command

Specifies an executable that runs before an SD job or before the first SD job in a batch is processed. An example is switching off an antivirus realtime monitor for the duration of a job container.

Default: empty

Jobcheck: Post-command

Specifies an executable that runs after an SD job or after the last SD job in a batch is processed.

Default: empty

The Post-command is only run, if a Pre-command is also specified!

Pre- and post-Job Check processing takes place regardless of the job linkage setting (batch job, synchronized, or no linkage) for a Job container tab.

Notes:

• If more than one job is run for a specific computer or user target, first the pre-Job Check executable is run, then all jobs, and finally the post-Job Check executable. If an intervening reboot or logoff takes place during job execution, the SD agent will run the post-Job Check executable, execute the reboot or logoff, then run the pre-Job Check executable, and continue with job execution.
• If Restart machine or Logoff user is specified as an SD procedure option to take place before job execution, no pre- or post-Job Check processing is done, until the first job in the job chain is to start executing.

  If Restart machine or Logoff user is specified as an SD procedure option to take place after execution of a job or after the last job in a chain, this does not cause any pre- or post-Job Check executables to run.

• Pre- and post-Job Check processing only takes place, if Job Check detects a waiting SD job. Job Check does not automatically start pre- and post-Job Check processing.