A permalink to the current version of the Zabbix agent MSI would be useful for scripting, etc.
Ad Widget
Collapse
Link to current version of Zabbix agent MSI
Collapse
X
-
Are you thinking about creating agent self update script? If so I would advice against it. It is better to use higher server version than the agent version and not the other way arround. As the backwards compatibility works from server to agent.
Once you update server you know which version of the agent you are going to use.👍 1 -
+1 for Blevar.
however if You still would like to pursue this, You might want to monitor the CDN for newer versions:
Comment
-
Clarifying that this is true when dealing with major versions, ie. 7.0 vs 7.2. For minor versions, not so much. We update agents minor versions more frequently than the server's and have never run into any problems. Same thing with proxies and servers, they should be of the same major version.Are you thinking about creating agent self update script? If so I would advice against it. It is better to use higher server version than the agent version and not the other way arround. As the backwards compatibility works from server to agent.
Once you update server you know which version of the agent you are going to use.Comment
-
This is not for automatic updates, this is for initial install so we don't have to edit install scripts when we want to start installing a newer version.
msiexec is happy to follow redirects, so we just stuck a redirect on example.com/zabbxagent.msi to the current version and use that in scripts. That's good enough for me.
I am not clear on the logic of choosing a different server/agent versions.Comment
-
> Clarifying that this is true when dealing with major versions, ie. 7.0 vs 7.2
I've used wildly different versions without any obvious ill effect [today I am deleting a bunch of hosts with 7.2.2 from a server running 4.4.10] . I know it's "not supported", but I don't pay for support anyway, so don't really care.Comment
-
I agree, perpetual Evergreen download links for the latest agent versions should be made available. It is a simple easy thing to do.Comment
-
👍 1
Comment
-
That link is helpful indeed. However, you still need figure out your exact download URL. To that end, I wrote a PowerShell function that will get you the latest download link from the CDN for specific trains and windows architecture. It will also optionally download the MSI installer to a location of your choice.
The-smart-way-to-update-zabbix-agents-powershell-automation-for-businesses/
Here are some brief details. See the article page for full details and code download.
Code:Get-ZabbixAgent2LatestCdn { <# .SYNOPSIS Returns the fully versioned CDN URL for the latest Windows Zabbix Agent 2 MSI. .PARAMETER Architecture 'amd64' (default) or 'i386'. .PARAMETER Train Optional (e.g., '7.4', '7.2', '7.0'). If omitted, the newest train is auto-detected from the CDN. .PARAMETER Channel CDN channel. Default: 'stable'. .PARAMETER DownloadTo Optional path to save the MSI. If provided, the file is downloaded and SHA256 is computed. .PARAMETER MaxRetries Maximum number of retry attempts for network operations. Default: 3. .PARAMETER RetryDelaySeconds Delay in seconds between retry attempts. Default: 2. .PARAMETER TimeoutSec Timeout in seconds for web requests. Default: 30. .PARAMETER ListAllVersions If specified, returns all available patch versions (X.Y.Z) for the selected train instead of the latest. .PARAMETER BaseUrl Base URL for Zabbix binaries CDN. Default: "https://cdn.zabbix.com/zabbix/binaries/". .OUTPUTS PSCustomObject with properties: - Train: The major/minor train (e.g., '7.4'). - Version: The full version (e.g., '7.4.1'). - Architecture: The architecture of the Zabbix Agent 2 ('amd64' or 'i386'). - Url: The fully qualified URL to the MSI file. - Sha256: The SHA256 hash of the downloaded MSI (if downloaded). - FilePath: The file path provided or resolved for the MSI (may be relative or as given). - FullFilePath: The absolute/resolved full file path to the MSI (if downloaded or exists). - FileSize: The size of the MSI file in bytes (if available). - Channel: The CDN channel used (e.g., 'stable'). - Source: The source domain (e.g., 'cdn.zabbix.com'). - FileName: The MSI file name. .EXAMPLE $r = Get-ZabbixAgent2LatestCdn -Architecture amd64 $r.Url .EXAMPLE $r = Get-ZabbixAgent2LatestCdn -Train '7.2' -DownloadTo 'C:\Temp' -Verbose #> }👍 2Comment
-
Yeah, I guess that's close enough. Seeing as this exists, I do wonder why the documentation points to specific sub-versions and not just the /latest/ URL.https://cdn.zabbix.com/zabbix/binari...le/7.4/latest/ ??
Even the names contain "latest"...Comment
-
There is option to choose certain version... They could probably include "latest" in that list..
But noone has pointed it out yet...
Comment
Comment