1. Home
  2. User Reference
  3. Service Check Reference
  4. Configuration Manager (Service Check)

Configuration Manager (Service Check)

Object Type: Service Check

Service Check Category: OmniCenter Checks

Passive: Yes

Description: Although named “Configuration Manager Passive Check,” this is technically an “authentication failure” service check. It is a passive check added to every device per the “Default” device template. This particular service check is updated only by the Config Manager, and is used to detect failures of a device’s authentication credentials. Any failure by the config manager to retrieve a configuration file (scheduled, manual, or triggered) will set this check to a WARNING alarm state.

Please note, however, that this check is intrinsically tied to the config manager. If the three criteria required for device configuration management are not all met for the respective device (resulting in the device being ignored by the config manager), this check will always remain in an OK state for that given device (since it’s passive). This means that even if the device does have bad credentials; if config manager is not managing the configuration files for it, this check will never detect those bad credentials.

Although this check is directly tied to the config manager; the incident opened by an authentication failure alarm is completely separate and unrelated to the incident opened by the config manager due to a detected configuration change. These two events generally shouldn’t happen together for a single device anyway, but the distinction is useful to make. By default, this service check uses the “blackhole” action group as the only selected action group in its alarm configuration. This means that no alert notifications are sent when an authentication failure alarm causes an incident to be opened. However, the alarm is displayed in the “Services” column of the Tactical Overview dashboard widget and listed in the Config Manager dashboard widget (both of which are represented on the Consolidated Dashboard). Administrators may add or change the action groups selected for this passive service check if they wish to receive notifications about an authentication failure of the config manager.


(Required) This field specifies a name for this check. The name entered must be unique among service check names on the host it is added to (the name may used again only on a different host). It is used to identify this specific check from among other service checks added to the same host.

Updated on July 24, 2020

Was this article helpful?

Need Support?
Can’t find the answer you’re looking for? Don’t worry we’re here to help!
Contact Support

Leave a Reply