The ServiceNow SCCM Integration doesn't Set the Virtual Field on Computer[cmdb_ci_computer] RecordsSummaryThe out-of-box BR 'Virtual Computer Check' (https://INSTANCENAME.service-now.com/nav_to.do?uri=sys_script.do?sys_id=dd6ea51f0a0a0b7800561c3567d869bf) is triggered on insert or update of Computer[cmdb_ci_computer] records. It tries to determine if the Computer record is a Virtual Machine (VM) or not, and if it is sets the 'cmdb_ci_computer.virtual' field to true. This BR has several checks it does to detect different types of VMs (VMWare, Microsoft HyperV and so on). However the Business Rule is part of the feature set for Discovery, and is only written to work with Discovery. This means that when used on Computer records imported by one of the Microsoft SCCM integrations (SCCM 2016, Service Graph SCCM and so on) it may not detect that a computer is a VM. For example the HyperV check relies on records in cmdb_ci_hyper_v_instance, however none of the ServiceNow SCCM integration plugins create or update records in this table, nor do they set the 'virtual' field on Computer records.ReleaseAll current ServiceNow releasesRelated LinksCustomers who need this functionality can raise an Enhancement Request asking for it to be added to the SCCM integration: Idea Management for customer enhancement requests https://hi.service-now.com/kb_view.do?sysparm_article=KB0755878 It might be possible to create a new custom BR, or edit the SCCM Transform Maps, to set the 'virtual' field on records imported by SCCM. We can't provide assistance with customisations, and whether a customisation like that would work depends on there being a field in the data coming from SCCM that lets you easily determine if the computer is a VM or not.