Administrator's Guide - Kerio Software Archive

Introduction
2.8 Upgrade - Software Appliance / VMware Virtual Appliance
Kerio Control can be upgraded by the following two methods:
• by starting the system from the installation CD (or a mounted ISO) of the new version.
The installation process is identical with the process of a new installation with an the
only exception that at the start the installer asks you whether to execute an upgrade
(any existing data will be kept) or a new installation (all configuration files, statistics,
logs, etc will be removed). For details, see chapter 2.7.
• by the Kerio Administration Console update checker. For details, refer to chapter 17.3
Warning:
Since 6.7.1, some configuration parameters have been changed for version 7.0.0. Although
updates are still performed automatically and seamlessly, it is necessary to mind the
changes described above that take effect immediately upon installation of the new version.
The following parameters are affected:
• Log file names — fixed log file names are set now (alert.log, config.log,
debug.log, etc.).
The path for saving the log files is kept unchanged — logs are saved under
/opt/kerio/winroute/logs
If log file names has been changed, the original files are kept and new logs are
recorded in files with corresponding names.
• Log type (Facility) and its Severity for external logging on the Syslog server — fixed
facility and severity values of individual logs of Kerio Control are now set. This is
a fact to bear in mind while viewing firewall logs on the Syslog server.
For details on log settings, see chapter 22.1.
After update, it is recommended to check Warning log carefully (see chapter 22.13).
2.9 Kerio Control components
Kerio Control consists of these components:
Kerio Control Engine
The core of the program that executes all services and functions. It is running as a service
in the operating system (the service is called Kerio Control and it is run automatically
within the system account by default).
Kerio Control Engine Monitor (Windows only)
Allows viewing and modification of the Engine’s status (stopped / running) and setting
of start-up preferences (i.e. whether Engine and Monitor should be run automatically at
system start-up). It also provides easy access to the Administration Console. For details,
refer to chapter 2.10.
26