- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2022 08:39 AM
When ServiceNow Discovery creates a CI for virtual computers and servers it also creates a record on the hardware asset table. How do you avoid ServiceNow from creating records for virtual devices on the hardware asset table.
Solved! Go to Solution.
- Labels:
-
Multiple Versions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2022 01:42 PM
Look at this KB: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0712445
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2022 01:42 PM
Look at this KB: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0712445

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2022 08:06 PM
You have to handle it at a model level for VMs by setting the Asset tracking strategy to Don't create assets.
It is common that a new model pops up and you have to do cleanup in arrears. For these we have asset health reports to highlight this occuring.
We have a fix scripts that finds all assets where the associated CI's isvirtual flag is true, the script then updates the models asset tracking strategy and deletes the associated assets.
We should create a button called Nuke the Assets on the hardware model form for asset managers to run it themselves instead of depending on the platform admin. This button would display if the asset tracking strategy is Don't create assets