Computer Asset state set to 'In Use' when discovered during build

[Richard Nelson]

Hi folks, I'm looking for ideas/suggestions on this issue.  When our desktop teams put new computers on the bench to install the base build they are discovered and automatically set to 'In use'/'Installed' in the Asset module/CMDB. 

In most cases the computers are then put into stock until they are needed so the teams have to find the newly created asset/CI and correct the status to In stock, etc.  This is another manual step enforced on them which in this age of automation and AI is not popular.

Additionally, If they do nothing and leave them as 'In Use' but unassigned it also shows up in our asset metrics as a breach of process causing further discontent.

I have tried excluding the build vlans from the discovery ranges but it's not an effective or efficient solution. 

Has anyone experienced similar challenges and found solutions to this real world problem?

Thanks in advance,  Richard

[CasperJT]

Hi Richard,

In my view life cycle cannot be handled by a discovery tool. There are simply too many possibilities. We are collecting our assets from Intune and let Intune manage all the OS level attributes of the asset. However anything relating to governance (ownership/life cycle) is managed through our processes.

For example when a machine is received from the vendor and awaiting installation we place it in "Inventory - Available". When it is installed we move it to "Deploy - In Stock" and when assigning it to a user it is moved to "Operational - In use". The problem with discovery tools is, that they do not know if a machine is operationally in use, being tested, is in repair or even stolen, so for those reasons we elect to keep control ourselves.

I hope this helps.

//Casper

[matrixtushar]

Hi,

A possible solution that I can think of... 

Whenever a new record is created on the cmdb_ci_computer table with a condition that class=computer then create a before insert business rule to set its initial values to be:

operational_status = Non-Operational

install_status = In Stock

Usually these systems are prepared and put off in racks for sometime before they are switched on again to be allocated to users.

As soon as these systems will return to the network and are caught up in discovery, their "Updated" timestamp will change and an On Update business rule can reset the state to Operational and Installed and if you have owned_by or assigned_to as a recommended attribute, your health scan will pick up and ask the local IT to set the value from the sys_user table.