Technical guidance for evaluating and operating ZENQIX.
Start with deployment, connectivity, platform status, remote-support governance and recovery.
Start with the current operating material.
Getting started with a ZENQIX Endpoint evaluation
Plan an evaluation around endpoint facts, deployment constraints, operator roles and written acceptance criteria.
Read documentDeployment architecture and ownership boundaries
Understand the separation between the public website, ZENQIX control plane, operational data, remote support and managed endpoints.
Read documentAgent connectivity and endpoint state
How ZENQIX treats heartbeat, last-seen state, inventory freshness and outbound connectivity in the endpoint record.
Read documentPlatform support and capability status
Read Available, Preview, Planned and Not available consistently across Windows, macOS, Linux and mobile roadmap items.
Read documentRemote support governance
Evaluate remote support as an authorized operational workflow rather than a hidden secondary login or uncontrolled access path.
Read documentBackup, upgrade and rollback discipline
The public operating model for preserving rollback artifacts, database backups, release identity and post-change health checks.
Read documentTroubleshooting principles
A safe public troubleshooting order for endpoint state, product reachability, actions, evidence and remote support.
Read documentOrganized by administrator task.
Getting Started
- Evaluation planning
- Deployment architecture
- Platform and capability status
Endpoint
- Enrollment and identity
- Inventory and endpoint state
- Actions, remote support and evidence
Administration
- Users and roles
- Policies and approvals
- Security and audit boundaries
Agent
- Windows agent
- macOS agent
- Linux agent
- Connectivity and troubleshooting
API
- Authentication
- Devices
- Jobs and results
- Reporting
Operations
- Monitoring
- Backup and restore
- Upgrade and rollback
- Troubleshooting
Short explanations for common endpoint questions.
Documentation follows capability maturity.
Availability labels on docs and feature pages use the same status vocabulary as the capability matrix.
Public guidance is available for the stated scope and current product status.
Documentation describes current implementation scope without implying general availability.
Information architecture is reserved; operating procedures are not published as current capability.
Use the docs to prepare the pilot.
Read the evaluation guide and deployment architecture, then record your acceptance criteria.