Norman Email Protection (NEP) can be installed with any third party anti-virus product as long as exclusions are set to skip scanning the following folders:
- The spool folder and its its subfolders
- The mailbox\@quarantine folder and its subfolders
- The Sieve data folder
- The Norman Email Protection root installer folder. i.e: C:\Program Files\Norman\Norman Email Protection
When Norman Email Protection is first installed, it creates a registry key in HKLM\Software\Norman Data Defense Systems\RootPath which points to the Norman Email Protection default folder, typically C:\Program Files\Norman\Norman Email Protection. When Norman Endpoint Protection is installed after, it changes that key to point to its default location, C:\program files\Norman.
ModusAdm.exe service still attempts to download updates in the usual manner, however, due to the installation of Norman Endpoint Protection, it will attempt to do this in the wrong location. When Moduscan starts it calls NrmQueryNormanPath which will now point to a Norman folder instead of Norman Email Protection. As a result, we are unable to unzip the contents after the download and therefore become stuck in a download loop which means that Norman Email Protection never gets virus updates. In this scenario you should see the avupdate.exe process running in task manager.
Norman Email Protection has to be reconfigured to let Norman Endpoint Protection do the downloading. To do this, follow the steps below:
- Update HKLM\Software\Vircom\Vopmail\VirusEnginePathNorman to C:\Program Files\Norman\Nse\Bin (ie. the location where Norman Endpoint Protection is downloading the definitions. There should be nse_w32.dll, nvcbin.def and nvcmacro.def there)
- Add HKLM\Software\Vircom\VopMail\VsOwnNorman DWORD key with a value of 0.
This tells ModusAdm.exe not to contact the Vircom update server and that Norman Endpoint Protection will take care of the updates
- Restart Moduscan