- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
on 05-25-2021 05:16 AM
Hi all.
It appears that baseline ServiceNow configuration will create asset records [alm_asset] when new CI is created even if this CI applies to virtual machine. I'd like to better understand what are best practices to avid asset record insertion for CIs whose "Is Virtual" field value is 'true'
My two comments are:
-- I would hate to make changes in baseline business rule "Create Asset on insert"
-- In 'Hardware Category' records there is a way to set 'Asset Tracking Strategy' to 'Don't create assets' but you never know what new model category will be created in the future to prevent new hardware categories from creating new assets for virtual machines.
I would appreciate your thoughts on best practices you followed for way around to this configuration.
Thank you.
Val
Solved! Go to Solution.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
on 05-25-2021 06:01 AM
Add a condition in the script to check to see if the CI has a field called "is virtual" and then if that value is True, exit.
https://<yourInstance>.service-now.com/nav_to.do?uri=sys_script.do?sys_id=0d6b59dc1b0310002502fbcd2c0713a5
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
on 05-25-2021 06:25 AM
Thanks for your reply Curtis. Based on your experience is this best practice to follow? I ask this because I hate to make changes in the baseline business rule. Thanks a lot 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
on 05-27-2021 06:24 AM
Very interested in this topic - we are discussing if virtual machines are assets. What is the best practice here - I'm thinking of using the "enforce CI verification" Yes.
I want to make sure that if a CI is created - it doesn't create an asset - but if an asset is created and the coalesce field (whereever we're supposed to identify that) matches a CI - then it will connect the 2.
Does this make sense?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
on 05-28-2021 05:27 AM
Thanks for your reply.
I don't think we should create Assets for virtual machines. Assets are used to track a record from financial perspective and virtual assets don't have financial value unless we're tracking sw licenses which then falls in software asset management area.
Enforcing CI verification seems like a good idea, but I was wondering if its a good idea to go through all possible CI verifications when we initially implement 'Discovery'? Then how do we maintain future records? It could end up being full time job for someone.
My hope was ServiceNow added system property (something like 'Prevent virtual CI from creating an asset') that we would set to 'True' but that does not seem to be the case.
I wonder how Steven Bell (Community MVP) would answer this question, but I don't know how to tag him on this post. This is his background. Maybe
