CMDB data flapping through sccm and discovery

[Sayali_N]

We have an scenario where the cmdb_ci_computer data is flapping through sccm and discovery

As per the requirement we need to update the cmdb_ci_computer attributes (serial number & name) just through sccm and cmdb_ci_server attributes (serial number & name) just through discovery.

We have implemented reconciliation rules for computer and server. For computer as discovery follows IRE and data precedency rule data is getting updated by SCCM only, but as for Server class as the SCCM data source does not follow IRE rules due to which cmdb_ci_server attributes are updated through sccm as well as discovery.

If anyone has encountered this issue before or has any insights to share, your help would be greatly appreciated.

[Community Alums]

Hi @Sayali_N ,

The best approach is extending IRE to cmdb_ci_server. Define Identification Rules (matching servers, e.g., by serial number) and Reconciliation Rules (prioritizing Discovery for serial_number and name). This ensures Discovery data prevails.

If IRE extension is not immediately feasible, use a Transform Map (for SCCM server updates). The onBefore script below prevents SCCM from updating serial_number and name:

(function runTransformScript(current, source, map, log, isUpdate) {
  if (isUpdate) {
    if (source.u_serial_number != null && current.serial_number != source.u_serial_number) {
      current.serial_number = current.serial_number; // Keep Discovery value
      // OR current.setAbort(); // Abort the entire update
    }
    if (source.u_name != null && current.name != source.u_name) {
      current.name = current.name; // Keep Discovery value
      // OR current.setAbort(); // Abort the entire update
    }
  }
})(current, source, map, log, isUpdate);

This script within the Transform Map blocks specific SCCM updates. Test thoroughly. Extending IRE is the cleaner, preferred solution.

Thank you....!

[Sayali_N]

Hi @Community Alums, 

We are having robust transform, can we know how can we add the above script in the robust transform? 

[Community Alums]

Hi @Sayali_N 

We can verify the data source precedence in the reconciliation rules and ensure data source for SCCM is configured with the appropriate lower precedence than Discovery for the cmdb_ci_server table, similar to how it's configured for cmdb_ci_computer.

In Addition, ensures that SCCM doesn't overwrite the Discovery data on cmdb_ci_server class.

[Sayali_N]

Hi @Community Alums, 

We are having the data precedence rule for SCCM that is configured with lower precedence than Discovery for the cmdb_ci_server table yet the sccm updates the cmdb_ci_server