Discovery not updating the virtualized by:: virtualizes relationship

Priyanka Ghosh · ‎04-07-2023

Hello,

The issue is that the old VM instance is Terminated (State) and Absent (Install Status) and now there is a new VM instance which should ideally have a "virtualized by:: virtualizes" relationship with the existing windows server. But the relationship isn't updating. The windows server is still having relationship with the Terminated VM instance.

Also, to mention, on research we found that under the same scenario, the discovery is updating the relationship for very few of them but for majority it isn't.

What could be the possible reason?

Any insights on this would be greatly appreciated.

Regards,

Priyanka.

Ratnakar7 · ‎04-08-2023

Hi @Priyanka Ghosh ,

Here are a few possibilities:

Discovery is not running: Make sure that Discovery is running and configured correctly. If it's not running, it won't be able to discover new relationships.
Schedule: Check the schedule for the discovery job. If it's running too infrequently, it may not be able to capture all changes in a timely manner.
Dependency mapping: Check if the dependency mapping for the windows server is correctly set up to capture the virtualized relationship. If the mapping is not set up correctly, it may not capture the relationship even if Discovery discovers it.
Data quality: Check the quality of the data in the CMDB. If there is incorrect or incomplete data, it may not be able to capture the relationship.
Discovery settings: Check the Discovery settings for virtualization. Make sure that the settings are configured correctly to capture the virtualized relationship.

If my response was helpful in resolving the issue, please consider accepting it as a solution by clicking on the ✅Accept solution button and giving it a thumbs up 👍. This will benefit others who may have a similar question in the future.

Thank you!

Ratnakar