IT Asset Management

What VerOps IT Asset Management is: agents feed one governed estate, the platform resolves it into asset intelligence, and dashboards, alerts and scheduled reports turn it into decisions.

Put VerOps Scout on a workstation: the preconfigured installer from Inventory → Agents → Deploy Scout (recommended), the generic Windows installer, the Linux tarball, or the Machine Agent's inventory module for servers — then verify the machine is enrolled and reporting.

Asset identity that survives renames and re-images, hosts versus MDM devices, agent versus imported origin, the active/stale/retired lifecycle, the asset detail page, and the timeline of history events.

Historical user↔device associations and the current user, plus directory enrichment — Entra ID app-only setup requirements, the CSV fallback, and exactly when an ambiguous match goes to review instead of being guessed.

How VerOps classifies devices as office, remote or unknown against trusted office networks (SSID/BSSID, CIDR, gateway MAC) — and why presence is network-inferred and never a guarantee of physical presence.

Normalization from executables and packages into products, the contains/exact/regex matching rules and their precedence, the review queue, and product merge — including why a merge without a rule does not stick.

Entitlement lines, exactly how per_device, per_user, per_core and site consumption are counted, the four compliance positions, true-up with cost-to-cure, daily position snapshots and the single-currency rule.

Purchase and warranty records, straight-line depreciation with book value computed on read, warranty expiry alerts at the 90- and 30-day marks, the single-currency rule, and bulk loading by CSV.

Load the assets no agent can reach: header auto-mapping, the asset_tag → serial → hostname match precedence, dry runs that provably change nothing, the agent-facts-always-win rule, and the enrollment merge.

The current/behind/critical/unknown buckets and the exact thresholds behind them, the manual OS build catalog, why unknown means an agent without the module, and the fleet-level alerting threshold.

Six report types rendered from the same queries as the on-screen tables, as CSV or PDF, on daily/weekly/monthly schedules, delivered as a download link with at-most-once-per-window guarantees.

The rollout order that saves the most work — import first, then agents — plus preconfigured per-tenant installers, enrollment tokens, central policy, coverage checks, and retirement with credential revocation.