“Requires verification” flag not being set appropriately?

[Craig Rogers]

This year we implemented ITSM (Change, Incident, Service Catalog, Knowledge).  We delayed Asset Management till after we had all of this up and going so we only created CIs with the thought of creating Assets after we have the processes in place and then implement Asset Management.  We came up on Jakarta but mid-year upgraded to Kingston.

In our current process of creating CIs from our various “discovery” imports (SCCM, Solarwinds, etc.), we have set all of the appropriate model categories set up such that they should “Enforce CI Verification”.  Meaning that when new CIs are created that are associated to the appropriate class, they should not automatically create assets but this can be done manually after the fact. 

It appears to me that we have this set up correctly.  Assets are not automatically being created,

BUT - when I look at all of the CIs, very few of them (about 400 out of 20,000) have the  “Requires verification” flag set to true.  Thus I am not able to create assets from them when I am ready. 

If I understand correctly, this flag must be set to true in order to allow creation of an asset from a CI "manually".  Based on the way we have the model categories set up and the fact that the CIs have the appropriate class and also are not automatically creating assets on initial CI creation, I would expect every computer CI that we have created should have “requires verification” set to true. I noticed this was happening when I went in to my sandbox environment to create some assets and do some testing in preparation for implementing Asset Management.

Can someone give me an idea as to why this might be happening and what I need to look at to help me figure this out?

Or maybe I do not understand how this is supposed to work so someone can set me straight? 

[tlcoop]

What is the 'Asset tracking strategy' on the model? That should be, 'Leave to category'.

Just an example:

Hardware Model:  8686-42A, which has model category: Linux Server; and asset tracking strategy: Leave to category

Model Category: Linux Server, has enforce CI verification checked

[Craig Rogers]

I looked at all hardware models and they all have "Leave to category".

[Craig Rogers]

I never did figure out why this flag was not being set correctly from implementation in July up through mid-October.  But, upon further investigation we discovered that starting in mid-October, all new CIs began having the the flag set correctly.  We did upgrade to Kingston in September and applied a patch in October so maybe it was a bug or maybe it had something to do with the way we moved from our DEV and QA environments into PRD initially.  

Regardless, it is working correctly now and I also worked with our ServiceNow Admin to get the Requires Verification set appropriately on all of the old CIs.  

[Mariano Lemus]

I hope this helps.

Provided the "Enforce CI Verification" checkbox is true in the model-category setting:

- If an asset is created a CI is created but the "Requires Verification" flag is false.

- If a CI is created (by Discovery for example) an asset is also created, and the "Requires Verification" flag is set to true, allowing either to Merge CI or to Create Asset (buttons).

M