Audit Job overview
Audit Jobs allow you to compare server objects, components, server-object-based snapshots, or component-based snapshots to determine whether their configurations match a standard configuration.
After running an Audit Job, you can view its results and quickly identify discrepancies between component configurations. When you identify discrepancies, you can bundle changes into a BLPackage and deploy the changes to a server so its configuration matches the standard configuration. Audits can also perform a security function by quickly identifying unauthorized changes to server configurations.
Audit Jobs require you to identify a master — that is, a server with a standard configuration that is used as the basis of comparison. The procedure for identifying a master depends on how you define an Audit Job:
- If you define an Audit Job by selecting live server objects, you must select either a server and a live server object on that server or a server-object-based snapshot as the master.
- If you define an Audit Job by selecting one or more component templates, you must select one or more components or component-based snapshots that act as a master.You can also select a server as a master, in which case the Audit Job performs automatic component discovery and generates components for use in the Audit Job.