vCenter Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2025 12:21 PM
Hello,
We have two vCenters in our environment. One main and one back up. When we first implemented discovery, we included both vCenters. We came across the issue of duplicate records, same CI but from each vCenter. I have excluded the back up vCenter from discovery, however, it is still discovering? What can I do to remove the back up vCenter?
Thank you
Nikki
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-20-2025 07:40 AM
Hi @NicoleHollihan ,
This data issue is something we are also experiencing. You want to build the automation as much as possible but on the other hand make sure your data is 100% accurate. Sometimes these two don't go together.
Tips:
1) Have regular checks on data. Either by a business owner (who normally has the final say) or by a configuration manager
2) You can also try to enforce different naming convention from vCenter making the CIs more easy to recognize by purpose.
Regards,
Jaap
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-21-2025 02:11 AM
How you know they are duplicate? Check the object id of the records to confirm if the ci is duplicate. You have to disable the discovery schedule which discovering the second one. Generally its a management ip which can discover the whole vcenter. In IP ranges check in what all schedules they have been added. I hope it it will fix it.