The hardware assets are created automatically when you create the hardware CI. There is a business rule that handles this creation, as well as synchronization of common/related attributes. The creation of the asset is determined based on the Model you choose for the CI. If the model's asset tracking strategy is to defer to the Model Category, then you will get an asset as long as the model category of that model defines an asset class. If you want to skip the creation of assets for a specific model (say a VMWare virtual server model for example), then go to that Model record and change its asset tracking strategy to "Don't create assets". Otherwise you should have an asset record created for every CI that is discovered. You can also tell ServiceNow to defer the creation of assets for an entire model category which would require someone to manually trigger asset creation on a case by case basis, but managing that process consistently requires a lot more care and feeding and is prone to error, so I typically do not recommend this approach unless you have a very mature asset management program in place and clear business requirements to justify the additional processing.
The opinions expressed here are the opinions of the author, and are not endorsed by ServiceNow or any other employer, company, or entity.
