Hi All,
There is possible issue reported :
Cloud VDIs are imported into the CMDB from two different sources – Azure Discovery and Intune Interface – and stored in different Tables. This is causing multiple duplicated entries in the CMDB.
When VDI gets for some reason returned or is not in use anymore, the Intune interface doesn’t set the CI to “retired” in the CMDB. It continues to be “operational”. The device name (ends with "-001”) of the returned VDI is reserved in Intune for the next requested/created VDI.
The new created VDI in Intune then becomes the already reserved device name but with a unique serial number. As a result, another entry gets created in the CMDB with the already existing CI name but with the new serial number from Intune. All CIs are then “operational”.
Also, we see a CI with the same name getting created from Azure into Virtual Machine Instance.
1. How can we handle the cleaning activity for already existing duplicate entries and achieve a single “operational” CI from the same source?
2. How can we merge CI from “Discovery source”=”SG-Intune” with the “operational” CI from Azure (“Discovery source”=”ServiceNow”) - or should these be merged at all? any docs/KA stating this is not advisable will be helpful
3. In order to avoid duplicates being created again in the future what steps to be taken?
4. The same record is also created in alm_hardware table, will it be a correct approach to create the record in alm_asset instead of alm_hardware since it's a VDI.
Thanks!
