Proactive IT security

Norman Endpoint Manager management console is sluggish and unresponsive

Date published: 2009-11-10
Date updated: 2010-04-15
Product: Norman Endpoint Protection, Norman Endpoint Protection
Module: Installation, Distribution, Upgrade
Operating system: Windows 2003 Server, Windows 2008 Server

Problem description

Norman Endpoint Manager (NEM) management console is sluggish and unresponsive. I see several Nise too busy messages in Elogger (norman\npm\bin\elogger.exe). Some or several clients are not able to communicate with the NEM server.

Problem solution

The Endpoint Manager has been tested to support 15000 clients for policy management and status reporting, but will vary with what kind of platform it is hosted on.

The testing was performed with no distribution of software updates being done. Update distributions are very bandwidth- and cpu intensive. In larger networks, it is crucial that the policies specify an alternate update path that points to a separate file share where the updates are placed.

The system has been designed to support a hierarchy of NEM distribution points. In the initial versions, however, we only support a single NEM for a realm, and hence have to use an alternate update path when the clients get into the hundreds.

To set up an alternate update path, please follow these instructions:

  1. Open the policy for the group of clients that are going to use an alternate update path
  2. Choose Configure Product Manager
  3. Choose Select update method
  4. Select Use alternate update path
  5. Fill in the path, username and password.
    Note! Please use the following syntax for path: \\servername\norman\distrib\download
  6. Create a script that (x)copies all files from \norman\distrib\download on the NEM server to \\servername\norman\distrib\download 
  7. Set up a scheduled task that runs the script once every hour.
    Note! The script must be run with user access rights to access the share, so that it is run even if no users are logged on.
    It may be wise to check the option to kill the process if it has run more than two hours.

The script needs to do the following:

  1. Verify that Norman Internet Update is not currently running
  2. Copy all files from \norman\distrib\download on the NEM server to \\servername\norman\distrib\download 
  3. If there is a sharing violation during file copy, wait a while and try again

We have already created a script for this that can be downloaded from the link below. To use this script all you need to do is edit the localpath and remotepath values to point to the correct locations.

Type Title Comment Usage
Example script May be used as a basis for your own script Software