Skip to main content

Upgrade Procedure

This topic provides the basic steps needed to upgrade StealthINTERCEPT 7.3.7+. For older versions, please reach out to Netwrix Support for assistance.

NOTE: By design, the Threat Prevention 7.4 server (Enterprise Manager) will not accept connections from pre 7.3.9 Agents. Existing customers must upgrade to 7.3.9 first. Else pre 7.3.9 Agents will be orphaned.

Typically a new release includes new policy templates. The Templates Update window displays the following message after an update: “Changes to Default Templates Detected. Do you want to update Templates?” Click Yes to import or No to skip. See the Upgrade Policy Templates topic for instructions on importing these templates if you selected No during the upgrade process.

See the What's New topic for details on new and improved features included with each release.

Considerations​

The upgrade process must be done on all servers where the Threat Prevention Infrastructure is installed as well as all systems where the Agent is deployed. For deploying Agents, see the Agents Interface topic.

RECOMMENDED: It is a best practice to export policies for backup prior to performing an upgrade.

For NAS file system monitoring, Threat Prevention works in conjunction with the Activity Monitor. Hence, the agent versions for the two products must be compatible. See the NAS Device Support topic for information on version compatibility.

Infrastructure Upgrade Procedure for 7.4.x to 7.4.x​

You can upgrade from an earlier Threat Prevention 7.4 build to a later build of the same version.

Follow the steps to install a later build of the same version.

Step 1 – Uninstall the current Threat Prevention build.

  • Do not make any changes to the database. The database schema is automatically upgraded.
  • Do not manually delete any other files post uninstall.

Step 2 – Install the newer build to the same location as the previous build. See the Application Server Install topic for additional information.

Infrastructure Upgrade Procedure for 7.3.9 to 7.4​

Follow the steps to upgrade from StealthINTERCEPT 7.3.9 to Threat Prevention 7.4.

Step 1 – Uninstall the existing StealthINTERCEPT server.

  • Do not make any changes to the existing StealthINTERCEPT database. The database schema is automatically upgraded.
  • Do not manually delete any other files post uninstall.

Step 2 – Install the Threat Prevention 7.4 infrastructure using the "Database Login Information" for the existing StealthINTERCEPT database. See the Application Server Install topic for installing v7.4.

The installer will look for the CertsInfo folder at the old SI 7.3.9 path and copy the needed files to the new Certsinfo folder, available at the following path in Threat Prevention 7.4:

...\Netwrix\Netwrix Threat Prevention\SIEnterpriseManager\

Verify that the post install Certsinfo folder contents have been copied from SI 7.3.9 (check file dates). If not, manually copy the files from the old to the new path. Else 7.3.9 Agents will be orphaned.

Step 3 – Use the Agents Interface in the 7.4 version to upgrade the Agent.

See the Upgrade Agent topic for additional information. See the Manual Uninstall on the Agent Server topic for information on removing the Agent from the server where it was deployed.

NOTE: If you are running a previous version of the Agent, you must first upgrade it to 7.3.9 and then to 7.4.

Infrastructure Upgrade Procedure for 7.3.7 to 7.3.9​

Follow the steps to upgrade from StealthINTERCEPT 7.3.7+ to 7.3.9.

Step 1 – Uninstall the existing StealthINTERCEPT server.

  • Do not make any changes to the existing StealthINTERCEPT database. The database schema is automatically upgraded.

Step 2 – Install the StealthINTERCEPT infrastructure for the newer version, using the "Database Login Information" for the existing StealthINTERCEPT database. See the Application Server Install topic for additional information.

Step 3 – Use the Agents Interface in the 7.3.9 version to upgrade the Agent.

See the Upgrade Agent topic for additional information. See the Manual Uninstall on the Agent Server topic for information on removing the Agent from the server where it was deployed.