Identification Rule Question - SCCM

[anfield]

Is there a way for computers being created via SCCM specifically, to have their own custom id rules that are specific to SCCM?

We have a requirement from a customer to use only serial and or another attribute SMBIOS_GUID to use, and to use those attributes only to identify a computer.

Is there a way to create another ID rule for SCCM to use (and maybe qualify to that Discoverysource), or another workaround to achieve this? We have a small amount of other data going into the computer table (from other sources), and it might be best not to customize to out of box hardware rule.

[pr8172510]

Hi @anfield,

Yes — this is possible using IRE Identification Rules + Data Source Rules for SCCM specifically.

Create a dedicated Identification Rule for cmdb_ci_computer

     using only:

• Serial Number
• SMBIOS_GUID

and qualify it for SCCM source.

 

Do NOT heavily customize the OOTB Hardware Rule directly.

Instead:

1. Create a new Identification Rule
2. Set higher priority than OOTB rule
3. Add condition:

Discovery source = SCCM

1. Use identifiers:

• serial_number
• smbios_guid

Ensure:

• SCCM always populates SMBIOS_GUID consistently
• serial numbers are normalized
• IRE precedence order is validated

source-aware identification through identification rules and reconciliation definitions

• using stable unique identifiers
• minimizing OOTB customization
• using source-specific reconciliation behavior where possible

This is the safest long-term approach for SCCM-specific identification behavior.

[anfield]

Thanks for the response.

Giving this a try and getting a message on the identifier table - "There is already an identifier created for this CI class, use and edit rules associated with it!"

The oob computer rule is inactive (and has independent) checked. Id rather create a new custom one and leave this one alone