4 Windows agent installation from MSI

Overview

Zabbix Windows agent can be installed from Windows MSI installer packages (32-bit or 64-bit) available for download.

A 32-bit package cannot be installed on a 64-bit Windows.

The minimum requirement for MSI installation is:

  • Windows XP x64 and Server 2003 for Zabbix agent;
  • Windows 7 x32 for Zabbix agent 2.

The Zabbix get and sender utilities can also be installed, either together with Zabbix agent/agent 2 or separately.

All packages come with TLS support, however, configuring TLS is optional.

Both UI and command-line based installation is supported.

Although Zabbix installation from MSI installer packages is fully supported, it is recommended to install at least Microsoft .NET Framework 2 for proper error handling. See Microsoft Download .NET Framework.

It is recommended to use default paths provided by the installer as using custom paths without proper permissions could compromise the security of the installation.

Installation steps

To install, double-click the downloaded MSI file.

4 Windows agent installation from MSI - 图1

4 Windows agent installation from MSI - 图2

Accept the license to proceed to the next step.

4 Windows agent installation from MSI - 图3

Specify the following parameters.

ParameterDescription
Host nameSpecify host name.
Zabbix server IP/DNSSpecify IP/DNS of Zabbix server.
Agent listen portSpecify agent listen port (10050 by default).
Server or Proxy for active checksSpecify IP/DNS of Zabbix server/proxy for active agent checks.
Enable PSKMark the checkbox to enable TLS support via pre-shared keys.
Add agent location to the PATHAdd agent location to the PATH variable.

4 Windows agent installation from MSI - 图4

Enter pre-shared key identity and value. This step is only available if you checked Enable PSK in the previous step.

4 Windows agent installation from MSI - 图5

Select Zabbix components to install - Zabbix agent daemon, Zabbix sender, Zabbix get.

4 Windows agent installation from MSI - 图6

Zabbix components along with the configuration file will be installed in a Zabbix Agent folder in Program Files. zabbix_agentd.exe will be set up as Windows service with automatic startup.

4 Windows agent installation from MSI - 图7

Command-line based installation

Supported parameters

The following parameters are supported by created MSIs.

ParameterDescription
ADDDEFAULTA comma-delimited list of programs to install.
Possible values: AgentProgram, GetProgram, SenderProgram, ALL.
Example: ADDDEFAULT=AgentProgram,GetProgram
ADDLOCALA comma-delimited list of programs to install.
Possible values: AgentProgram, GetProgram, SenderProgram, ALL.
Example: ADDLOCAL=AgentProgram,SenderProgram
ALLOWDENYKEYSequence of “AllowKey” and “DenyKey” parameters separated by ;
Use \; to escape the delimiter.
CONFThe full pathname to a custom configuration file.
Example: CONF=c:\full\path\to\user.conf
ENABLEPATHAdd agent location to the PATH variable.
ENABLEPERSISTENTBUFFERZabbix agent 2 only. Enable the usage of local persistent storage for active items.
HOSTINTERFACEAn optional parameter that defines the host interface.
HOSTMETADATAAn optional parameter that defines the host metadata.
HOSTMETADATAITEMAn optional parameter that defines a Zabbix agent item used for getting the host metadata.
HOSTNAMEAn optional parameter that defines the hostname.
INCLUDESequence of includes separated by ;
INSTALLFOLDERThe full pathname of the folder in which Zabbix components along with the configuration file will be installed.
LISTENIPA list of comma-delimited IP addresses that the agent should listen on.
LISTENPORTThe agent will listen on this port for connections from the server.
LOGFILEThe name of the log file.
LOGTYPEThe type of the log output.
PERSISTENTBUFFERFILEZabbix agent 2 only. The file where Zabbix agent 2 should keep the SQLite database.
PERSISTENTBUFFERPERIODZabbix agent 2 only. The time period for which data should be stored when there is no connection to the server or proxy.
SERVERA list of comma-delimited IP addresses, optionally in CIDR notation, or DNS names of Zabbix servers and Zabbix proxies.
SERVERACTIVEThe Zabbix server/proxy address or cluster configuration to get active checks from.
SKIPSKIP=fw - do not install the firewall exception rule.
STATUSPORTZabbix agent 2 only. If set, the agent will listen on this port for HTTP status requests (http://localhost:<port>/status).
TIMEOUTSpend no more than Timeout seconds on processing.
TLSACCEPTWhat incoming connections to accept.
TLSCAFILEThe full pathname of a file containing the top-level CA(s) certificates for peer certificate verification, used for encrypted communications between Zabbix components.
TLSCERTFILEThe full pathname of a file containing the agent certificate or certificate chain, used for encrypted communications between Zabbix components.
TLSCONNECTHow the agent should connect to Zabbix server or proxy.
TLSCRLFILEThe full pathname of a file containing revoked certificates. This parameter is used for encrypted communications between Zabbix components.
TLSKEYFILEThe full pathname of a file containing the agent private key, used for encrypted communications between Zabbix components.
TLSPSKFILEThe full pathname of a file containing the agent pre-shared key, used for encrypted communications with Zabbix server.
TLSPSKIDENTITYThe pre-shared key identity string, used for encrypted communications with Zabbix server.
TLSPSKVALUEThe pre-shared key string value, used for encrypted communications with Zabbix server.
TLSSERVERCERTISSUERThe allowed server (proxy) certificate issuer.
TLSSERVERCERTSUBJECTThe allowed server (proxy) certificate subject.
Examples

To install Zabbix Windows agent from the command-line, you may run, for example:

  1. SET INSTALLFOLDER=C:\Program Files\Zabbix Agent
  2. msiexec /l*v log.txt /i zabbix_agent-6.4.0-x86.msi /qn^
  3. LOGTYPE=file^
  4. LOGFILE="%INSTALLFOLDER%\zabbix_agentd.log"^
  5. SERVER=192.168.6.76^
  6. LISTENPORT=12345^
  7. SERVERACTIVE=::1^
  8. HOSTNAME=myHost^
  9. TLSCONNECT=psk^
  10. TLSACCEPT=psk^
  11. TLSPSKIDENTITY=MyPSKID^
  12. TLSPSKFILE="%INSTALLFOLDER%\mykey.psk"^
  13. TLSCAFILE="c:\temp\f.txt1"^
  14. TLSCRLFILE="c:\temp\f.txt2"^
  15. TLSSERVERCERTISSUER="My CA"^
  16. TLSSERVERCERTSUBJECT="My Cert"^
  17. TLSCERTFILE="c:\temp\f.txt5"^
  18. TLSKEYFILE="c:\temp\f.txt6"^
  19. ENABLEPATH=1^
  20. INSTALLFOLDER="%INSTALLFOLDER%"^
  21. SKIP=fw^
  22. ALLOWDENYKEY="DenyKey=vfs.file.contents[/etc/passwd]"

You may also run, for example:

  1. msiexec /l*v log.txt /i zabbix_agent-6.4.0-x86.msi /qn^
  2. SERVER=192.168.6.76^
  3. TLSCONNECT=psk^
  4. TLSACCEPT=psk^
  5. TLSPSKIDENTITY=MyPSKID^
  6. TLSPSKVALUE=1f87b595725ac58dd977beef14b97461a7c1045b9a1c963065002c5473194952

If both TLSPSKFILE and TLSPSKVALUE are passed, then TLSPSKVALUE will be written to TLSPSKFILE.