Article ID: 9753, created on Feb 28, 2011, last review on May 10, 2014

  • Applies to:
  • Operations Automation 5.1
  • Operations Automation 5.0

Resolution

Dr.Web version 4.44 products are no longer supported starting from January 31, 2011. This means that no updates of virus databases and program modules for version 4.44 will be released. Therefore, starting from POA 5.2, Dr.Web version 4.44 is not supported; Dr.Web version 5.0.1 is available instead. At the same time, if Dr.Web version 4.44 is used in POA 5.1, it will still be available after upgrading to POA 5.2. In this case, Dr.Web should be upgraded to version 5.0.1.

Dr.Web 5.0.1 can be deployed on CentOS/RHEL 5 only. Thus, if you have Dr.Web running on Fedora 1, Fedora 3, RHES 3, or RHES 4 machines and want to upgrade Dr.Web to version 5.0.1, you should migrate your Dr.Web installations to CentOS/RHEL 5. Below are the instructions on how this should be done (assuming that you have only one Dr.Web instance):

  1. Choose the machine with CentOS/RHEL 5 installed where drweb_daemon service will be hosted. Register the machine in POA if it is not registered yet. Install the drweb_daemon 5.0.1 service package on this machine.
  2. Go to the "System Emails" tab of the DrWebFilter application, click "Edit," and click the "Submit" button. This will schedule the DrWebFilter configuration update. Ensure that the newly created task "Dump config of DrWeb filter service" has been executed successfully. This step should be performed for each DrWebFilter instance.
  3. Remove the old drweb_daemon package.
  4. Repeat step (2).
It is important to note that while performing the described upgrade procedure, antivirus protection stays active almost the entire time, except, perhaps, in between steps (3) and (4) when one of the registered drweb_daemon services does not exist.

Unfortunately, an automated upgrade from Dr.Web 4.44 to 5.0.1 is not possible, even if you are already running drweb_daemon service on CentOS/RHEL 5 machines. There are two alternative ways to upgrade. The first one is to perform the steps described above for existing Fedora 1, Fedora 3, RHES 3, or RHES 4 installations (move drweb_daemon service installation to another node). The second way is described below (it is assumed that you have only one Dr.Web instance):

  1. Remove the old drweb_daemon service.
  2. Install the new drweb_damon service.
  3. Go to the "System Emails" tab of the DrWebFilter application, click "Edit," and click the "Submit" button. This will schedule the DrWebFilter configuration update. Ensure that the newly created task "Dump config of DrWeb filter service" has been executed successfully (Task Manager -> Task Log). This step should be performed for each DrWebFilter instance.
In this case, antivirus service will be down during the entire upgrade procedure. You can avoid this if there are at least two drweb_daemon instances available before performing the upgrade and you upgrade them one after the other. (Perform steps 1, 2, and 3 as described above for each drweb_daemon installation; one drweb_daemon installation will be available for the entire time of the upgrade). Therefore, it would be good to introduce a temporary drweb_daemon service installation if only one is available.

Dr.Web license issues

Dr.Web allows you to "reuse" the license after upgrading. The license for Dr.Web 4.44 works fine for the 5.0.1 version as well. The license file is kept on the machine upon drweb_daemon service removal. You should not do anything with the license if you upgrade drweb_daemon service on the same machine. However, do not forget to install the license for new Dr.Web installations.

c27596ac4fff6cb4c8ec8891dae57001 5356b422f65bdad1c3e9edca5d74a1ae 25ba5a02b9d70d4212e34c355e881968 2554725ed606193dd9bbce21365bed4e caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF