1
Asset records and ownership
Assets combine manually managed lifecycle data with agent-observed device identity. Owners and admins can maintain assignment, location, department, status and support notes.
- Use assignment fields for accountable ownership, not informal naming conventions.
- Review the asset activity trail when identity or ownership changes.
- Use the Windows confirmation prompt when the signed-in user should verify assignment details.
2
Inventory snapshots
Enrolled agents send structured inventory in versioned snapshots. Ordantra presents categories independently so unavailable data does not hide the rest of the device.
- System, compute, storage, network and security posture
- Update state, services and privacy-controlled local account context
- Installed software and optional privacy-preserving usage signals
3
History and relationships
Inventory history lets resolvers compare what the endpoint reported over time. Link the asset to tickets, risks and changes so technical state stays connected to service work.
- Use software history to distinguish current and removed applications.
- Use graph relationships to inspect nearby work and dependencies.
- Keep risk remediation and change validation linked to the affected asset.