SG-SCCM and Computer Hard Drives/Disks Updates

[kchapman87]

My organization is working on ensuring we are tracking Computer Disks (hard drives) within ServiceNow when we have ran into a question that I cannot seem to find a clear answer on in regards to the SCCM Service Graph Connector.

If a USB/Removable/Portable drive (disk) is removed from a computer, will the CI record make this update upon the next SCCM scan (e.g. the disk will drive will no longer be related to the computer CI record)? Or will it remain and also appear on another Computer CI it may be moved to?

[Vishnu-K]

Hi @kchapman87 ,

In the SCCM Service Graph Connector integration, disk data is discovered from SCCM and processed through staging before being inserted into the cmdb_ci_disk table. During the transformation step a relationship is created between the disk CI and the corresponding Computer CI in the cmdb_rel_ci table, and the last_discovered field is updated.

If a USB, removable, or portable disk is removed from the computer, the next SCCM scan will not return that disk in the source data. Because the record is no longer received, the relationship between the disk and the computer is removed and the last_discovered field is not updated. At this point the disk CI becomes orphaned in the CMDB because it is no longer related to a computer.

A cleanup process then scans for disks discovered through SCCM that no longer have a relationship in cmdb_rel_ci. These orphaned disk records are deleted in batches to remove stale data.

In simple terms, if a removable disk is unplugged, it will stop being related to the original Computer CI after the next SCCM import. If the disk later appears on another computer and SCCM reports it again, a new relationship will be created for that computer during the next import.

You can check out the "SG-SCCM CleanupUtil" which will help you to understand how it works.

Hope this helps you, Please do mark it as helpful . And accept the solution.

Thanks,

Vishnu.

[Fabian Kunzke]

Great detail on the deletion process!

[naziyabegum]

 Hi, 

I'm facing this issue, currently we don't have the serial Number on our Disk table, so wanted to pull in the serial numbers as well,

Steps I followed is

->Given the Both values of SerialNumber as Serial Number in SQL query

-> Did the RTE field mappings and RTE entity mappings (Import, Temp, SCCM disk to disk)

-> I did the load all records, successfully I was able to get the serial Numbers for half of the records on the disk table, but the other half is Not pulling in, this is the exact issue let's say we have 4000 records in disk table only half of them pulled in the serial number other half have empty serial number, Cross verified with SCCM team they said they have the serial numbers for all the 4000 records that we are pulling in. 

Note: I have observed this issue as well, so when I Delete the Record in the Disk table which doesn't have the serial number, and then load the records and transform it then I'm getting that Deleted Record with Serial Number,

-> So basically, it is not updating it But the Insertion is happening

-> How do I navigate this issue any help would be really appreciated

[kchapman87]

@Vishnu-K 

I looked into the "SG-SCCM CleanupUtil", and it appears that is to be used for clean-up when moving from the old SCCM plug-in to the SG-SCCM. That is not currently what we are doing as we have been using the SGC for quite some time.