Skip to Content
Unsupported content This version of the product has reached the end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Remediating drifts

A drift is caused by one of the following events:

  • An authorized change: A change in configuration that is initiated through a Change Request form can cause drift if the baseline of the comparison job is not updated.
  • An unauthorized change: Change in a configuration setting from the standard value, installation of unauthorized software, or modification in the hardware of a computer without prior approval.

If the drift can be correlated to a change request, the configuration manager can update the baseline and the comparison job as per the new standard. 
If a drift cannot be correlated to a change request, you can create a change request or an incident request from the drift management console.

The following topics describe the actions to be taken after a drift is detected:

Task

Reference

Correlate an authorized configuration change with a Change Request.

Create a change request or an incident to track unauthorized configuration changes.

 

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

BMC Helix CMDB 25.2