Previous Topic: Delete Remediation ProfilesNext Topic: Create Profile Jobs


Run Ad Hoc Remediation Jobs from the Component List

While many CA Configuration Automation operations require you to specify a service or server on which to run an operation, an Ad Hoc Remediation Job does not show components in the context of a particular server or service. Instead, it uses a component-centric approach the lists all components currently on at least one server in your enterprise. From this list, you can navigate to a particular configuration parameter and view its value on each server where it appears. From there you can run or schedule a job to remediate one or more of these values.

To run an Ad Hoc Remediation Job

  1. Click the Management link, then the Remediation tab.

    The Remediation tab page appears.

  2. Click the Ad Hoc link (below the main tabs).

    The Ad Hoc Remediation page appears with the software components listed in the left pane.

  3. Click the plus sign next to the component to navigate to the file or registry entry you want to remediate.

    The Details page appears in the right pane.

  4. Enter the following information in the appropriate field:
    Action

    Specifies the type of remediation action.

    New Value

    Specifies the value to replace the unwanted value. If you want to see the current values before entering a new value, you can click the Servers link above the Details fields and view the current value on each server where the selected component exists (as described in step 5).

    Change Description

    Describes the purpose of the Remediation Job. This description appears in the Job Description column of the Remediation Jobs table after the jobs is created.

    Fail If Expected Value Not Equal to Actual Value

    Specifies whether you want this job to fail instead of completing when the differences in the values affects the current change you are making.

    This is important because the value stored in the CA Configuration Automation Database may not be the actual value on the server if the value has changed and the component has not been refreshed since the change. Having the operation fail lets you investigate and evaluate the differences before re‑running the Remediation Job.

    Stop If Pre Macro Execution Failed

    Specifies that the job stops if the Pre Macro fails to perform its function. For example, if the Pre Macro was created to stop a service before a remediation change could be made, and it failed, this job would fail.

    Pre Macro

    Specifies the macro step to run before the remediation occurs. A common example is to create a Pre Macro that stops a service.

    Post Macro

    Specifies the macro step to run after the remediation occurs. A common example is to create a Post Macro that restarts a service.

  5. Click the Servers link (above the Details fields).

    A pie chart appears above the Summary table.

  6. Do one or both of the following in the Summary table:
  7. (Optional) Click the Selected Servers link.

    The Selected Servers table appears and displays a summary of the servers selected in step 6.

  8. Click Remediate.

    The Remediate dialog appears.

  9. Select one of the following options from the Run drop-down list:
    Now

    Specifies that the job starts when you click OK.

    Later

    Displays the Time field where you can specify the date and time to start the job.

  10. Select one of the following options from the Notification drop-down list, then enter the Subject line for the notification if you want to override the subject defined in the selected profile.:
    Use Default

    Specifies that the Notification Profile that is designated as the Default is used for this job.

    User-defined profiles

    Specifies the user-defined Notification to use for this job.

  11. Click OK.

    One of the following happens depending on your selection in step 9: