VMware ESXi
ESXi 8.0 or later
OVA · 1.59 GB
VMware hardware version 20. Existing OVA passed 47 checks and cold boots in Workstation 17. Native ESXi validation is pending.
Choose your virtual platform, import, and start your 30-day trial.
A ready-to-run appliance with HTTPS management, a setup console and preinstalled monitoring services. Every fresh import generates its own identity and administrator login.
ESXi 8.0 or later
OVA · 1.59 GB
VMware hardware version 20. Existing OVA passed 47 checks and cold boots in Workstation 17. Native ESXi validation is pending.
QCOW2 disks + import helper
TAR.GZ · 1.54 GB
29 functional checks, backup/restore and cold-boot persistence passed under QEMU software emulation. Native KVM acceleration and libvirt import validation are pending.
VHDX disks + import helper
ZIP · 1.63 GB
Native Generation 2 boot, Secure Boot and HTTPS dashboard availability tested on Windows 11 Pro. API/login, trial, recovery and cold-boot tests are pending. Boot-tested only.
Download the checksum and signature alongside your archive. Compare its SHA-256 with the checksum file, then verify the checksum signature with the public key.
Get-FileHash .\YOUR-DOWNLOAD -Algorithm SHA256 openssl pkeyutl -verify -pubin -inkey zentryc-release.pub -rawin -in YOUR-DOWNLOAD.sha256 -sigfile YOUR-DOWNLOAD.sha256.sig
Each KVM and Hyper-V package includes both disks, a checksum manifest, an import helper and instructions. The helpers verify the extracted disks and copy them into a new VM directory. Keep the unbooted master disks for future fresh imports.
Workstation 17 or later remains available for local evaluation. Choose File → Open, select the OVA and a new storage folder. NAT with DHCP is suitable for local testing. Keep the host clock correct, EFI and Secure Boot enabled, then power on.
Use a native KVM host with libvirt 8.6+, virsh, Python 3.11+ and OVMF Secure Boot firmware with enrolled Microsoft keys. Provide an existing management bridge with DHCP and keep the VM’s RTC in UTC.
tar -xzf zenplus-appliance-1.24.14-kvm-r1.tar.gz cd zenplus-1.24.14-kvm sudo python3 create-kvm.py --name ZenPlus --bridge br0 \ --directory /var/lib/libvirt/images/zenplus --start
Replace br0 with your existing bridge. Choose a new VM directory that your libvirt security policy permits and the QEMU service can read. Open the VM’s graphical console with Virtual Machine Manager or virt-viewer.
Extract the ZIP. In an administrator PowerShell session, open the extracted zenplus-1.24.14-hyperv folder and run:
.\Import-ZenPlus.ps1 -Name ZenPlus -SwitchName 'External' -VMDirectory 'D:\VMs\ZenPlus' -Start
Replace External with your existing virtual switch connected to a trusted DHCP network, and select a new VM directory. The helper creates a Generation 2 VM with fixed 8 GiB RAM, 4 CPUs, both SCSI disks and the Microsoft UEFI Certificate Authority Secure Boot template. It removes NTFS compression and sparse flags from the copied disks and disables automatic checkpoints for the new VM.
Keep the host clock accurate and the Time Synchronization integration service enabled. Open Connect in Hyper-V Manager for the console.
The trial starts at first initialization and lasts 30 days: 50 devices, 20 service checks and 5 users. There is no shared administrator or SSH password. Console option 3 sets or recovers the administrator password. Activate a license through subscription settings when ready.
| Use | Destination |
|---|---|
| Management, agents and API | HTTPS TCP 443 |
| OpenTelemetry HTTP | https://APPLIANCE/v1/traces with application ingest credentials |
| NetFlow | UDP 2055 |
| sFlow | UDP 6343 |
| SNMP traps | UDP 162 |
Database ports remain private. Place the appliance on a trusted management network, configure the management allowlist and install an organization-trusted certificate for normal operation.
The console provides network configuration with timed rollback, service status, password recovery, restart and shutdown. Use Storage for backups and Support for diagnostic bundles. Keep an independent hypervisor backup before major changes. A fresh import creates a separate appliance; it does not restore an existing deployment’s data.