Executing a job against failed targets

If you perform this procedure on a Deploy Job that failed on some target servers, the entire job runs again on those servers. All phases of the job repeat, even those that previously succeeded. Similarly, performing this procedure on a Batch Job that failed runs the whole Batch Job again, including all member jobs that previously succeeded.

Before you begin

Ensure that you have, at minimum, Read and Execute authorizations for the job. For example, to execute an Audit Job, you must have, at minimum, AuditJob.Read and AuditJob.Execute.

To repeat this procedure through an Execution Task, you must also have, at minimum, the ExecutionTask.Read and ExecutionTask.Execute authorizations.

To execute a job against failed targets

1. Find the job by doing one of the following:
   • Using the Jobs folder, navigate to a job, right-click it, and select Show Results.
   • Using the Servers folder, right-click a server and select Browse. Then select the Audit Results or Snapshot Results tab to navigate to a job.

2. Right-click a failed job run and select Execute Against Failed Targets.

   Warning

   Note

   As a preferred alternative to these first steps and if you are repeating this procedure after having already created an Execution Task during a previous execution against failed targets, navigate to the Execution Task in the Jobs folder (instead of navigating to the job). Then do one of the following:

   • Right-click the Execution Task and select Execute Against Failed Targets.
   • Right-click the Execution Task and select Show Results. Then right-click a failed job run under the Execution Task and select Execute Against Failed Targets.

   A window shows the targets where this job has ended with warnings or errors.

3. From Servers, select one of the following:
   • All Failures — Runs the job on all servers where errors or warnings have occurred.
   • All Warnings — Runs the job on all servers where warnings have occurred.
   • All Errors — Runs the job on all servers where errors have occurred.
     For each option, a list of the relevant servers (up to 100 servers) is displayed.

   • If you want an Execution Task created for this job as soon as the job starts executing, select the Create Execution Task check box. An Execution Task enables you to continue keeping track of subsequent job runs until the job executes successfully on all target servers. For more information about Execution Tasks, see Execution Tasks for managing job runs.

     Warning

     Note

     To create an Execution Task, you must have, at minimum, the ExecutionTask.Create authorization. The Create Execution Task check box is not available if you accessed this window from an Execution Task (rather than a job).

4. Click OK to execute the job immediately on the group of servers that you selected. A new job run is created for the job. This job run can be viewed under the job or under its associated Execution Task (if you created one in previously).

If there remain target servers on which the job failed, you can repeat this procedure through the newly created job run, preferably from where it appears under the Execution Task, or through the Execution Task itself.