How to prevent discovery to not to create a CI without a serial number attribute.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-11-2022 03:12 AM
Hi all,
We have run into an issue where we create duplicate CI's whenever serial number is not discovered, I was wondering if anyone has come up with a solution that if the Serial number is empty, do not create the CI?
Issue: Sometimes SNMP query for serial number getting time out for few legacy printers. In such cases duplicates records are getting created without the serial number.
Expectation: Should not create a CI if serial number is empty.
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-11-2022 04:22 AM
Hi,
ServiceNow identify CIs using CI Identifier. If you want it only based on Serial Number then do the following
- Goto Discovery Definition > CI Identification > Identifier
- From the list search for "Hardware Rule" in name field
- From the "Identifier Entries" related list deactivate all the entries where serial_number is not present in "Criteria Attributes"
Now Identification happens only if serial_number has some value
Palani
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-17-2022 02:24 AM
Thanks PalaniKumar.
Let me be more specific on the requirement.
Expectation: Only Printer CI records should not be created whenever Serial number is not discovered.
As per current design, Our Printer Discovery is using out of the box IRE rules.
Is there any solution Which is not involving the defining new custom IRE rules for Printer CI

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-17-2022 09:19 PM
Hierarchy as per class manager
Configuration Item----->Hardware---->Printer
What ever Mr Palani suggested is correct . Just do the same changes in Printer Class IRE Rule.
Local IRE configuration will override the Parent configuration and it will not Impact Other Classes derived from Hardware Class.
Regards
RP