Skip to main content
If a system answers during a scan but cannot be assigned to a type, it lands in this list instead of the inventory. It is the step between a find and an asset: every entry is either assigned a type or removed. On the dashboard, the Unknown Systems metric with the line Typing pending leads straight here.

​
Information per entry

Details opens a display-only sidebar with four fields for each row: Missing values appear as a dash.

​
Editing entries in bulk

Select several rows through the checkboxes and choose Edit Systems: the sidebar opens a form whose activated fields apply to every selected entry. Whatever you do not explicitly activate stays unchanged.
Name and IP address cannot be set here — both are excluded from bulk editing because they differ per system. Only shared entries are assigned: type, environment data and similar fields.
Review a few entries through Details first—often a pattern shows up, an address range or a device class. Then edit by that pattern instead of row by row.
Delete removes the selected entries for good, after a confirmation.
A deleted entry cannot be restored. Delete only what you were actually able to classify, or what demonstrably does not belong to your environment.

​
What the list does not show

Two things are deliberately missing here:
  • The job that made the find. There is no direct reference; through Detected On and the IP address, though, a find can be narrowed down against the execution history and the targets of your jobs.
  • A direct type assignment per row. This page does not assign a single system to a type; only bulk editing does that.
If a whole address range stays unknown, the cause usually lies with access, not with this list: a target that answers but cannot be signed in to delivers too little for a classification. Check the credentials of the job concerned and its Last Scan Details.
Docusnap365 carries assigned systems as an asset from then on—it continues with capturing ITAM data.