Device management
Create a dependable operational record for each managed endpoint: identity, state, site context and recent activity.
What the administrator needs to solve.
IT teams lose time when device identity, ownership, network context and status are split across spreadsheets and tools. A hostname alone is not enough to operate a distributed fleet.
How ZENQIX handles it.
ZENQIX maintains an endpoint record around stable identity and recent evidence so an administrator can answer what the device is, where it belongs, who is using it and when it last checked in.
Requested action and verified outcome stay separate.
What is currently in scope.
Stable device identity
Assigned site context
Online/offline state
Last-seen timestamp
Logged-in user where supported
Operating-system and architecture context
Search and filtering
Availability by operating system.
Validated in the current private-pilot path.
Agent builds and isolated testing are available; physical acceptance is still staged.
Agent builds and isolated testing are available; physical acceptance is still staged.
Inspect the state the UI needs to expose.
This panel uses synthetic data. A genuine ZENQIX Endpoint screen can replace it only after sanitization and publication approval.
Security
- • Outbound-first endpoint connectivity
- • Controlled enrollment
- • Device identity separated from shared bootstrap material
- • Role-aware administrative access
Evidence
- • Registration time
- • Last heartbeat
- • Observed platform facts
- • Site assignment
- • State changes over time
Technical detail
- • Central control plane with agent-reported state
- • Server timestamps stored consistently
- • Public website demo remains synthetic and separate from customer environments
Technical questions for this capability.
Does ZENQIX expose managed endpoints directly to the Internet?
The product direction is outbound-first. Managed endpoints should not require unnecessary inbound exposure for routine control-plane communication.
Is a missed heartbeat immediately treated as offline?
No. Operational status should use a defined tolerance so normal network jitter or sleep does not create false alarms.
Evaluate device management in your environment.
Use the capability matrix and the written acceptance checklist to confirm whether the current status matches your pilot needs.