Upgrading to Symantec Protection Engine 9.1.0
Supported upgrades describe the upgrade path that Symantec Protection Engine 9.1.0 supports.
Previous version number | Description |
|---|---|
9.0.x | Symantec Protection Engine 9.1.0 supports an upgrade from version 9.0.x. You can choose to upgrade the product and preserve your existing settings or perform a clean upgrade. If you choose to do a clean upgrade, the installer removes the previous version, and then installs the newer version as a full installation, without preserving any previous settings. |
8.2.x | Symantec Protection Engine 9.1.0 supports an upgrade from version 8.2.x. You can choose to upgrade the product and preserve your existing settings or perform a clean upgrade. If you choose to do a clean upgrade, the installer removes the previous version, and then installs the newer version as a full installation, without preserving any previous settings. |
Cross SKU upgrades are not supported, that is, previous installation of SPE for Cloud Services can only be upgraded to SPE for Cloud Services. Similarly, previous installation of SPE for NAS can only be upgraded to SPE for NAS.
The URL filtering capability of Symantec Protection Engine (SPE) was powered by RuleSpace until SPE 8.2. From SPE 8.2.1 onwards, SPE uses the WebPulse technology for URL filtering. Since WebPulse has different URL category names than RuleSpace, the categories you selected from the RuleSpace list before upgrading will not be preserved after you upgrade to SPE 8.2.1.
About report.xml
A report.xml file maintains different types of violations and file scan statistics since you have installed SPE. It also contains the SPE details like version, platform, licensing details, definitions dates, and their versions.
During the preserve settings upgrade, SPE takes a backup of the
report.xml
file on the disk. However, it does not use the file after the upgrade and does not use the related data to show any pre-upgrade statistics in the SPE console.SPE keeps the
report.xml
backup to make sure that you do not lose any historical data and can refer to the file in case you need to check out the past scan statistics.If you are using SPE with old web-based console or in core server mode and now you want to use the new SPE console
The preserve settings upgrade option lets you retain the existing Symantec Protection Engine policies. After the upgrade if you want to add your SPE instance to the new SPE console, the SPE console applies the policy of the scanner group to which the SPE instance is added.
In the new SPE console, the upgraded SPE preserved policies are overridden with the scanner policy of the group.
You can prevent this issue if you migrate the preserved SPE policies to the scanner group of the new console first, and then add your Symantec Protection Engine instance to the scanner group.To migrate the preserved SPE policies to the scanner group of the new console, use the following steps:
- Log in to the SPE console and click onScannersin the top pane.
- Click onNew Group...to create a scanner group. For example, custom_scanner.

- Go to the machine on which you have installed the new SPE console, open the command prompt, and then navigate to the bin folder of the SPE console.Default bin folder -C:\Program Files\Symantec\Scan Engine Console\CMaF\bin.
- Now, execute theCwpMigrationUtil.exeto import the SPE server whose settings you want to apply to the scanner group. Usage:CwpsMigrationUtil.exe GroupName ServerIP Port UserName Password SSL.