Asset vs CI creation for printers discovered via runZero

[fatiha12]

Hello,

I am a junior Configuration Manager, and I am currently facing the following CMDB challenge.

We recently installed several new printers that were not initially created as Assets in ServiceNow. These printers are now being discovered through the runZero connector.

The discovered records have several missing attributes, however I managed to identify one key attribute that allowed me to detect that these printers are not correctly assigned to the territories I manage.

My goal is to:

• First, attach these printers to the correct territory
• Then, complete the missing information

At the moment, I cannot update or enrich these records because they are outside of my managed scope, so correcting the territory assignment is a prerequisite.

This leads me to a broader question regarding best practices for Asset vs CI creation in this situation:

• Should I create the Asset records first, and let the mapping mechanism create or reconcile the CI afterward, knowing that some data may then need to be maintained manually?
• Or should I rely on runZero to create and populate the CI first, then complete the data later — and in that case, how and when should the Asset be created?

In our current configuration, I have rarely seen Assets being automatically created from CIs, which raises a concern.

My main concern is:
Do I risk having to manually create one Asset per printer if I follow the wrong approach?

I would really appreciate your feedback on the recommended approach and lifecycle for printers discovered via runZero in a CMDB/Asset context.

Thank you in advance for your guidance.