Identification rules based on discovery source

[Jayesh Mohan3]

Now Advisors,

We have a setup of service graph connector with Intune. Due to the nature of the source data, we have setup two new custom identification rules on the Computer table to look at the enrolled date (from Intune) and serial number of the computer. This helps us create duplicate CI with the same serial number but different name. There is another identification rule that is activated for the Serial number table just like the identification rule on the hardware table.

So the identifier on the computer table has two entries:

1. Match with enrolled date and serial number

2. Match with the serial number on the serial number table (lookup rule)

We don't want rule (2) to be effective when the discovery source is Intune. In order to do that, we used advanced conditions on rule (2) to set Discovery source to be just ServiceNow. 

If there already a computer ABC with serial number 123 added to the CMDB by Intune, discovery creates a new CI  although a computer with the same serial number exists in the computer table as rule (1) and rule (2) results in No Match. Rule (2) here does not match as due to the advanced conditions that match on the discovery source.

Ultimately, we would like specific identification rules to be applied only to certain discovery sources. Is there a way to set identification rules to be applied only for certain discovery sources? Or would you please suggest any other way to achieve this. 

Thank you

[emir]

not sure I followed all of that, but here is my $.02

Computer Emir001 exist with SN of ABC123 on your network. Discovery and/or Intune found it and made a CI for it in the CMDB. Emir leaves the company and you want give that Computer to Frank. It is now Frank001 with the same serial. OOB the name will be updated. This is what you seem to want to change.

If you want to keep 2 records in the CMDB then you need to do the following:

When Emir returns his laptop, the CI needs marked as Retired. You will now add a new Inclusion rule to exclude Retired Computers. When the device is re-imaged and deployed as Frank001 (same SN) then a new record is created in the CMDB by Disco or Intune whoever gets to it first. You end up with 2 CIs in your CMDB, one retired and one Installed and operational. Your auditor is happy because INC and other history is kept with each lifecycle. Your asset manager has to do some magic to map the asset and or entitlements to the new CI.