junglehaa.blogg.se - Zabbix agent msi deployment

The activated trigger indicates that there is a problem.

If the received data meet the specified conditions, a trigger is activated.

A Zabbix server receives and processes the data.

Usually, the operating scheme looks like this:

Apache2/Nginx web server with a PHP handler.

A zabbix_server binary (usually, it is working as a service).

Again, a simple SCCM package that contains a static powershell script, which executes another powershell script in Github, that is the one that download userparam file and metadata file etc from Github, and compares the files, and if there is a newer version from Git, it replaces the file and restart the Agent.

This means that my SCCM package never has to be updated, and I maintain my configuration from Github.Īfter that, I made another script that keeps my configuration files updated on all of our servers. What I have done in my own environment is having created a SCCM package, that contains a static Powershell script, which executes another script from Github. Also an uninstallation and upgrade script. This is the simple version where it automatically downloads the zabbix agent and installs it. I have created some simplified Powershell scripts but the one I use my self is much more advanced and do more things. I have actually done this in my environment. I have good success with this, though it may not be the ideal way to go. On the Zabbix server I define this an auto registrations action looking for hosts with this as a condition Conditions

In the conf file I set the server for passive and active the FQDN of my Zabbix host and define this item HostMetadataItem=system.uname Zabbix_agentd.exe -config "C:\Zabbix\zabbix_nf" -installĮcho Starting Zabbix agent installation and configuration script - FINISHED IF EXIST "C:\Zabbix" (GOTO Yes) ELSE (GOTO No) Netsh advfirewall firewall add rule name="Zabbix out" dir=out action=allow protocol=TCP localport=10050 Netsh advfirewall firewall add rule name="Zabbix in" dir=in action=allow protocol=TCP localport=10050

I would install the Zabbix agent with something like this onĮcho Starting Zabbix agent installation and configuration script Then separately PDQ Deploy had a scheduled deployment for the Zabbix agent to any server without it. When a new server is deployed in AD, PDQ Inv would pick up the new object, scan it and find that Zabbix isn't installed.