How do I manually upgrade to the latest MetaDefender Core version?

Windows (Standalone DB mode)

To perform a MetaDefender Core Deployment Upgrade, please follow the steps below:

  1. Browse $link[page,314800,Release Notes] for details on the latest %product_name% version release.
  1. Visit My OPSWAT to download the latest %product_name% version for Windows.
  1. Log in as Admin user on the %product_name% server, then Run the installer file.
  1. Let the MetaDefender Core Setup Wizard guide you through the process.
  1. If you are upgrading from a prior release, ensure you use the Config Export/Import feature, as illustrated below $link[page,314775,Read This to learn more].

With the help of this feature, and provided no errors occur during the upgrade process, your configurations and licensing information will be fully preserved through the upgrade process.

  1. Once installed, click the %product_name% icon to log into the Management Console and verify that the system is functioning as expected.
  1. In the Console, open Inventory>Modules to view the status of your module and engine downloads.
  1. Once all your required modules are up-to-date and enabled, and your Security Policies configured, drop a test file in the Process field to run your first scan.

Windows (Standalone DB mode) command line

%product_name% supports two modes to setup PostgreSQL server:

  1. Local PostgreSQL Server
  2. Existing PostgreSQL Server

Local PostgreSQL Server

Here, %product_name% will install a new PostgreSQL server locally, alongside the product.

A sample ignition file for PostgreSQL server’s information is shown below. Note that only non-Unicode characters are supported for both user and password.

On Windows systems, it is possible to install %product_name% by running the corresponding .msi file. This can be done via command line by executing the following command.

Where the <option keys>, their default values and their descriptions are as follows:

Existing PostgreSQL Server

Here, %product_name% will connect to a pre-installed PostgreSQL server, running remotely, before setting up its database.

Be sure to follow the $link[page,314818,Open Connection steps on PostgreSQL server] first, so that your existing remote PostgreSQL server is ready to accept the upcoming connection from %product_name%.

A sample ignition file for PostgreSQL server’s information is shown below.

On Windows systems, it is possible to install %product_name% by running the corresponding .msi file. This can be done via command line by executing the following command.

Where the <option keys>, their default values and their descriptions are as follows:

Windows (Shared Database mode)

To perform a MetaDefender Core Deployment Upgrade, please follow the steps below:

  1. Browse $link[page,314800,Release Notes] for details on the latest %product_name% version release.
  1. Visit My OPSWAT to download the latest %product_name% version for Windows.
  1. Log in as Admin user on the %product_name% server, then Run the installer file.
  1. Let the MetaDefender Core Setup Wizard guide you through the process.
  1. If you are upgrading from a prior release, ensure you use the Config Export/Import feature, as illustrated below $link[page,314775,Read This to learn more].

With the help of this feature, and provided no errors occur during the upgrade process, your configurations and licensing information will be fully preserved through the upgrade process.

  1. For Shared Database mode, the same upgrade instructions apply as described above for Standalone mode, with one exception: at the Setup stage illustrated in the screenshot below, you will need to specify your current PostgreSQL server IP address.
  1. Once installed, click the %product_name% icon to log into the Management Console and verify that the system is functioning as expected.
  1. In the Console, open Inventory>Modules to view the status of your module and engine downloads.
  1. Once all your required modules are up-to-date and enabled, and your Security Policies configured, drop a test file in the Process field to run your first scan.

Windows (Shared Database mode) command line

%product_name% supports two modes to setup PostgreSQL server:

  1. Local PostgreSQL Server
  2. Existing PostgreSQL Server

Local PostgreSQL Server

Here, %product_name% will install a new PostgreSQL server locally, alongside the product.

A sample ignition file for PostgreSQL server’s information is shown below. Note that only non-Unicode characters are supported for both user and password.

On Windows systems, it is possible to install %product_name% by running the corresponding .msi file. This can be done via command line by executing the following command.

Where the <option keys>, their default values and their descriptions are as follows:

Existing PostgreSQL Server

Here, %product_name% will connect to a pre-installed PostgreSQL server, running remotely, before setting up its database.

Be sure to follow the $link[page,314818,Open Connection steps on PostgreSQL server] first, so that your existing remote PostgreSQL server is ready to accept the upcoming connection from %product_name%.

A sample ignition file for PostgreSQL server’s information is shown below.

On Windows systems, it is possible to install %product_name% by running the corresponding .msi file. This can be done via command line by executing the following command.

Where the <option keys>, their default values and their descriptions are as follows:

Linux (Standalone mode)

To perform a MetaDefender Core Deployment Upgrade, please follow the steps below:

  1. Browse $link[page,314800,Release Notes] for details on the latest %product_name% version release.
  1. Visit My OPSWAT to download the latest %product_name% version for your Linux distro.
  1. Log in as Root user on the %product_name% server, then Run the installer file.
  1. Depending on your distro, Software Install or a similar utility will guide you through the process.
  2. If you are upgrading from a prior release, ensure you use the Config Export/Import feature, as illustrated below $link[page,314775,Read This to learn more]. With the help of this feature, and provided no errors occur during the upgrade process, your configurations and licensing information will be fully preserved through the upgrade process.
  1. Once installed, click the %product_name% icon to log into the Management Console and verify that the system is functioning as expected.
  2. In the Console, open Inventory>Modules to view the status of your module and engine downloads.
  1. Once all your required modules are up-to-date and enabled, and your Security Policies configured, drop a test file in the Process field to run your first scan.

Linux (Standalone mode) command line

- 1. Log into the terminal as Root user. 2. Create an ignition file (if one does not already exist) via command line by running the following command: touch ometascan.conf 3. Now, run: nano ometascan.conf to edit the file with the necessary information. 4. An example of an ignition file is shown below.

  • Linux: /etc/opswat/ometascan.conf

%product_name% supports two modes to setup PostgreSQL server:

  1. Local PostgreSQL Server
  2. Existing PostgreSQL Server

Local PostgreSQL Server

Here, %product_name% will install a new PostgreSQL server locally, alongside the product.

A sample ignition file for PostgreSQL server’s information is shown below. Note that only non-Unicode characters are supported for both user and password.

Finally, enter the relevant command from the table below to install %product_name%.

Existing PostgreSQL server

Here, %product_name% will connect to a pre-installed PostgreSQL server, running remotely, before setting up its database.

Be sure to follow the $link[page,314818,Open Connection steps on PostgreSQL server] first, so that your existing remote PostgreSQL server is ready to accept the upcoming connection from %product_name%.

A sample ignition file for PostgreSQL server’s information is shown below.

Finally, enter the relevant command from the table below to install %product_name%.

Linux (Shared Database mode)

To perform a MetaDefender Core Deployment Upgrade, please follow the steps below:

  1. Browse $link[page,314800,Release Notes] for details on the latest %product_name% version release.
  1. Visit My OPSWAT to download the latest %product_name% version for your Linux distro.
  1. Log in as Root user on the %product_name% server, then Run the installer file.
  1. Depending on your distro, Software Install or a similar utility will guide you through the process.
  2. For Shared Database mode, the same upgrade instructions apply as described above for Standalone mode, with one exception: during setup, you will need to specify your current PostgreSQL server IP address.
  3. If you are upgrading from a prior release, ensure you use the Config Export/Import feature, as illustrated below $link[page,314775,Read This to learn more]. With the help of this feature, and provided no errors occur during the upgrade process, your configurations and licensing information will be fully preserved through the upgrade process.
  1. Once installed, click the %product_name% icon to log into the Management Console and verify that the system is functioning as expected.
  2. In the Console, open Inventory>Modules to view the status of your module and engine downloads.
  1. Once all your required modules are up-to-date and enabled, and your Security Policies configured, drop a test file in the Process field to run your first scan.

Linux (Shared Database mode) command line

  1. Log into the terminal as Root user.
  2. Create an ignition file (if one does not already exist) via command line by running the following command: touch ometascan.conf
  3. Now, run: nano ometascan.conf to edit the file with the necessary information.
  4. An example of an ignition file is shown below.

Linux:/etc/opswat/ometascan.conf

%product_name% supports two modes to setup PostgreSQL server:

  1. Local PostgreSQL Server
  2. Existing PostgreSQL Server

Local PostgreSQL Server

Here, %product_name% will install a new PostgreSQL server locally, alongside the product.

A sample ignition file for PostgreSQL server’s information is shown below. Note that only non-Unicode characters are supported for both user and password.

Finally, enter the relevant command from the table below to install %product_name%.

Existing PostgreSQL Server

Here, %product_name% will connect to a pre-installed PostgreSQL server, running remotely, before setting up its database.

Be sure to follow the $link[page,314818,Open Connection steps on PostgreSQL server] first, so that your existing remote PostgreSQL server is ready to accept the upcoming connection from MetaDefender Core.

A sample ignition file for PostgreSQL server’s information is shown below.

Finally, enter the relevant command from the table below to install %product_name%.

Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
Next to read:
What is the latest MetaDefender Core version?
On This Page