Assets are being created for virtual machines even after the model is set to "Don't create Assets"

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-26-2024 02:44 PM
Assets are being created for virtual machines even after the model is set to "Don't create Assets"
Please help how to restrict the CI not to create any assets.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-27-2024 11:51 PM
Hi @Community Alums
May i know on which environment you are testing?
You will NOT modify baseline Create Asset on insert business rule, since it has long term implications on future instance upgrades.
-Even if you were to modify Create Asset on insert" BR, it will not work, because there is "Asset - Create asset delayed sync" scheduled job that will still create an asset from CI. And if I were to modify that too it would be to much to modify in the baseline.
Here solution was:-
-Run discovery in your DEV environment. Check what kind of virtual assets are being created and note their "Hardware Model" records. For example you have:
1. "VMware Virtual Platform"
-Modify those Hardware Model records "Asset tracking strategy" to "Don't create assets"
-Export those Hardware Records in .XML format and import them on higher instances
-Run Discovery on higher instances and assets for hardware models that you've imported (and previously modified not to create assets) will not be created.
Unfortunately this approach will not work if you already ran discovery in higher instances because asset records have already been created.
Mark it Helpful and Accept Solution. If this helps you to understand.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-30-2024 05:01 AM
Hi Basha,
Thanks for the response. We are importing the CI's in production environment. For the virtual CI's, assets are being created despite the "Don't create Assets" is selected.
And your answer of creating in lower environment and import to higher. Wouldn't be any alternate solution like any kind of configuration not to create assets for virtual CI.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2024 02:18 AM
Hi @Community Alums,
This can be because of the sync business rule, May be you need to create a business rule on insert exceptionally to avoid creation of asset.
☑️ Please mark responses as HELPFUL or ACCEPT SOLUTION to assist future users in finding the right solution....

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-30-2024 05:05 AM
Hi Sohail,
Thanks for the response. isn't there any OOB configuration to avoid there. Is this a servicenow product bug itself? because "Don't create Assets" not working anymore.
Any help would be appreciated. Thank you.