CMDB data flapping through sccm and discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-11-2025 03:45 AM
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.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-12-2025 01:00 AM
Hi @Sayali_N
if SCCM with a lower precedence than Discovery, then important to ensure that the "Data Precedence" rule is set correctly for the cmdb_ci_server class in the Data Source Configuration.
also ensure Discovery Priority should be higher than SCCM for both of these fields.
There might be additional configurations in SCCM that are forcing the update to the server.
For testing purpose checks if the data is being updated from SCCM for servers, and if so, prevent updates from Discovery for the serial_number and name fields(you can create BR for this).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-14-2025 02:38 AM
Hi @Community Alums,
Thanks for your response.
How can create a BR just for the 2 fields and check if those are updating through SCCM.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-14-2025 11:13 PM
Hi @Sayali_N
To make sure the fields are getting updated through SCCM. we need a field in your table (e.g., source, updated_by_integration, etc.) that indicates SCCM updates, you can use this field to identify SCCM-based changes.
then the follwoing script will support you to verify those filed is getting updated by SCCM.
Script:
(function executeRule(current, previous /*null when async*/) {
var field1Updated = current.field1 != previous.field1;
var field2Updated = current.field2 != previous.field2;
if ((field1Updated || field2Updated) && current.sccm_update_flag == true) {
gs.info("Field1 or Field2 has been updated via SCCM.");
}
})(current, previous);