How to update attributes of the Computer configuration item

Overview

The Generic inventory provider workflow (server workflow) uses the new Import Assets activity that imports devices into Matrix42 Enterprise Service Management. This article explains which data definitions of the Computer configuration item can be updated this way. All attributes are updated with each next import.

General rules for the successful import of attributes

1. If you import an attribute whose value is a relation to another entity, the value must be provided as a GUID. Only hosts, users, and domains are matched by a name as specified below.
2. When importing values for attributes that refer to other entities (tables), make sure that these values are present in the database. Otherwise, the import will fail.
3. Always check the expected data type for imported values.

Mandatory data definitions of the Computer configuration item that can be updated

The Generic Inventory data provider can update attributes of the following mandatory data definitions of the Computer configuration item:

• SPSAssetClassBase 
• SPSAssetClassMobile
• SPSCommonClassBase
• SPSCommonClassLdap 
• SPSComputerClassAD 

Relation to domain is saved as GUID in the database, but a domain name must be used as source data. The workflow will match it to existing domains.

• SPSComputerClassBase

Relation to host is saved as GUID in the database, but a host name must be used as source data. The workflow will match it to existing computers.

• SPSComputerClassOS
• SPSInventoryClassBase
• SPSInventoryClassNetSupport

Relation to SKU

The SPSStockKeepingUnitClassBase data definition can also be updated although it is not a part of the Computer configuration item.

You can import an SKU value for a computer. The matching is done by ManufacturerName in SPSAssetClassBase and Model in SPSStockKeepingUnitClassBase. If no match is found, a new stock keeping unit is created.

Relation to user

A principal user can be set for imported devices if the user is found in the ESM system. The matching is done by the UserPrincipalName attribute in the SPSAccountClassAD data definition. This attribute is set when the Azure Active Directory data provider imports Azure accounts.

The following priority of matching is used:

1. If the imported user principal name matches the UserPrincipalName attribute in the SPSAccountClassAD data definition of an account and this is a primary account for a person, this person is set as a principal user.
2. If the imported user principal name matches the UserPrincipalName attribute in the SPSAccountClassAD data definition of an account and this account is assigned to a person, this person is set as a principal user.

Multifragments of the Computer CI that can also be updated

• ASMDatacenterClassInventoryResult 
• SPSAssetClassScanLog 
• SPSComputerClassApplicationUsage

After importing data into this data definition, the system will create local application usage tracking records if the local application usage tracking has been configured for specific devices.

• SPSComputerClassDiskPartition
• SPSComputerClassGraphicCard
• SPSComputerClassHardDisk
• SPSComputerClassHostHistory
• SPSComputerClassLogon

Relation to LoggedAccountName is saved as GUID in the database, but a login account must be used as source data. The workflow will match it to accounts. The User Logins grid is never overwritten and only new records are added to it.

• SPSComputerClassMemoryModule
• SPSComputerClassModem
• SPSComputerClassNetworkCard
• SPSComputerClassOpticalDrive
• SPSComputerClassProcessor
• SPSComputerClassSoundCard
• SPSConnectorManagementTypeClassBase 
• SPSInventoryClassApplication

Matching to existing fingerprints is done by Name, Manufacturer and Version. If such a fingerprint is not found, a new record is created. The Installed Applications grid is never overwritten and only new records are added to it.

If OS name, version and manufacturer have been imported into the SPSComputerClassOS data definition, the data provider will also create a fingerprint for the OS.