Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Audit Job - General

The General panel lets you provide information that identifies an Audit Job. It also lets you choose the basis for the Audit Job-either components or live server objects.

Field Definitions

Name

Identifying name.

Description

Optional descriptive text.

Save in

Folder in which to store the Audit Job.

Select Audit Job type

Choose one of the following options:

  • Audit components — The job audits all components that are based on the component template you have specified.
  • Audit server objects — The job audits live server objects that you select.

Selecting Audit components requires that a component template and at least two components exist.

With components, you can use property substitution to compare items that might have slight variations across multiple systems.

Click here to learn more.

For example, to compare a file that exists in %WINDIR%\system32 on two systems where %WINDIR% evaluates to C:\WinNT on one system and C:\Windows on the other, take the following steps:

  1. Create a component template with a file part of ??TARGET.WINDIR??/system32/file.exe.
  2. Create (discover) components on each target server.
  3. Audit using the two components.

Number of Targets to Process in Parallel

Choose one of the following options:

  • Unlimited — Simultaneously runs the job on as many servers as possible. Application Server settings control the number of targets the job can access.
  • Limited — Specifies the maximum number of targets on which the job can run simultaneously. Limiting the number of targets is useful when a job might temporarily disrupt the functionality of a target server, and you want to limit that disruption to a small fraction of your managed servers.
    If you want the job processed serially at the target servers, set this value to 1. Note, however, that although this is the best approach for achieving serial processing, it does not always guarantee full serial processing at all targets; the first two or three targets might still run in parallel.

Set Execution Override

Select if this job should always execute as if your current role and user are scheduling the job. After you click this option, the job definition shows the role:user combination under which the job executes.

Clear Execution Override

Remove an existing execution override.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*