What does "Enforce CI verification" do in Asset Management?

[Uncle Rob]

I'm having trouble understanding what this does on a Model Category.   I THINK it should allow you to create a CI manually without having it linked to a specific Asset, but when I test it, something totally different happens.   I test by creating a new CI for a model category with "Enforce CI Verification" on, but it immediately associates that Config Item with an "Unknown" asset.   There is seemingly no way to create a new asset of a specific class.

Did I completely misunderstand the purpose of that field?

[Community Alums]

Robert,

This allows you to create a CI (manually or via some discovery source) and it will not automatically create an asset. With it turned on, when new CIs are created, they are automatically flagged with the Requires verification field as true, and those CIs present two options when you view the CI record: Create Asset and Merge CI.

As you might expect, Create Asset creates an asset and turns off the Requires verification flag.

Merge CI is useful for a situation where an asset for that particular CI was created via a separate process (which would create an associated CI) and another CI was created either manually or via the discovery source and did not properly coalesce on the CI created by the asset. This allows you to merge these items.

Typically you would end up with an "Unknown" asset if you did not define a Model ID on the CI, but with Enforce CI verification on, that should not happen until you tell it to create the asset. If you are seeing otherwise, I would be curious to take a look to see what might be happening.

ben

[Uncle Rob]

Thanks, Captain Sweetser.

[jesusemelendezm]

Hi Ben,

I tried this scenario with two laptops:

Scenario # 1:

1) Uncheck enforce CI verification for model category "Computers".

2) Run discovery against a specific computer

3) CI was created and asset was created (Is it normal behavior)

Scenario # 2:

1) Check enforce CI verification for model category "Computers".

2) Run discovery against a specific computer

3) CI was created and asset was created (I do not see any flag indicating that CI is not verified). The true/false type field "require verification" is uncheck in both cases. Thanks for your help.

[Community Alums]

Jesus,

First, can you please verify a couple things in Scenario 2?

Did you ensure the CI (and corresponding asset) did not exist prior to the targeted discovery (you can check the Create field)?

Be sure the new CI created ended up in the Computer CI class and not one of the classes that extend it. If Discovery identified it as a Server or some other class of CI, then it would use that corresponding Model category. Model categories only apply to a specific class.

That's where I would start to investigate here.

Ben