Inventory Data and Audit Conflicts
On this page
Alloy Navigator imports inventory data from two sources: AlloyScan and Alloy Discovery. Each import runs as a job on the Automation Server. Setting up the AlloyScan import is covered in AlloyScan Synchronization, and the Alloy Discovery import in Alloy Discovery Synchronization. Each run is logged with its statistics, such as the computers and hardware it created, and an administrator reads that log in the Settings App. The result of a run is also visible in the records it wrote; see Inventory data in the Web App.
What an import writes to a record
An import does not write object fields directly. For each class it runs a service action, one for new records and, except for persons, one for existing records, and the action's field mapping decides which fields an audit fills in. The mapping is part of the configuration, so the set of fields that arrive depends on how the actions are mapped. An AlloyScan import also adds the audit date to the mapped fields. An administrator chooses the actions and mappings when setting up synchronization.
- An AlloyScan import creates and updates computers and hardware from the corresponding device lists returned by the AlloyScan site.
- An Alloy Discovery import creates and updates computers, hardware, and Chromebooks, which it records as computers, and can create a person for a computer user it cannot match.
The service actions of the Default Workflow, and what they set on a new computer, are listed in In the Default Workflow.
An AlloyScan run reads only the devices audited after the newest audit date that the previous successful run saw, so after a run that fails part-way, the next run reads the same devices again. When no run has recorded that date yet, or no computer holds an AlloyScan audit yet, the run reads every device on the site. When the job is set to delete the AlloyScan records of devices retired in Alloy Navigator (see Retiring a device), the run does so before it imports anything, so such a device is removed from the site in the same run that would otherwise import it again.
An AlloyScan import replaces a serial number that is a known placeholder
value, such as To Be Filled By O.E.M., N/A, or Default string, with an
empty value before matching records or checking audit conflicts. A serial
number mapped from another attribute is kept as received.
Both imports compare the number of audited computers with the licensed node count:
- AlloyScan checks before its computer import and again before each computer. At the limit, it skips new computers with a warning that the limit is reached; above the limit, it stops the computer import with a warning that the limit is exceeded. Its hardware import does not check the limit.
- Alloy Discovery checks each computer or Chromebook just before its service action runs. Above the limit, or at the limit for a new device, the device fails with an error that is logged, and the run moves on to the next device.
How AlloyScan finds an existing record
- A computer is matched to the computer that AlloyScan imported earlier for the same audit or, for a device migrated from Alloy Discovery, to the computer whose audit ID is the one AlloyScan reports as the device's legacy audit ID. Only when neither exists does AlloyScan try the conflict resolution rules; see Audit Conflict Policy.
- Hardware is matched to the hardware that AlloyScan imported earlier, then by serial number, then by name, each ignoring case; the first match wins. No rules are used for hardware.
- A device matched this way whose stored audit date is not older than the incoming audit is skipped in that run. For a computer, this check applies only when the computer was matched in one of the two ways above, by its earlier import or by its legacy audit ID, not when a rule matched it.
- A matched computer or hardware item that is retired is logged and left unchanged.
Discovered software
When AlloyScan imports a computer, the installed software arrives with the computer's audit. Unknown products, manufacturers, and platforms are added to the software catalog, and the computer's discovered software is then brought in line with the audit: changed rows are updated, rows no longer detected are deleted, and new rows are inserted. After that, the computer's license allocations are recalculated; how automatic allocation picks a license is in Allocate Software Licenses. Product name, version, publisher, install key, and serial number are shortened to fit their fields.
The AlloyScan job also controls which platforms have their software imported:
- For all platforms: software is imported for Windows, Linux, and macOS computers.
- For selected platforms only: software is imported for the chosen platforms. A computer on any other platform has its discovered software cleared.
- Do not import software: AlloyScan is asked to return no software, and an imported computer has its discovered software cleared.
AlloyScan imports software only for its Windows, Linux, and Mac computer types. As the setting itself notes, only software from groups marked for tracking can be imported.
The software catalog's platform for Mac computers is named macOS. On a database upgraded from an earlier version, the platform named Macintosh is renamed macOS. If that platform had been given another name in your database, it keeps that name, and the first AlloyScan import of Mac software adds a second platform named macOS.
Alloy Discovery updates the discovered software of each computer it imports, except a Chromebook, and also refreshes the discovered software of computers it imported earlier. A Chromebook imported from Alloy Discovery has no discovered software written by the import. Neither import writes discovered software for a hardware item.
Alloy Discovery recalculates license allocations only for the computers it imports. A Chromebook or a hardware item that it imports gets no license allocation from the import. How automatic allocation matches a hardware item is in Allocate Software Licenses.
Alloy Discovery synchronizes its software catalog with Alloy Navigator. It adds missing manufacturers, platforms, software product groups, and categories, and updates group names and ignored settings and category names where they differ. It adds products whose source software group is unspecified or marked for synchronization and updates matching products when newer source data is available. Products are matched by name, version, and manufacturer, so a product renamed in Alloy Discovery arrives as a second product. This catalog synchronization does not delete products; unused products are removed in the cleanup described below.
At the end of each AlloyScan or Alloy Discovery run, every product in the software catalog that no discovered installation refers to and that is not tracked is removed from the catalog, including a product that AlloyScan or an administrator added. In an Alloy Discovery run, a failure of this step is written to the session log and counted as an error, and the run still finishes.
What discovered software means for licenses is covered in License Compliance.
Audit conflicts
Only Alloy Discovery raises audit conflicts; AlloyScan never does.
For each audited computer or Chromebook, Alloy Discovery first looks for a computer already linked to the device's Alloy Discovery record. A retired computer found this way is logged and skipped. Any other linked computer is updated, unless its stored audit date is not older than the incoming audit. When no computer is linked, the conflict resolution rules are tried in rank order until one fires. A rule's conditions are all required: a rule matches only a computer that meets every one of them. Retired computers are never matched by a rule.
- An Overwrite rule that matches exactly one computer updates that computer. More than one match is an error for the device.
- A Manual rule that matches raises a conflict for an administrator, and the device is quarantined.
A raised conflict records the incoming and the stored values of the computer name, the MAC address, and the serial number side by side, for the first existing computer the rule matched. A conflict has one of four statuses: New, Scheduled, Resolved, or Error. A conflict is New when it is raised. No import run and no resolution sets a conflict to Error.
An administrator resolves a New conflict by choosing either to create a new computer from the audit or to overwrite the existing computer with the audit. The choice sets the conflict to Scheduled and allows no further editing. The next Alloy Discovery run applies it and sets the conflict to Resolved. The choice is never applied at the moment it is made.
Conflicts are resolved in the Settings App, from the conflict list of the Alloy Discovery Connector manager in the Conflict Details window, or in the Admin Center, on the Conflict List tab. Both procedures, and the rules that decide when a conflict is raised, are in Audit Conflict Policy.
Inventory data in the Web App
Find imported records
In the Web App, imported computers are listed under the Configuration Management entry Computers, and imported hardware under Hardware. A Chromebook imported from Alloy Discovery is a computer record, so it is listed under Computers and in All CIs.
Inventory data on the Computer and Hardware forms
In the default Computer form, the Configuration tab follows General and Activity. It holds the groups Operating System, CPU, HDD & RAM, Virtualization, Network, User Activity, Audit Information, Display, and IP Addresses. The Audit Information group holds the audit date and the Show audit information button. The Virtual Machines and Software tabs follow the Configuration tab, and Software holds two tabs, Discovered Installations and Allocated Licenses.
The default Hardware form also has a Configuration tab, which holds the network, the audit date, and the IP Addresses list.
Open a computer's audit
The Computer form's Show audit information button opens the audit behind the computer's data.
- For a computer audited by AlloyScan, the button opens the device's audit in the AlloyScan audit viewer, in a new browser tab.
- Where the computer's stored audit holds only a link to the device, the button opens that link.
- When the computer has no stored audit link, as for a computer imported from
Alloy Discovery, the button downloads the computer's audit as a file named
<computer name>_<GUID>.adt.
The Web App does not open a downloaded .adt file. The Alloy Audit Snapshot
Viewer, which ships in the separate Alloy Audit Tools package, opens it:
Open the downloaded file with Alloy Audit Snapshot Viewer. If Windows does
not open .adt files in the viewer, associate the file type with it in
Windows, or start the viewer and select the file in Open Audit Snapshot.
The dialog lists .adt and .adtx files.
In the Default Workflow
A new database created with the Default Workflow (see Default Workflow Configuration) contains the service actions and conflict resolution rules below. It contains no AlloyScan or Alloy Discovery job: an import runs only after an administrator has created its job. An upgraded database need not contain the actions and rules, and an administrator may have changed or replaced them.
The supplied service actions, by the job slot each is for:
| Import | Records | For new records | For existing records |
|---|---|---|---|
| AlloyScan | Computers | New Computer (AlloyScan) | Update Computer (AlloyScan) |
| AlloyScan | Hardware | New Hardware (AlloyScan) | Update Hardware (AlloyScan) |
| Alloy Discovery | Computers | New Computer (Alloy Discovery Connector) | Update Computer (Alloy Discovery Connector) |
| Alloy Discovery | Hardware | New Hardware (Alloy Discovery Connector) | Update Hardware (Alloy Discovery Connector) |
| Alloy Discovery | Chromebooks | New Chromebook (Alloy Discovery Connector) | Update Chromebook (Alloy Discovery Connector) |
| Alloy Discovery | Unmatched computer users | New Person (Alloy Discovery Connector) | - |
A computer created by New Computer (AlloyScan) or New Computer (Alloy Discovery Connector):
- has its status set to Auto-Added;
- gets the activity "Computer was auto-added" and the activity "New Computer created via AlloyScan" or "New Computer created via Alloy Discovery Connector";
- gets an associated asset, with its status set to Deployed, its type to Unspecified, its quantity to 1, and its received date to the time it is created, unless the computer is marked as a virtual machine. A computer marked as a virtual machine gets the category Virtual Host instead, and no asset.
The actions start with the type Unspecified and can set the computer's type from its inventory data. The AlloyScan action can also set a category from the device type and subtype.
A Chromebook created by New Chromebook (Alloy Discovery Connector) is a computer with its category set to Chromebook, its type to Workstation, and its status to Auto-Added. It gets the activities "Computer was auto-added" and "New Chromebook created via Alloy Discovery Connector", and it always gets an associated asset.
The supplied conflict resolution rules, in rank order:
| Rule | Action | Conditions |
|---|---|---|
| Audit_ID is checked for computer duplicates | Overwrite | The audit ID equals. |
| Automatically overwrite duplicates when Serial Number and Computer Name match | Overwrite | The computer name equals and the serial number equals. |
| Automatically overwrite when Serial Numbers matches | Overwrite | The serial number matches. |
| Computer Name is checked for computer duplicates | Manual | The computer name matches. |
AlloyScan uses only the second and the third of them. What the operators mean is in Audit Conflict Policy.
In such a database, the platform status that marks a computer or hardware item as inactive is labeled Retired. Wherever this topic says retired, it means that status, whatever its label.
Related topics
- AlloyScan Synchronization - set up and run the AlloyScan import.
- Alloy Discovery Synchronization - set up and run the Alloy Discovery import.
- Audit Conflict Policy - conflict resolution rules and resolving raised conflicts.
- License Compliance - how discovered software counts toward license compliance.
- Allocate Software Licenses
- Default Workflow Configuration - the configuration a new database is created with.