

This is not necessarily identical to the host name of the computer. When registering the plug-in also needs the name of the host as it is known in the monitoring.

Hint: you can do this in scripts with the command:Ĭmk-update-agent register -s -i heute -H myserver -p https -U cmkadmin -P * -v Saved your registration settings to /etc/cmk-update-agent.state.

You can now update your agent by running 'cmk-update-agent -v'

Successfully registered agent of host "myserver" for deployment. Going to register agent at deployment server | For this step you need an administration account on WATO for | | register this host at your deployment server for agent updates. | Check_MK Agent Updater v2.0.0 - Registration | Other architectures: If you have packages for other architectures such as arm or ppc, set this option manually to the Python script, since Checkmk does not intercept this automatically and no binaries are offered for these cmk-update-agent register -v Checkmk will use the Python script even if you leave the default value on the 64bit binary. Solaris: You do not have to adjust anything here either. Note: Should you find a 64bit binary of the agent updater on any of your Windows hosts, this version dates back to an older version of Checkmk and is not up-to-date. This rule is being ignored for Windows hosts. Windows: For Windows hosts Checkmk will always deploy a 32bit-executable. Any existing setting in this rule is ignored. Note: As of Version 1.6.0 of Checkmk, the plug-in is always delivered as a 32-bit executable code. The script is not available here and will be ignored accordingly. Windows: The 64bit binary is also the default - if necessary you can select the 32bit binary. Linux distributions have generally met these requirements since 2006. Important: For the binary you need the glibc package (minimum the 2.5 version). You can also optionally select a 32bit binary for legacy systems, or the old Python script. Linux (deb, rpm, tgz): You do not have to manually adjust anything for these systems the agent updater is passed as a 64bit binary.
