- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-04-2024 12:32 AM
We know that ServiceNow creates one entry in VM instance and anohter entry for its host in Server table when discovering servers in cloud.
My question is - what is the use of discovering VM instances? Technically is a duplicate and redundant record for me, unless you say its not 🙂
Please share your feedback if know the rationale behind it/use cases of VM instances.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-12-2024 06:50 AM
Just some final thoughts from me. You are correct and most clients use vCenter for management. But ServiceNow goes farther than management. It links things together that vCenter doesnt, and if that vm instance is not there you disconnect the line between the Computer record and the VCenter system is running in. If ever you plan on doing any event monitoring, Service Mappings, these come in as a requirement, cause and effect reporting type of scenario. For day to day stuff yes, it can be ignored, and I would just do that Ignore the records. If in the future the other products serviceNow provides needs it in the middle, then you have that detail that ServiceNow can use.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2024 07:16 PM
How would we avoid selecting the wrong CI record when raising the incident? When typing the number it may show 2 records with the same name
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2024 06:23 AM
I would recommend you look into using the "Principal Class filter". This way way you can have the VM Instance as a CI, but only the virtual server running in the VMI will be presented as a CI in your Configuration Item field.
Update the list of classes in the Principal Class filter
In the CI Class Manager you can define Principal CI Classes. If you modify your reference qualifier on the Configuration Item field on tasks you can prevent items with the same name to create confusion.
For example, if you run Discovery you may end up with a VMI, a Windows Server and a DNS Name that are all the same name.
Hope this helps.
//Casper
