IT asset management and inventory
Know what you own, who uses it and whether it is up to date. The Scout agent inventories workstations, the machine agent can add servers, and imports cover the assets no agent can reach, all in one estate with the same permissions as the rest of VerOps.
- Agent
- Scout, for Windows and Linux
- Enrolment
- Expiring token, per-device key
- Directory
- Microsoft Entra ID or CSV
- Reports
- CSV or PDF, on a schedule
What Scout reports
Hardware
Manufacturer, model, serial number, BIOS version and chassis type; CPU, cores, memory, disks and GPUs; network interfaces, gateway and Wi-Fi network.
Installed software
Installed packages and the executables that actually run, normalised into products so twelve executables become one product.
DocumentationUsers and devices
Who is signed in to each device, the history of which user had which device, and directory details from Microsoft Entra ID or a CSV file.
DocumentationPatch posture
Each device is placed in a current, behind, critical or unknown bucket using thresholds the documentation states exactly.
DocumentationOffice or remote
Devices are classified as office, remote or unknown against your trusted office networks (by SSID, BSSID or IP range), with history kept from daily to yearly.
DocumentationSoftware activity
Which applications are actually used and for how long, measured by foreground, CPU and network activity rather than by an open window.
Learn more
Running the estate
Identity that survives change
A device keeps its asset record and history through renames and re-images.
DocumentationServers too
The machine agent’s optional inventory module reports servers into the same estate.
DocumentationImport the rest
Load assets no agent can reach from CSV or through the API, matched by asset tag, serial number or hostname.
DocumentationFinancials and warranty
Purchase cost, warranty end dates with expiry warnings, and straight-line depreciation with book value worked out on read.
DocumentationCentral configuration
Agents, groups and rulesets decide what each group of devices collects and how often, from one place.
DocumentationOpt-in self-update
Scout can update itself from a release channel once you turn it on. It is off by default.
Documentation
Reports
Reports are built from the same queries as the on-screen tables. Download them as CSV or PDF, or email them to members of your organisation daily, weekly or monthly.
| Report | Answers |
|---|---|
| Hosts inventory | What devices exist, with hardware, OS and presence |
| Licence position | Entitled versus consumed, per licence |
| True-up | What to buy or drop before a renewal |
| Patch posture | Which devices are behind, and by how much |
| Financials summary | Cost, book value and warranty status |
| Software usage | Which products are used, and how much |
| Host presence | Hours in the office and remote, per device |
Rolling it out
- 01
Import what you know
Start with a CSV of the assets you already track, so agents attach to existing records.
- 02
Deploy Scout
Download a preconfigured Windows installer from Inventory, then Agents, then Deploy Scout, or use the Linux package. Each installer enrols with a limited-use, expiring token.
- 03
Curate and report
Review newly discovered software, set licences and office networks, then schedule the reports people need.
Limits worth knowing
- Scout runs on Windows and Linux. macOS is not supported.
- Directory sources are Microsoft Entra ID and CSV. On-premises Active Directory over LDAP is not supported.
- There is no native MDM connector. Mobile device records can be pushed in through the inventory API.
- Focused (foreground) activity and per-process bandwidth are measured on Windows. On Linux, activity comes from CPU and network use.
Read more in the docs
Try it on your own systems
Create a workspace, or tell us about your environment and we will walk you through it.