Cloud Discovery creates same CI even the Object Id and VM Instance Id exists

[_zg_r T_rker]

We run Cloud Discovery in Azure environment. However discovery does not update the CI's existing in the CMDB,it creates new Virtual Machine Instance CIs. It should match the VM Instance Id and Object Id and update the CI. However instead of updating, it creates a new CI with the same VM Instance Id and Object Id. (We have Virtual Machine Instance Configuration Items in our CMDB which are creted via CloudForm integrations , but all have correct VM ınstance Id and Object Id values. Now we want to discover, however we are facing with this problem)

Best Regards

[Ashutosh Munot1]

Hi,

Check this HI article for identification mechanism for VMware.

https://hi.service-now.com/kb_view.do?sysparm_article=KB0813327
Thanks,
Ashutosh

[_zg_r T_rker]

Hello,

Thank you for your answer. This article is very useful for cmdb_ci_vmware_instances. However I cannot find the sensor script for  "cmdb_ci_vm_instance" (Virtual Machine Instance). I need same documentation for Virtual Machine Instances

How does the Virtual Machine Instance discovery work? Which probe and sensor scripts are running?

I upgraded my instance to New York Patch 9 (on -prem instance)

Before Upgrade it was sufficient to match vm_inst_id and object_id for identification, but I think something has been changed after Upgrade from Patch 6 to Patch 9. But I cannot find the discovery sensor script for Virtual machine Instances.

Thanks in Advance,

Özgür

[Ashutosh Munot1]

Hi,

This are the probes:

Sensor you can find in this probes.

And MID Server Script Include are used by this Probes:

Thanks,
Ashutosh

[_zg_r T_rker]

Which of them is for Virtual Machine Instances?