All of this is vendor-reported. The sources reviewed contain no independent customer results, time-saving figures or comparisons with dedicated asset-management tools.
The gap Hexnode says it is closing
An enrolled-device record only covers part of what IT is responsible for. Hexnode's own material says monitors, accessories, loan equipment and other workplace assets also need assignment histories, maintenance records and eventual recovery or disposal.
Hexnode CTO Sahad M put it this way: a device can be correctly configured while the record of who holds it, what goes with it and when it should come back stays incomplete. That is the company's rationale, not independent evidence of demand. It is still a familiar problem. Many IT teams keep this information in spreadsheets, and Hexnode explicitly pitches the module as reducing reliance on them.
How the inventory model works
Hexnode's help documentation splits physical inventory into four types. The split matters, because it decides how much record-keeping each item gets.
| Inventory type | What it holds | Examples given |
|---|---|---|
| All Assets | Individually tracked items, each with its own lifecycle record | Laptops, monitors |
| Pools | Identical, non-serialized items tracked by quantity | Keyboards, cables, headsets |
| Kits | Related items grouped into one assignable bundle | A monitor and keyboard with a workstation |
| Detected Assets | Peripherals seen on managed devices, awaiting review | Connected peripherals |
Hexnode's guide says an asset record can hold identity, hardware, purchase and financial details, warranty data, attachments, maintenance records, lifecycle information, contracts and connection history. Kits can be defined either from specific asset records or from a type template, such as one monitor and one keyboard. Pools can be marked as returnable or consumable, and returnable items carry an expected return date.
The console path is Manage > Assets. Its sections are Dashboard, All Assets, Detected Assets, Pools, Kits, Audits and Settings. Settings covers custom asset types, custom fields, a Building → Floor → Room location hierarchy and asset-ID preferences.
Detection is not automatic registration
The announcement says connected peripherals are detected automatically for administrator review and registration. The support guide is more precise. Detection gives visibility without adding every peripheral to tracked inventory. An administrator reviews each detected item and uses a Register as Asset action to bring it into All Assets. Bulk registration is also supported. Discovery is automatic, but inventory is still an administrator's decision. That is probably the right design, since you don't want every USB dongle that ever touched a laptop becoming a managed asset.
Assignments, offboarding and lifecycle records
Hexnode lists these assignment and lifecycle features:
- Bundles and loans. Equipment bundles can be assigned to users, with checkout records and return deadlines.
- Directory linkage. User directory integration ties assets to employee profiles, so offboarding can show what must come back. The sources don't say which directory providers the asset module supports.
- Financial records. The module holds purchase, vendor, warranty and contract details. It also calculates depreciation and book value automatically. The sources don't say how depreciation is configured or which accounting methods are used.
- Maintenance and disposal. Teams can schedule maintenance and document disposal. Disposal certificates are generated automatically.
- Dashboard. It shows asset counts, status breakdowns, recent activity, overdue pool checkouts and warranty alerts.
Physical audits
Hexnode's audits are QR-based, with telemetry pre-scans and guided workflows for reconciling assignment or location discrepancies. The help guide adds that an audit can cover IT assets, non-IT assets or pools. Its scope can be all assets, one location or one asset type.
Each item is marked Found, Not Found or Misplaced. For a misplaced item, the actual location can be recorded. The audit then produces a summary with a pass rate and a Discrepancy Report of missing and misplaced items. Hexnode also says the console has 16 or more reports for this feature.
Plan requirement and role scoping
Two practical boundaries stand out:
- Plan. The asset management function is available to customers on Hexnode's Enterprise plan and above. The sources give no pricing for the module, so smaller customers should confirm entitlement before planning around it.
- Least privilege. Inventory staff can be given access through an Asset-Only Technician role without broader permissions over endpoint policies. This lets a stockroom or helpdesk employee manage equipment records without being able to change device policy. The sources don't give plan-specific technician limits.
Remote BIOS management for Windows PCs
For Windows administrators, the more technical part of the release is remote firmware control. Hexnode says it covers boot-order configuration and firmware password controls on supported Windows PCs. The stated use cases are preparing machines for network imaging, changing passwords after staffing changes and clearing credentials before resale.
Support differs by vendor, and sources conflict
Hexnode's own materials disagree slightly on which brands are covered. The Hexnode release-notes post from November 6, 2026 says BIOS password actions (set, change, clear) are supported on ASUS, HP, Dell and Lenovo devices. The November 17 announcement summary lists only HP, Dell and Lenovo for BIOS password actions. Check current Hexnode documentation for your hardware before relying on ASUS support.
The pre-boot system password is narrower still, according to the release-notes post:
- Set System Password: Dell only.
- Change or Clear System Password: Dell and Lenovo.
The compatibility detail I found concerns passwords. I found no source that states which brands support boot-order configuration, so don't assume the password list applies to it.
Where to find it and what it protects against
According to Hexnode's help page, the actions are under Actions > Security for a selected Windows device. Configured credentials can be viewed in masked form under Manage > Devices > the device > Device Info > Device Status Info. Several safeguards are described:
- Changing or clearing a credential requires entering the active password first, which is meant to prevent lockouts.
- Leading and trailing spaces are trimmed from password inputs to avoid lockouts caused by invisible characters.
- Success can be checked in Action History on the device summary page.
- The status section only shows credentials set or changed through the Hexnode console. A password changed directly on the machine won't appear there.
That last point is a real caveat for fleets where technicians still touch firmware by hand. The console's view may not match what is on the device.
This is also a shift from earlier Hexnode guidance. One of its hardware-refresh workflow pages describes deploying OEM-specific custom scripts, for example via PowerShell, to randomize UEFI passwords on Windows. A native action should be easier to audit than scripts, but only on supported models.
Android shared-device policies
The Android addition is aimed at frontline and shift-based work, where one handset or tablet is passed between people. It offers individual sign-ins and automatic logout. Some apps can stay available without sign-in, while others require authentication.
The November 6 release-notes post gives more detail. Sign-in can use Active Directory, Google Workspace, Okta or Microsoft Entra ID. Access can be open to all users or limited to selected groups. Logout intervals can include warning prompts. An "Unassigned Mode" decides which apps remain reachable when nobody is signed in.
What to weigh before adopting it
- Consolidation is the draw. Linking assets to users and managed devices in one console avoids reconciling separate systems. Dedicated ITAM suites may go deeper on procurement, contracts or accounting, and the sources don't compare them.
- Check the plan first. The Enterprise-and-above requirement is the first practical test.
- Plan for review work. Detected peripherals need a person to register them.
- Verify BIOS support per model. Test on your own hardware and confirm current vendor coverage, given the ASUS discrepancy.
- Don't expect console visibility of manual firmware changes. Device Status Info only shows what was set through Hexnode.
Hexnode isn't alone in pushing UEM platforms toward asset and lifecycle tracking. The pitch is that the endpoint console is already where users and devices are known, so it can also hold the records of what was handed out. Whether Hexnode's version replaces a dedicated tool will depend on how much finance, procurement and reporting depth a team needs. The sources reviewed don't answer that.
References
- Hexnode adds native asset management to UEM platform - ChannelLife UK ChannelLife UK · 2026-11-19T16:15:00+00:00
- Hexnode Adds Native IT Asset Management to its UEM Platform hexnode.com
- IT Asset Management (ITAM) with UEM | Hexnode Feature Guide hexnode.com