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: http://www.norman.com/home_and_small_office/contact_us
Before upgrading, please ensure that you have met the following requirements:
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 requires a certain number of precautions. The most important is doing a backup before upgrading: