ServiceNow Discovery not updating Computer records that have a non-SericeNow data source.

[codycotulla]

Hi,

In our environment, we have thousands of Computer Cis (cmdb_ci_computer table) that were created from an external system. These computer CIs have the discovery_source value that represents the other system (uCMDB is the value, but i don't believe the value is relevant).

Now that we are using ServiceNow discovery, we want these computer records to be updated by ServiceNow Discovery. I find though while the computers are being found, and Discovery is creating things like network adapters, Discovery is not updating fields like Data Source or Most Recent Discovery on the computer record itself.

Note that if i delete the CI, Discovery will create a new CI and then update the recreated CI on subsequent discovery runs.

So.. My question, what do we need to do to have Discovery update the computer Cis that were created by another system?

Let me know if you have any questions.

Thanks,

Cody

[Dave Ainsworth · Accepted solution]

Hi Cody,

Do you have any Datasource Precedence or Reconciliation Rules that could be preventing Discovery updating the CIs if uCMDB has recently updated them? Check the following:

Configuration->Identification/Reconciliation->Datasource Preferences

Configuration->Identification/Reconciliation->Reconciliation Definitions

Regards,

Dave

[codycotulla]

Hi David,

Thanks for your reply.

I see the problem when I don't have any Datasource Precedence or Reconciliation Rules set up. I've also tried setting up rules that give ServiceNow a higher precedence that the uCMDB data source. 

Regards,

Cody

[amititp]

yeap, Precedence & Reconciliation should take care of your query.

Also, check your sys_properties on DUP Tasks settings, initially good to have Disc. Tasks created than an Auto Reconciliation, so as to understand and gauge the gaps.