Downloads of v 3.4.11:


Last Update:

28 Sep 2018

Package Maintainer(s):

Software Author(s):

  • Zabbix SIA


zabbix monitoring admin

Zabbix Agent (TLS)

3.4.11 | Updated: 28 Sep 2018



Downloads of v 3.4.11:



Software Author(s):

  • Zabbix SIA

Zabbix Agent (TLS) 3.4.11

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed


To install Zabbix Agent (TLS), run the following command from the command line or from PowerShell:


To upgrade Zabbix Agent (TLS), run the following command from the command line or from PowerShell:


To uninstall Zabbix Agent (TLS), run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade zabbix-agent-tls -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade zabbix-agent-tls -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure zabbix-agent-tls installed
    name: zabbix-agent-tls
    state: present
    version: 3.4.11
    source: STEP 3 URL

See docs at

Coming early 2020! Central Managment Reporting available now! More information...

chocolatey_package 'zabbix-agent-tls' do
  action    :install
  version  '3.4.11'
  source   'STEP 3 URL'

See docs at

    Name: zabbix-agent-tls,
    Version: 3.4.11,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller zabbix-agent-tls
   Name     = 'zabbix-agent-tls'
   Ensure   = 'Present'
   Version  = '3.4.11'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'zabbix-agent-tls':
  provider => 'chocolatey',
  ensure   => '3.4.11',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install zabbix-agent-tls version="3.4.11" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator Pauby on 01 Oct 2018.


This package installs a version of the Zabbix Agent compiled with TLS support and bundled with openssl libs. Zabbix LLC has refrained from distributing openssl/gnutls/mbedTLS binaries for legal reasons. These sources are extracted from user-contributed builds in support ticket ZBXNEXT-3047.

Executables are placed in %ProgramFiles%\Zabbix Agent and the zabbix_agentd.conf file is stored in %ProgramData%\zabbix. When new versions of the agent are installed, the config is not overwritten but rather the version number of the new file is appended to the name. For example, if version 3.2.0 is installed and then upgraded to version 3.4.6 you will find the sample 3.4.6 config files saved as “zabbix_agentd-3.4.6.conf”.

The source code for this Chocolatey package can be found on GitHub, forked from the original repo maintained by Zabbix LLC. Please do not file issues to the upstream tracker without verifying they are not unique to this TLS-enabled version.

$version        = '3.4.11'
$id             = 'zabbix-agent'
$title          = 'Zabbix Agent'
$url            = "$"
$url64          = "$"
$checksum       = "ab880f1ab3eddda6c7fbf19dd188a080"
$checksumType   = "md5"
$checksum64     = "48ebd868443d51c0c709888001f3a15a"
$checksumType64 = $checksumType

$is64bit = (Get-WmiObject -Class Win32_OperatingSystem | Select-Object OSArchitecture) -match '64'

$service = Get-WmiObject -Class Win32_Service -Filter "Name=`'$title`'"

$configDir    = Join-Path $env:PROGRAMDATA 'zabbix'
$zabbixConf   = Join-Path $configDir 'zabbix_agentd.conf'

$installDir   = Join-Path $env:PROGRAMFILES $title
$installDirHeaders  = Join-Path $installDir 'dev'
$zabbixAgentd = Join-Path $installDir 'zabbix_agentd.exe'

$tempDir      = Join-Path $env:TEMP 'chocolatey\zabbix'

if ($is64bit) {
  $zipFile      = Join-Path $tempDir "zabbix-$"
} else {
  $zipFile      = Join-Path $tempDir "zabbix-$"
$sampleConfig = Join-Path $tempDir 'conf\'
$binFiles     = @('zabbix_agentd.exe', 'zabbix_get.exe', 'zabbix_sender.exe', 
 'libcrypto-1_1-x64.dll', 'libssl-1_1-x64.dll', 'msvcr120.dll')
$headerFiles  = @('zabbix_sender.dll', 'zabbix_sender.h', 'zabbix_sender.lib')

try {
  if ($service) {

  if (!(Test-Path $configDir)) {
    New-Item $configDir -type directory

  if (!(Test-Path $installDir)) {
    New-Item $installDir -type directory

  if (!(Test-Path $tempDir)) {
    New-Item $tempDir -type directory

  Get-ChocolateyWebFile -PackageName "$id" -FileFullPath "$zipFile" -Url "$url" -Url64bit "$url64" -Checksum "$checksum" -ChecksumType "$checksumType" -Checksum64 "$checksum64" -ChecksumType64 "$checksumType64"
  Get-ChocolateyUnzip "$zipFile" "$tempDir"

  if ($is64bit) {
    $binDir = Join-Path $tempDir 'win64'
    $headerDir = Join-Path $tempDir 'win64\dev'
  } else {
    $binDir = Join-Path $tempDir 'win32'
    $headerDir = Join-Path $tempDir 'win32\dev'

  foreach ($executable in $binFiles ) {
    $file = Join-Path $binDir $executable
    Move-Item $file $installDir -Force
  foreach ($header in $headerFiles ) {
    $file = Join-Path $headerDir $header
    Move-Item $file $installDirHeaders -Force

  if (Test-Path "$installDir\zabbix_agentd.conf") {
    if ($service) {
      Clear-Variable -Name $service

    Move-Item "$installDir\zabbix_agentd.conf" "$configDir\zabbix_agentd.conf" -Force

  } elseif (Test-Path "$configDir\zabbix_agentd.conf") {
    $configFile = "$configDir\zabbix_agentd-$version.conf"
    Move-Item $sampleConfig $configFile -Force

  } else {
    $configFile = "$configDir\zabbix_agentd.conf"
    Move-Item $sampleConfig $configFile


  if (!($service)) {
    Start-ChocolateyProcessAsAdmin "--config `"$zabbixConf`" --install" "$zabbixAgentd"

  Start-Service -Name $title

  Install-ChocolateyPath $installDir 'Machine'

} catch {
  Write-Host "Error installing Zabbix Agent"
  throw $_.Exception
$id         = 'zabbix-agent'
$title      = 'Zabbix Agent'
$installDir = Join-Path $env:PROGRAMFILES $title
$configDir  = Join-Path $env:PROGRAMDATA 'zabbix'

  $service = Get-WmiObject -Class Win32_Service -Filter "Name=`'$title`'"

  if ($service) {

  Remove-Item $installDir -Recurse
  Remove-Item $configDir -Recurse

  Write-Host "Error uninstalling Zabbix Agent"
  throw $_.Exception

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Zabbix Agent (TLS) 3.4.9 152 Thursday, July 12, 2018 Approved

2018-09-28 Release 3.4.11

  • Bumped up to Zabbix 3.4.11 from initial TLS version 3.4.9

2018-05-25 Release 3.4.6

  • Bumped up to Zabbix 3.4.6
  • Fix logo for nuspec config

2017-03-01 Release 3.2.0

  • Bumped up to Zabbix 3.2.0
  • Updated logo
  • Swiched repository references back to
  • Updated to newer nuspec config

2017-03-01 Release 3.0.4

  • Removed depreciated values from install scripts
  • Bumped up to Zabbix 3.0.4
  • Switched download url to https://

2015-03-22 Release 2.4.4

  • Moved config file from $env:ProgramFiles\Zabbix Agent to $env:ProgramData\zabbix
  • Reworked .nuspec file to adhere to Chocolatey standards
  • Reworked scripts so that all variables are at the top and so that they are less likely to throw
    errors or fail
  • Made syntax more consistent throughout scripts. For example, changed to use Join-Path everywhere
    instead of just in some place.

This package has no dependencies.

Discussion for the Zabbix Agent (TLS) Package

Ground Rules:

  • This discussion is only about Zabbix Agent (TLS) and the Zabbix Agent (TLS) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Zabbix Agent (TLS), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus