DokuWiki » Infrastructure » Operating System » Windows 7

h1. Setup Zabbix 3.0 agent on Microsoft Windows

this is basically copied from https://www.zabbix.com/documentation/3.0/manual/appendix/install/windows_agent

further information may be found at: http://yallalabs.com/windows/how-to-install-zabbix-agent-3-4-and-add-windows-host-to-zabbix-monitoring/

h2. Configuring agent

Zabbix agent runs as a Windows service.

You can run a single instance of Zabbix agent or multiple instances of the agent on a Microsoft Windows host. A single instance can use the default configuration file ''C:\zabbix_agentd.conf'' or a configuration file specified in the command line. In case of multiple instances each agent instance must have its own configuration file (one of the instances can use the default configuration file).

An example configuration file is available in Zabbix source archive as ''conf/zabbix_agentd.win.conf''.

See the https://www.zabbix.com/documentation/3.0/manual/appendix/config/zabbix_agentd_win options for details on configuring Zabbix Windows agent.

h3. Hostname parameter

To perform active checks on a host Zabbix agent needs to have the hostname defined. Moreover, the hostname value set on the agent side should exactly match the "Host name" configured for the host in the frontend.

The hostname value on the agent side can be defined by either the **Hostname** or **HostnameItem** parameter in the agent configuration file - or the default values are used if any of these parameters are not specified.

The default value for **HostnameItem** parameter is the value returned by the "system.hostname" agent key and for Windows platform it returns the NetBIOS host name.

The default value for **Hostname** is the value returned by the **HostnameItem** parameter. So, in effect, if both these parameters are unspecified the actual hostname will be the host NetBIOS name; Zabbix agent will use NetBIOS host name to retrieve the list of active checks from Zabbix server and send results to it.

**NOTE:**

The **system.hostname** key always returns the NetBIOS host name which is limited to 15 symbols and in UPPERCASE only - regardless of the length and lowercase/uppercase characters in the real host name.

Starting from Zabbix agent 1.8.6 version for Windows the "system.hostname" key supports an optional parameter - _type_ of the name. The default value of this parameter is "netbios" (for backward compatibility) and the other possible value is "host". 

**NOTE:**

The **system.hostname[host]** key always returns the full, real (case sensitive) Windows host name.

So, to simplify the configuration of zabbix_agentd.conf file and make it unified, two different approaches could be used.

  - leave **Hostname** or **HostnameItem** parameters undefined and Zabbix agent will use NetBIOS host name as the hostname;

  - leave **Hostname** parameter undefined and define **HostnameItem** like this:\\ **HostnameItem=system.hostname[host]**\\ and Zabbix agent will use the full, real (case sensitive) Windows host name as the hostname.

Host name is also used as part of Windows service name which is used for installing, starting, stopping and uninstalling the Windows service. For example, if Zabbix agent configuration file specifies ''Hostname=Windows_db_server'', then the agent will be installed as a Windows service "''Zabbix Agent [Windows_db_server]''". Therefore, to have a different Windows service name for each Zabbix agent instance, each instance must use a different host name.

h2. Installing agent as Windows service

To install a single instance of Zabbix agent with the default configuration file ''c:\zabbix_agentd.conf'':

<pre>

zabbix_agentd.exe --install

</pre>

**NOTE:**

On a 64-bit system, a 64-bit Zabbix agent version is required for all checks related to running 64-bit processes to work correctly.

If you wish to use a configuration file other than ''c:\zabbix_agentd.conf'', you should use the following command for service installation:

<pre>

zabbix_agentd.exe --config <your_configuration_file> --install

</pre>

A full path to the configuration file should be specified.

Multiple instances of Zabbix agent can be installed as services like this:

<pre>

zabbix_agentd.exe --config <configuration_file_for_instance_1> --install --multiple-agents

zabbix_agentd.exe --config <configuration_file_for_instance_2> --install --multiple-agents

...

zabbix_agentd.exe --config <configuration_file_for_instance_N> --install --multiple-agents

</pre>

The installed service should now be visible in Control Panel.

h2. Starting agent

To start the agent service, you can use Control Panel or do it from command line.

To start a single instance of Zabbix agent with the default configuration file:

<pre>

zabbix_agentd.exe --start

</pre>

To start a single instance of Zabbix agent with another configuration file:

<pre>

zabbix_agentd.exe --config <your_configuration_file> --start

</pre>

To start one of multiple instances of Zabbix agent:

<pre>

zabbix_agentd.exe --config <configuration_file_for_this_instance> --start --multiple-agents

</pre>

h2. Stopping agent

To stop the agent service, you can use Control Panel or do it from command line.

To stop a single instance of Zabbix agent started with the default configuration file:

<pre>

zabbix_agentd.exe --stop

</pre>

To stop a single instance of Zabbix agent started with another configuration file:

<pre>

zabbix_agentd.exe --config <your_configuration_file> --stop

</pre>

To stop one of multiple instances of Zabbix agent:

<pre>

zabbix_agentd.exe --config <configuration_file_for_this_instance> --stop --multiple-agents

</pre>

h2. Uninstalling agent Windows service

To uninstall a single instance of Zabbix agent using the default configuration file:

<pre>

zabbix_agentd.exe --uninstall

</pre>

To uninstall a single instance of Zabbix agent using a non-default configuration file:

<pre>

zabbix_agentd.exe --config your_configuration_file --uninstall

</pre>

To uninstall multiple instances of Zabbix agent from Windows services:

<pre>

zabbix_agentd.exe --config configuration_file_for_instance_1 --uninstall --multiple-agents

zabbix_agentd.exe --config configuration_file_for_instance_2 --uninstall --multiple-agents

...

zabbix_agentd.exe --config configuration_file_for_instance_N --uninstall --multiple-agents

</pre>