Service Graph for SCCM - how do you avoid creating duplicate CI / Asset Computer records ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-21-2024 04:41 PM
Hi all,
We are currently having an issue with our hardware asset(computer) wherein it is inserting a new ci record because the serial number is one of the identifiers based on OOB.
Problem being is, sometimes the computer hits SCCM first before the existing CI/asset record created by the procurement team is updated with the serial number. When this happens, SG SCCM will insert a new CI because it could not find a similar CI based on s/n.
How do you guys handle this in your org? If I can't control the timing of when the asset records/shells created by the procurement team will be updated with the serial number, can I just config SG-SCCM to not insert a computer CI?
I know it sounds silly and maybe not best practice but any help is appreciated.
Cheers,
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-22-2024 08:30 AM
Hi @Mark C_,
Please check the IRE rules for the particular classes for which data is updated by SCCM, you can resolve are correct configuration of IRE rules.
Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
Thanks
AJ
Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/
ServiceNow Community Rising Star 2024
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-22-2024 09:03 AM
If you are using Asset Tag (which cascades from Asset to CI when the asset is created), try creating a duplicate prevention business rule to check if a record exists by Asset Tag or Serial Number while creating CI. If Serial number is different but Asset Tag is same, then don't allow insert. When your procurement team updates serial number on the asset, that change will cascade to the corresponding CI. Next time when SCCM sync runs, it will find it by the new/matching serial number.
I suggest to create similar business rule on Hardware Asset table as well.
This would stop the bleeding but for the existing duplicates, you will have to bite the bullet and cleanup manually.
Regards,
Sharad