Hardware assets

The Hardware tab on Assets lists every device from every connected source. Changes here, such as exclusions, source priority and bulk edits, apply to the data every app reads.

The Hardware view opens with two charts and a device table.

• Records by Vendor shows how many devices you have from each manufacturer, such as HP, Dell or VMware. Use it to see what your estate is made of, and to spot records with no manufacturer, which show as Unknown.
• Records by Source shows how many devices each data source contributed, such as SCCM Queries, SIM - Template, Lansweeper Cloud or NinjaOne. Use it to confirm an integration or upload is delivering data, and to see which sources most of your devices come from.

The table lists one device per row. Its default columns are Device Name, Device Type, Manufacturer, Operating System, Model, CPU Model, Total Number Of Cores, Total Number Of Processors, Serial Number and Sources, the data sources that reported the device.

Click the arrow at the start of a row to see more about the device. Each source that reported it is listed with the device’s name and type in that source, and when the data was received.

Click the ⋮ at the end of a row to open its menu:

• Edit changes the device’s details.
• Exclude takes the device out of analysis.

An excluded device stays in Assets but moves to the Excluded Hardware table, under the main Hardware table, and is no longer passed to the applications.

To exclude devices by rule rather than one at a time, use Device Exclusions. Excluded devices remain visible in Assets but are never passed to SIM, MDM, OJDM, RDM or IFMP.

Rules match against the device business key: the device identifier as it appears in the source data.

To add rules:

1. Click Device Exclusions.
2. Select a match type.
3. Enter the business key or pattern.
4. Click Add Rule. Repeat for additional rules.
5. Click Save.

Rules are evaluated against all current and future records. Removing a rule restores the matched devices to the pipelines on the next analysis run.

When the same device is reported by more than one source, Source Priority decides which source’s values are used, for the device record and for its software data points.

1. Click Source Priority.
2. Drag the sources into order, highest priority first. Where two sources disagree, the higher one wins.
3. Click Save.

Source Priority applies to hardware and software data in the project. A typical order puts authoritative agent-based sources (SCCM, NinjaOne, BigFix) above manually maintained templates, so that a template upload can’t override live discovery data unless you intend it to.

You can change hardware data in bulk by downloading a template, editing it and uploading it again. Licenseware keeps track of your changes and applies them on top of the data from your sources. Use it, for example, to:

• standardize vendor names, so Dell Inc. and Dell count as one manufacturer
• apply a naming convention to device names
• add devices that no integration reports, or correct other attributes

How uploaded records rank against other sources is set by Source Priority.

Discovery often reports a generic SQL Server edition, or reports Developer or Evaluation as a paid edition. The SQL edition file has three required columns:

One row per device. A host with several instances of different editions is not one row.

Hardware files go through Assets, then the Hardware tab. The toolbar is Download Template, Upload, Device Exclusions and Source Priority.

The SQL edition file is still uploaded in the app. Keep the column rules above.

Rejected rows are on the History tab. The file needs these columns:

A separate file excludes devices that are already covered, for example disaster-recovery and failover rights, or user-based entitlements such as MSDN and Visual Studio on development and test machines. The file is a CSV with three columns, all required:

This exclusion file is still uploaded in the app. Keep the three columns above.

Device names have to match the discovery record, including the way they are spelled.