Ask the Expert: Live Chat | Assets and Models and CIs, Oh My!

ServiceNow · ‎06-25-2015

Original Air Date: Thursday, July 9, 2015 | 10:00 AM (PDT) | 1:00PM (EDT)

Do you struggle with the difference between Assets and Configuration Items? And why do we need Model records? Isn't that just another thing to maintain? Get a better understanding of these items, how they are different, and how they work together in this session with Ben Sweetser.

Ben Sweetser is a ServiceNow "old timer" with experience on the full platform with focus on Asset and Configuration Management and Automation, such as Orchestration and Discovery.

</p>

Community Alums · ‎07-16-2015

And you are correct. That was the exact reason the button was created: mistaken asset creation.

braddiamond · ‎09-22-2016

Ben - How can I get a copy of the deck you presented in this video?

Thanks,

Brad

Community Alums · ‎10-04-2016

Hi Brad,

I'm not sure I still have the deck around any more. Is there anything in particularly you needed? Was it just for your information?

Ben

braddiamond · ‎10-18-2016

Hi Ben,

It was more to share some of the relevant content internally, as opposed to having them watch the video.

Thanks anyways!

Brad

roy_walton · ‎12-07-2016

Ben,

Very helpful webcast, thanks!

Why is it that for many of the Model Categories that shouldn't have models associated with them (like "Next Hop Routing Rule" and "Switch Port"), Discovery wants to associate the CI with a model upon creation and, since there's no model, creates an "Unknown" model? The end result is that our CMDB has thousands of CIs where the Model ID is "Unknown" (refer to screenshot below for examples).

The Model Categories are all set up with an Asset Class of -None-, so no assets are being created -- but why is ServiceNow trying to associate these CIs with Models? Is it possible to prevent this?

If it helps, this started occurring late March/early April of 2015 -- CIs created before that don't have Unknown model IDs -- the Model ID field is simply blank. Is it possible the behavior change is tied to a ServiceNow upgrade?

Thanks for your insight,

Roy