SCCM 2012 v2: Handling Device Deletions in SCCM

[taarik_rahaman]

Hi everyone,

We did a test recently and SCCM device deletions don't seem to flow into ServiceNow.   What have people done to have deletions/deactivations in SCCM flow back into ServiceNow?

Thanks all!.

[akash_mehta]

Taarik:   This is really a process issue - if something is getting aged out of SCCM, then that item should have been either put back into stock or retired in ServiceNow.   The data shouldn't be deleted in ServiceNow, as there maybe tickets and history associated to it.   Another possible item, if the processes are in place, is to mark the CI/Asset as missing when the item has not been discovered in the last "X" days and status = 'installed'.   This way, a team in your organization can start looking into why this item is not reporting and find out where the break down in process was.

-Akash

[taarik_rahaman]

Hi Akash,

I completely understand about the deletions issue.   I guess I didn't word it correctly...if an item in SCCM is removed, there is no communication back to ServiceNow to mark the asset as Lost/Retired.

The ServiceNow admin is going to try doing that by modifying the SCCM query to pull the last discovered field in SCCM into the Last Discovered field on the ServiceNow CI record.   With this info, we can set-up a Scheduled Job in ServiceNow to mark assets as Inactive, and deactivate/remove the Software Installation records associated with the Asset.

What do you think about this plan?

Thanks for your input Akash.

[akash_mehta · Accepted solution]

Taarik:   I agree about bringing in some Element from SCCM to populate the Most Recent Discovery field in ServiceNow.   This can be used to help run some reports or auto mark the item as Missing/Absent if necessary.

I would check with your SAM team if removing the Software Installations is a good thing or not.   I would wait on removing software installations, until the asset has been marked as Retired or Missing.

In any case, I think you are going down the correct path.

Regards,

Akash

[taarik_rahaman]

Thanks Akash!