Please enable JavaScript in your browser!
Upgrading KSMG to version 2.1.1
You can upgrade to KSMG 2.1.1 only from in KSMG 2.1 (2.1.0.7854) or later. If you want to upgrade KSMG to version 2.1.1 from an earlier version, you must first upgrade to version 2.1 or migrate settings .
When you upgrade to version 2.1.1, you lose all manual changes of configuration file templates in the /opt/kaspersky/ksmg/share/templates/core_settings directory, including changes made to implement Technical Support recommendations. You must edit the files to make these changes again after the upgrade.
Upgrade scenario
Upgrading KSMG to version 2.1.1 involves the following steps:
Checking the server for compliance with hardware and software requirements If necessary, update the software to the required version.
Downloading the installation package from the Kaspersky website or a Kaspersky partnerThe KSMG 2.1.1 installation package is used to install the application update.
Upload the following files to the server:
KSMG installation package in DEB or RPM format, depending on your operating system. KSMG localization packages in DEB or RPM format, depending on your operating system. Installing the update You must upgrade each node of the cluster.
Changes after the upgrade
After a successful upgrade of KSMG to version 2.1.1, the following changes occur on the nodes:
The web interface of the node is upgraded, the application version is changed. The link to the KSMG 2.1.1 online help is updated. New application functionality is added on the Control node of the cluster in all localization languages. The previously added license key is applied. The following data are kept:Messages in Backup Email traffic processing events Data in the Dashboard section Messages in Quarantine User accounts and roles Application settings Web interface certificate Rules KPSN settings Local administrator password KATA certificates The following data are removed:Application events Database upgrades LDAP cache data KSN settings KSN cache data Recommendations
To avoid data loss, please do the following:
Manually update the databases after each installation of the update package on a node. If necessary, configure the publishing of application events to the SIEM system from scratch. If necessary, configure from scratch the settings of the snmpd service for interaction with an external monitoring system via the SNMP protocol. If necessary, recreate the settings of the application that require editing KSMG configuration file templates.
Page top