for example, in E:\openssl-1.1.1. 4. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 RC. 5. Go to the OpenSSL source directory, e.g. E:\openssl-1.1.1. 1. Verify that NASM For example, E:\pcre2-10.39\build. 5. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 and from that shell environment run cmake-gui. Do not try to start Cmake from the Windows usable build system - Makefile. 15. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 and navigate to the Makefile mentioned above. 16. Run NMake command: E:\pcre2-10.39\build>

后端数据库，则必需。 pgsql 如果使用 PostgreSQL 作为 Zabbix 后端数据库，则必需。 curl php-curl。如果未安装，前端将照常工作，但是 Duo Universal Prompt 多因素身份验证 选项将不可用。 Zabbix 提供的第三方前端库： 库名称 强制状态 最小版本 备注 jQuery JavaScript Library 是 3.6.0 简化跨浏览器开发过程的 件以显示来自站点子域或外部域的内容、从 OpenStreetMap 切换到另一个地图引擎或添加外部 CSS 或小部件，则可能需要不同 的 CSP 标头配置。如果您使用 Duo Universal Prompt 多因素身份认证 方法，请确保将 “duo.com” 添加到虚拟主机配置文件中 的 CSP 指令中。 要在 Apache 配置中为 Zabbix 前端启用 CSP，请按照以下步骤操作： 1. Duo Universal Prompt。 配置 配置参数： 参数 描述 启用多因素认证 勾选此框以启用多因素认证。 方法 点击 添加来配置一个多因素认证方法（参见下面的方法配置）。 方法配置 方法配置参数： 参数 描述 类型 选择多因素认证方法的类型： TOTP - 使用认证器应用生成基于时间的一次性密码； Duo Universal Prompt - 使用Duo认证服务提供多因素认证。

environmental variable @echo off set PATH=%PATH%;c:\bin\mingw\bin cmd When compiling use Windows prompt instead of MSYS terminal provided by MinGW Compiling PCRE The following instructions will compile before static libraries. Compiling Zabbix agent 2 32 bit Open MinGW environment (Windows command prompt) and navigate to build/mingw directory in the Zabbix source tree. Run: mingw32-make clean mingw32-make ARCH=x86 PCRE=c:\dev\pcre32 OPENSSL=c:\dev\openssl32 64 bit Open MinGW environment (Windows command prompt) and navigate to build/mingw directory in the Zabbix source tree. Run: mingw32-make clean mingw32-make

for example, in E:\openssl-1.1.1. 4. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 RC. 5. Go to the OpenSSL source directory, e.g. E:\openssl-1.1.1. 1. Verify that NASM For example, E:\pcre-8.41\build. 5. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 and from that shell environment run cmake-gui. Do not try to start Cmake from the Windows usable build system - Makefile. 15. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 and navigate to the Makefile mentioned above. 16. Run NMake command: E:\pcre-8.41\build>

whatever size you made available for the virtual disk. To do so, enter the following sequence in fdisk prompt: d n p 1 (accept default 63) (accept default max) If you wish to leave some space for additional by Windows agent is currently not supported. Note that the telnet check looks for a login prompt (’:’ at the end). Old naming: check_service[*] https and telnet services are supported since by Windows agent is currently not supported. Note that the telnet check looks for a login prompt (’:’ at the end). Old naming: check_service_perf[*] https and telnet services are supported

environmental variable @echo off set PATH=%PATH%;c:\bin\mingw\bin cmd When compiling use Windows prompt instead of MSYS terminal provided by MinGW Compiling PCRE development libraries The following instructions before static libraries. Compiling Zabbix agent 2 32 bit Open MinGW environment (Windows command prompt) and navigate to build/mingw directory in the Zabbix source tree. Run: mingw32-make clean mingw32-make ARCH=x86 PCRE=c:\dev\pcre32 OPENSSL=c:\dev\openssl32 64 bit Open MinGW environment (Windows command prompt) and navigate to build/mingw directory in the Zabbix source tree. Run: mingw32-make clean mingw32-make

Setup environmental variable @echo off set PATH=%PATH%;c:\mingw\bin cmd When compiling use Windows prompt instead of MSYS terminal provided by MinGW Compiling PCRE development libraries The following instructions before static libraries. Compiling Zabbix agent 2 32 bit Open MinGW environment (Windows command prompt) and navigate to build/mingw directory in the Zabbix source tree. Run: mingw32-make clean mingw32-make ARCH=x86 PCRE=c:\dev\pcre32 OPENSSL=c:\dev\openssl32 64 bit Open MinGW environment (Windows command prompt) and navigate to build/mingw directory in the Zabbix source tree. Run: mingw32-make clean mingw32-make

the appliance packages may be upgraded. To do so, run: zypper ref zypper up The last command will prompt to accept repository signing key (this has to be done only once): New repository or package signing whatever size you made available for the virtual disk. To do so, enter the following sequence in fdisk prompt: d n p 1 (accept default 63) (accept default max) If you wish to leave some space for additional by Windows agent is currently not supported. Note that the telnet check looks for a login prompt (’:’ at the end). See also known issues of checking HTTPS service. https and telnet services

for example, in E:\openssl-1.1.1. 4. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 RC. 5. Go to the OpenSSL source directory, e.g. E:\openssl-1.1.1. 1. Verify that NASM that sources are in e:\zabbix-3.0.24. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 RC. Go to e:\3.0.24\build\win32\project. 4. Compile zabbix_get, zabbix_sender and zabbix_agent whatever size you made available for the virtual disk. To do so, enter the following sequence in fdisk prompt: d n p 1 (accept default 63) (accept default max) If you wish to leave some space for additional

for example, in E:\openssl-1.1.1. 4. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 RC. 5. Go to the OpenSSL source directory, e.g. E:\openssl-1.1.1. 1. Verify that NASM For example, E:\pcre-8.41\build. 5. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 and from that shell environment run cmake-gui. Do not try to start Cmake from the Windows usable build system - Makefile. 15. Open a commandline window e.g. the x64 Native Tools Command Prompt for VS 2017 and navigate to the Makefile mentioned above. 16. Run NMake command: E:\pcre-8.41\build>