Prepare a Windows server

Product Zbix CRM · Version 1.2.0 · Source reviewed · Reviewed 28 October 2026
Audience Administrators and implementation teams · Deployment Release specific self hosted

Overview

The native Windows package creates a shared Zbix CRM server accessed from browsers. It includes native application processes, PostgreSQL 17, the compiled web interface, a Windows service host and Caddy for HTTPS. There is no Docker, WSL, Hyper-V, Linux VM or WebView2 requirement for this installation method.

Purpose

Validate the Windows host and access design without borrowing Linux resource figures or assuming that an installer operating-system check is a complete support certification.

Prerequisites

• Administrator access to an always-on x64-compatible Windows host.

• The approved native Windows installer and its release checksum.

• An agreed public-domain, private-network or combined access design.

Procedure

1. Confirm the target Windows build with the implementation owner. The installer has a minimum version gate of 10.0.17763 and x64-compatible architecture; the available evidence does not provide a complete certified Windows Server edition/build matrix.

2. Size CPU, memory and storage through a workload-specific assessment and an isolated installation test. No verified Windows hardware minimum was found in the reviewed release evidence.

3. Provide space for application binaries, PostgreSQL, private files, logs, temporary recovery work and retained backups. Keep recovery-key custody independent of the data drive.

4. Reserve the gateway ports required by the exact installer release. Keep the internal PostgreSQL and API listeners private. Resolve existing web-server port ownership before installation.

5. For public access, prepare a stable DNS name and the required inbound HTTPS and certificate-validation connectivity. For private hostnames or addresses, plan managed distribution of the exported office CA certificate.

6. Confirm that the organization accepts the distribution package under its software approval process. The published 1.2.0 installer is not Authenticode-signed; browser TLS certificates do not replace publisher signing.

Expected result

The host, Windows build, capacity, software provenance and client trust plan are approved for an isolated installation and subsequent operational handover.

Screenshots and diagrams

Important notes

• The service host is packaged as a self-contained .NET Windows application. End users only need an appropriate browser and network access.

• The 25 October native acceptance report covers isolated runtime startup and HTTPS on the earlier 1.0.0 package. The published 1.2.0 package must retain its own qualification status.

• The runtime uses ProgramData for persistent state. Reinstalling binaries is not a substitute for an independently verified recovery point.

Troubleshooting

• If the installer rejects the operating system or architecture, obtain a compatible approved package rather than bypassing the check.

• If another service occupies a gateway port, have the implementation owner review the exact release and coexistence design before starting CRM.

• Escalate missing hardware qualification or unsigned-software policy questions before customer onboarding.

Related articles

• Install the native Windows Server edition

• Plan network access DNS and HTTPS

• Plan capacity for CRM workloads

• Complete the installation readiness review