Software deployment
Prepare software install, remove and upgrade workflows that verify the resulting software state instead of trusting installer output alone.
What the administrator needs to solve.
Large fleets make manual installation slow, while blind automation can spread a bad package quickly. An installer returning success is not enough evidence.
How ZENQIX handles it.
ZENQIX models software changes as precheck → integrity validation → execution → inventory refresh → observed-version verification.
Requested action and verified outcome stay separate.
What is currently in scope.
Install action model
Uninstall action model
Upgrade action model
Checksum metadata
Compliant-state no-op behavior
Post-action verification model
Availability by operating system.
Physical package execution QA pending.
Physical package execution QA pending.
Physical package execution QA pending.
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
- • Checksum validation where policy requires it
- • No arbitrary executable URL execution without policy
- • Structured process invocation
- • Controlled temporary paths
Evidence
- • Previous observed version
- • Requested package/version
- • Integrity result
- • Execution result
- • Observed post-action version
Technical detail
- • Status remains Preview until provider-specific physical QA is complete
Technical questions for this capability.
Is software deployment generally available today?
No. The control-plane and verification architecture are in Preview while provider-specific physical QA continues.
What does ZENQIX verify?
The intended model re-reads endpoint software state after execution and compares the observation with the requested outcome.
Evaluate software deployment in your environment.
Use the capability matrix and the written acceptance checklist to confirm whether the current status matches your pilot needs.