Applications Systems

'Server configuration has changed' and 'Server configuration differs from baseline' alerts not triggered in SCM

This article describes and provides a work-around for the following issue: 'Server configuration has changed' and 'Server configuration differs from baseline' alerts are not triggered in Server Configuration Monitor (SCM) after profiles are unassigned and then re-assigned to the same node.

First published date

5/30/2019 7:06 PM

Last published date

4/27/2021 3:18 PM

Overview

Product section

Server Configuration Monitor

Resolution

Restart the Orion Alerting Service.

After profiles are re-assigned to the same node, 'Server configuration has changed' and 'Server configuration differs from baseline' alerts are now triggered in SCM.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.