Upgrading from Protection Engine 7.5.x to 8.2
search cancel

Upgrading from Protection Engine 7.5.x to 8.2

book

Article ID: 206934

calendar_today

Updated On:

Products

Protection Engine for Cloud Services Protection Engine for NAS

Issue/Introduction

You need to upgrade from Symantec Protection Engine (SPE) 7.5.x to SPE 8.2

Resolution

Direct upgrade to SPE 8.2 is not supported. In most cases, the best course of action is to perform a fresh installation and review settings due to the significant changes between 7.5.x and 8.2. We recommend this course of action.

If upgrading and preserving your settings is necessary, you will need to migrate to SPE 7.9 first and then upgrade to SPE 8.2. The following instructions explain the steps to do this.

Upgrading a Single Server

  1. Migrate your server to 7.9.0 using the migration instructions. This should preserve all the settings from the current install.
  2. After the migration to 7.9.0 is complete, run the SPE 8.2 installer and select the option to upgrade and preserve settings.
  3. Once 8.2 is installed, enroll the scanner in the centralized console.
  4. Add the scanner to a scanner group
  5. Create a policy that mirrors the settings on that scanner by importing the scanners settings.

Upgrading Multiple Servers

  1. Choose a single server and perform the steps to upgrade a single server. After following these steps, you'll have a policy that can be applied to other scanners, without the need to perform an upgrade/migration on those scanners.
  2. Remove SPE and perform a clean install of 8.2 on all other scanners.
  3. Enroll the scanners in the centralized console.
  4. Once the 8.2 scanners are enrolled, add them to the scanner group.
  5. Once the scanner group is populated with all the scanners, apply policy you created when migrating the to the scanner group, which will deploy the policy to all the scanners in that group.

Additional Information

If there are conflicts between the cloud console and any local settings, the cloud console settings will be applied. If there are settings that are unavailable in the cloud console, then those settings will not be overwritten locally.