- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-14-2020 06:24 AM
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
Solved! Go to Solution.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-19-2020 02:43 AM
Hello,
I changed the dependent Identification rule, to independent Identification rule. Now it works.
Thanks in Advance

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-16-2020 12:29 PM
Hi,
In First screenshot the first one VmWare - vCenter VMs is for VM instance and if you open that probe then in description field of that probe you will see tha script include name.
Thanks,
Ashutosh

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-19-2020 02:25 AM
seems to be something with the IRE payload, have you raised a support case?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-19-2020 02:43 AM
Hello,
I changed the dependent Identification rule, to independent Identification rule. Now it works.
Thanks in Advance