- 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 07:30 AM
Hyper-V is the virtual instance of the Windows OS, and are technically not duplicates. This would be the same idea as a Server CI and a VMware Virtual Machine Instance. The only confusing part is that Hyper-V is extended from Server rather than Virtual Machine Object.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-16-2019 10:22 AM
That's not technically correct... Discovery is not classifying the instantiated server as a Hyper-V server. Servers RUNNING Hyper-V are being classified as Hyper-V servers and because of this they are duplicates. All of my Hyper-V servers have Windows Servers that share a hardware model and a serial number.
The actual VM's are being classified as "Microsoft Virtual Machine" which I am not creating assets on.
It seems like the real issue is that Hyper-V servers are using the same hardware models and I can't tell it not to create assets so we do technically get a duplicate from the asset management perspective.
Thoughts?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-16-2019 10:35 AM
You are correct, I guess Hyper-V is technically more like ESX servers in my poor example. Regardless, this is intended by Discovery as answered in the blow HI Knowledge article.
https://hi.service-now.com/kb_view.do?sysparm_article=KB0719772
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-16-2019 11:11 AM
Thanks Andrew that is helpful, at least to know there is some acknowledgement of this. I think it's an issue and should be handled differently because I now have two assets using the same server hardware and this impacts budgets for replacing hardware and other things. It's good for software asset management and bad for hardware asset management.
I'm still not sure how to proceed but I don't want to do any heavy customizing at the risk of defeating OOB relationship creation.
