- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-16-2016 06:07 PM
We have turned on 'Enforce CI verification' on our Model Categories so that new CIs do not automatically create assets. This is due to the fact about 90% of our CIs do not require assets.
We are looking to add assets manually at the start of the process ie. before the device is actually on the network and discovered.
What I would like to do, is that when the device is turned on and automatically discovered and a CI created, that the system tries to find a previously manually created asset based on matching serial number.
Would I need to wright a new Business Rule with some javascript to try and match to an existing asset based on serial number when a new CI is inserted?
Not sure if there is a more out-of-the-box way to do this as it seems it would be a fairly common use case.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-17-2016 07:48 AM
The coalesce would be AND if you added one, so it would only coalesce if both match. How are you setting the IP Address to coalesce on? Is everything in your environment running with static IPs? My initial thought is that this sounds dangerous. If any IP address changes, suddenly you've replaced a CI with a different device. I would recommend using something that doesn't change, like a Serial number or Asset tag to uniquely identify items for your coalesce.
When the Asset is created, the CI is created. You can use the CI Status (install_status) and the Asset State to indicate when the device is active.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-12-2018 03:36 PM
what things would be stopping my ci from being created? I loaded assets, (over a month ago) and the CI's are not being created.
It was noticed when they brought one back to mark it as back in stock and the assets are not found.
(this is about 225 thin clients - and they are not the only thin clients we have)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-12-2018 07:25 PM
Hi Susan,
I'm not sure I understand what you are describing. I'll restate it how I interpret your post and you can correct me.
You state that you loaded the assets, but the CIs were not created when you did this. If this is the case, there are a couple things you can check:
- Did you populate the Model Category and Model when you loaded the assets? These are required fields when you create the asset manually, but you can import without them. This could cause ServiceNow to not create corresponding CIs for these assets.
- If you did populate the Model Category, verify that the Model Category you used has both a CI class and an Asset class defined. If it only has an Asset class, it will not create a corresponding CI.
Then you state that when a thin client was brought back in to return it to stock, the Asset record was not found.
- How are you searching for it?
- When you loaded it, did you have a unique value, such as Asset tag or Serial number?
- Is it possible that something got run to delete the records?
This is just a start to troubleshoot here.
Ben
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-22-2018 02:49 AM
Bsweetser - If a CI Class has not been defined on a model category, what can you do about it?
ServiceNow won't let you change it after creation. I guess I could force it by fiddling with the ACLs but, clearly, there is a good reason why this isn't allowed OOTB.
So, I can recreate the model categories from scratch but then all of the assets are no longer associated with them.
P.S. I arrived at this thread because I have created assets that have not synchronised in CIs. Everything else checks out except the CI Class.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-15-2018 02:26 PM
I realize I am slow to get back to this, unfortunately I need to have more time in the day 🙂
Answers to your questions are all yes. Model Category - Computer, Model HP t530 Thin Client, and it does have both classes assigned to it
And yet the CI never happened: this is one I loaded in January
My model looks like this:
Sounds like I have some surface pc's with issues as well. not sure if I am just not defining the model correctly. Should I remove the model number?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-15-2018 02:30 PM
A little more -
My script from the vendor was loading my assets tot he asset table, then discovery was to take over, but it seems that all of our thin clients don't get discovered (well) and remote computers. We just had a person go to discovery training recently as we lost the resource in that area, so hoping they can get to the bottom, I think our cmdb is a mess since I signed up for asset mgr.
Not sure I want to continue (seems little value) in the script from our asset project vs the way the old team used to load these into the CMDB and then let the Asset happen? will that work better.