Reinstate the software once the CI state has moved back into an Operational State

[will_forster]

I have had the below request from a customer however I am not sure this is possible. I also do not think it should work this way. It all pulls from SCCM. Sadly i do not no enough about SAM to give the customer a decent response to this.

Basically when you move a CI to a none operational state. it removes all software from that record. as it should I believe. But if you change the state back it does not reinstate all the software on the related list. which I also believe this is how it should be.

Customers Request.

"Look into getting the software installed to appear so if a CI in a none operational state, which has had software installs removed, to have said software installs restored should that CI be returned to an operational state."

[Daniel Slocum · Accepted solution]

Hi Will,

If you move a CI to Retired, Lost, or Stolen, then automation in SAM will remove all of the Software Installations. However, moving a CI to anything else will leave the software installations intact. In most, if not all, cases an organization is responsible for the software installed on a device even if that device is not currently in use.

If a software title is uninstalled, then the corresponding software installation record should also be removed via automation within the SCCM Service Graph Connector. This use case supports Reclamation and other Uninstall processes. 

The above are baseline functionality for SAM.  If the customer is asking you to automate the removal of SW Installations for any other state, you likely should ask the "why" question and make sure they understand that "in stock", or under repair devices will still have software accountable under vendor audit.  If you build automation to remove SW Installations, SCCM will add those installation records back to the CI once it is found again on the network. 

[will_forster]

Hi Daniel..

Does SCCM update computers which are in a retired state ?
Should devices be set to retired from CMDB Computers table or SCCM ? Does it matter ?
If you can retire devices in servicenow then what happens if you put it back into an opertional state ?

Issue : Organization is concerned that when CI Computers are being placed back into an operational state that the software that should be
installed on that device does not come back onto it.

[will_forster]

Hey Daniel, are you able to provide any additional advice ?