SG-SCCM - Decommission of devices

[gagribben]

Hey Guys, I apologize if this is not the correct forum to post this question. Please feel free to redirect it to the appropriate forum if needed. 

I am looking for advice on how to handle device decommissions from SCCM. Currently, there is a process that spans several teams that involves physically collecting the device, removing licensed software, removal and destruction of hard drive, etc. However, it is not uncommon that the device will reside in SCCM for quite some time (after the device has already been removed from inventory) before its removed from SCCM. How are you handling maintaining an accurate install state/operational status if SCCM is still a source of truth. Is there some sort of attribute that we can use to define a retirement rule. I am trying to prevent the need to have manual updates to cmdb and maintain an accurate CI install state/operational status.

Thanks in advance. 

[goldenjc97]

Our depot team ultimately is the last team to have the device and I have a catalog item only opened to them that has a MVRS where they add all the items they are checking in. If it's a computer, it asks is it going to surplus to back into circulation, and also has some required checkboxes to make sure they remove from SCCM, etc... Depending on if they chose surplus or back to stock, the flow iterates through all items and updates the install/operational states accordingly. I tried to make it as simple as possible.

[gagribben]

Thanks for the response. I think the issue we are having is that the devices are not being removed from SCCM, and if they are it's inconsistent. I think there is some task or process that the team does where they are eliminating machines from SCCM that haven't checked in for a certain amount of time and that's done on like a monthly meeting, which causes problems because if the device is still in sccm it can potentially show as installed/Operational on the CI. Ideally, the device should be removed from the endpoint (SCCM); however, there is pushback from the team, and they want to automate as much as possible.