
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-16-2019 06:17 AM
Hello,
I'm seeing Hyper-V and Windows Servers creating duplicates of each other. I'm considering using unique identifier entries on the Hyper-V server class to look at servers table but then I believe new Hyper-V servers would not be created if a Windows Server exists.
I'm also considering a unique ID for Windows Servers to look for Hyper-V's, but thinking through this logic I'm not sure this would prevent the duplicate from being created. This would involve quite a bit of testing through unique use cases to determine.
Maybe a combination of ID entries and inclusion rules would do the trick but before I start down this road and commit I'm curious to hear what others have done to solve for this issue.
Can anyone provide their solution?
Solved! Go to Solution.
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-17-2019 07:18 AM
Model Categories do not create Assets from the extended classes. That's why you'll see all of the relevant Server classes broken out in the Model Categories. If Asset records are being created for your Hyper-V CIs, you must have an accidental customization forcing that creation.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-16-2019 11:49 AM
From an Asset Management standpoint, you shouldn't have to worry. By default, there isn't a Hyper-V model category [cmdb_model_category] for synchronizing CIs to Assets. You might want to check there if that's not the case for you and disable the category.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-17-2019 05:46 AM
Unfortunately they create computer assets, as the computer table is the table extended originally.
computer -> server -> virtualization server -> hyper-v
Maybe the solution is to actually create a model category and do not specify an asset table?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-17-2019 07:18 AM
Model Categories do not create Assets from the extended classes. That's why you'll see all of the relevant Server classes broken out in the Model Categories. If Asset records are being created for your Hyper-V CIs, you must have an accidental customization forcing that creation.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-17-2019 08:52 AM
You are correct there, I just tested creating a Hyper-V server directly on the table and it does not create a CI. What appears to be happening is when the server team builds the server they are using SCCM to push the OS ISO. When that happens it creates a computer record in SCCM, which then gets pulled down / updated nightly through our SCCM integration.
Maybe?
I've deleted the assets in my dev environment and I'm going to wait for all of the scheduled jobs/discoveries to run this weekend and see if the asset is being created by an integration or cloud discovery at some point.
Andrew you have been helpful, thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-12-2019 03:42 AM
If Hyper-V server is a virtual instance of windows, then why is there Asset information in the Hyper-V server class.
I am currentliy trying to import our Hyper-V enviroment (we are not using discovery), and I am a bit confused on the chain I would like to build (from rack to virtual machine instance).
If I create a windows server and then a hyper-v server, they will have the same hostname. Will that a challenge according to you