the-exe.org just another blog

Symptom: After updating NVC to NEM the Exchange IS is not starting
Problem:The NVC had a flag set if the NVC was on the same server as Exchange. If this flag is set and NVC is no longer available, Exchange cannot start the informationstore.
SolutionTo fix this issue, go to the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\VirusScan

Change the value from 1 to the following:

Key: Enabled
Type: REG_DWORD
Value: 0

written by eXe \\ tags: Exchange IS, Exchange NVC Migration, Norman Endpoint Protection, Norman NEM, NVC NPRO

Since Norman released their latest security Product a few weeks ago, I had several problems when deploying client files from Norman Endpoint Manager to another Server.

After initializing the Push Installation on the Endpoint Manager, Zanda.exe and zlh.exe appear on the remote Server. But even after a few minutes there was no change of it’s state. The zlh.exe process is beeing closed and zanda.exe does not seem to be working anymore.

In fact Norman has a built in delay to start finalizing the installation. This delay should be set to 15 minutes by default, so the network is not blocked by the high load generated when distributing files. If you want to see if zanda is still working, open the eLogger.exe. You can find it in your Norman directory in the subfolder \Npm\Bin\ if you start the eLogger.exe you will see what Zanda is doing.

If you want to immediately start zanda to update, open a command line prompt and enter the following command:

zanda /updatenow

zanda will update now and you will see the information in the eLogger window. If the update is over, you will get the message in eLogger. Then it might take some time for zanda to start the norman services.

All the above information can be found in the norman support issue archive.

Link to original article: here

written by eXe \\ tags: installation does not continue, NEM, Norman Endpoint Manager, Norman Endpoint Protection, Norman remote installation