Moving Assets from Hardware Model Categories

[adamrauh]

Hi All,

I'm starting the process of cleaning up/moving our ITAM to Servicenow, however I'm running into a few issues - one being that when we implemented SN, we did so importing some ITAM information from SCCM.   This was great because it populated CI's, but bad b/c variations in data imported from SCCM ahs created multiple Hardware Model categories for the same items.

For ex,

For a 'Dell E7240' laptop model, I have 2 entries:

Dell E7240: [no manufacturer]

Dell E7240: Dell Inc. [manufacturer]

I would like to combine these categories, and set it so that anything new that comes in 'Dell E7240...' ish doesn't create a new model category, but goes to the one I created.   I read where I can delete the model category I don't want, which is fine, but I as the field is set in the Asset/CI form I don't see how I could just change the categories for the associated assets/CI's until it's down to 0, and then delete - so barring manually creating these again in the correct category I'm not sure the best way to tackle this.

Any ideas?

[Jacob_Andersen]

Adam,

Do you mean to say that it creates new Hardware models?   That will happen, but it will not create new model categories.   If you will confirm this, let's start the discussion from there.

[adamrauh]

Correct - see example:

[adamrauh]

Hi Jacob -

Was wondering if you had had a chance to check my above screenshot.   I'm not sure how to best clean up this data so we can take the multiple model's and move them into one.

[Jacob_Andersen · Accepted solution]

Adam,

The image did not come through, but I do see your reply.   There is a alm_asset.model read ACL that applies to these records.   I'd modify this to make it so that admins can change this field.   Then go and clean up all of your hardware models and point your HW assets to the correct models.

A word of caution.   When a new HW asset is created, SN will not look at your existing custom-made HW models and choose one.   Rather, it will create its own.   If you have a clean HW model list and you update all of your records to use the model that you wish, they will work just fine during updates in the future.   You will want to check the new records to make sure that you're happy with what the system created/used for you.

Please mark this as the answer to your question if I've given the correct answer.