25 Feb
2021
25 Feb
'21
3:02 p.m.
Branch: refs/heads/2.0.0
Home: https://github.com/tribe29/checkmk
Commit: 1e18962898d840c46368539c60791a422fb0ba0e
https://github.com/tribe29/checkmk/commit/1e18962898d840c46368539c60791a422…
Author: Sergey Kipnis <sergey.kipnis(a)tribe29.com>
Date: 2021-02-25 (Thu, 25 Feb 2021)
Changed paths:
A .werks/11851
Log Message:
-----------
11851 Windows agent MSI checks that Windows OS is appropriate for installation
Previously, it was possible to configure the Windows agent in WATO in such
a way that installing on older operating systems would cause the Windows
agent updater to fail( or make such plugins as mk_jolokia or mk_logwatch more
inoperable). For example: setting of the <tt>Standard python environment(3.8+
)</tt>
and deploy such MSI on Windows 2008. This could cause complete falling out the
host of the monitoring, because installed standard Python, 3.8+, can't work
on Windows 2008.
With this release the problem has been solved. If during deployment configuration
is not supported by Windows OS, the installation will not be performed: the
MSI will always check Windows version and stops installation if Windows OS
doesn't match to it's criteria. The host will continue to operates normally in
any case.
Nevertheless, you need to fix the configuration in WATO in order to make
the update for older Windows system. In the case of the aforementioned example,
you have to select <tt>Deploy legacy environment (Python 3.4 + standard set of
modules)</tt>
in the rule <tt>Install Python runtime environment</tt>, activate changes and
bake
the agent.
Change-Id: Ic13b0ca83d0e38040060cfc3c75f9a784c2fa8be