Norman Email Protection Upgrade Checklist

Problem description

This support article is intended for existing Norman customers who are currently running an older version of Norman Email Protection (NEP). You should read this document thoroughly before upgrading. If you have any questions or feel something is missing from this document, feel free to contact technical support:


Before upgrading, please ensure that you have met the following requirements:


  • Backup your databases (QT, Audit, Monitoring and Sieve) before launching the upgrade
  • Ideally, this should be a full backup
  • If you are using SQL Server Express, ensure that Full Text Indexing is installed
  • Ensure that .Net 3.5 Framework is installed
  • Ensure that you have your current installation package
  • In the event that you must roll back after upgrading, keep a copy of the *.exe installation file
  • If you do not have a copy of the file, before upgrading, contact technical support:
  • Backup your Windows Registry
  • On the NEP server, click on Start > Run
  • Type regedit to open the Registry Editor
  • In the Registry Editor, click on File > Export
  • Select the file location, enter a name for the backup file and click OK
  • Backup any customized quarantine reports and/or web applications folders
  • Read the Release Notes for all new features and changes to modus, especially the section regarding encryption

If you opt to use encryption, there is a sieve script that must be added to prevent issues with foreign languages for outbound messages. This script is included in the Release Notes.


Upgrading NEP to v5.61

         Due to a series of architectural changes in versions upgrading from version 4.7 must be done in two steps:

        1. upgrade from v4.7 to v 5.0 or v5.1

       2. upgrade directly to v5.61

If you are running any version higher the 5.1 you can directly upgrade to v5.61.


Changes to the installation process:

         Starting from v5.42 NEP comes with a new web interface. The new interface will not overwrite your existing WebQuarantine programs. This will allow you to continue using the 'old' site until you have had time to test and/or customize the new one.


NEP Web Quarantine information:

         There will be a new folder created called WebQuarantine locate under C:\Program Files(x86)\Norman\Web. This folder will contain the new websites attributes for the new web quarantine pages. The virtual directory will still exist in IIS.



          If you plan to use the monitoring feature, it is preferable to use a Microsoft SQL database instead of the native Access format. Whether to use Microsoft Access or Microsoft SQL depends on your volume of traffic. A good rule of thumb would be to use your quarantine database as your guide: if you use SQL for the quarantine, then you should use it for the monitoring stats as well.


Upgrading NEP

Upgrading requires a certain number of precautions. The most important is doing a backup before upgrading:

  • Make sure you have access to your old NEP installation package in case you need to rollback. If you do not have a copy, click on the help -> about button in your NEP console to find out what version you have and the build number; contact us by email, and we will be happy to provide you with the original install package.
  • Backup your configuration: - Open the NEP administration console and select File > Backup configuration - Select the path where the configuration file will be stored (*.reg file) - Keep this registry file (*.reg) in a safe location as a backup of your NEP configuration.
  • Backup the Registry: - Open the Registry Editor (regedit) - Click on File > Export
  • Select the file location, enter a name for the backup file and click OK
  • Backup the Web directory: Located under...\Norman\Web
  • Backup the databases: Normally located under the root installation of SQL \\Microsoft SQL Server\MSSQLXX.SQLEXPRESS\MSSQL\DATA
  • Proceed with the upgrade.

Date Published: 2014.08.15   Date Updated: 2014.08.15