1. Introduction

• network administrator’s management options of NOD32 Antivirus System
• fast, straightforward and efficient update and upgrade of the system (for both network and single-user installations)

• Fully automatic (and/or ”a click away”) update of the system from a predefined (internet, intranet, LAN, or even CD) server. No user manipulation with the update files is necessary. (For details on initial setup of the system, please, see chapter 2.)
• Increased frequency of updates supported. Based on closely monitored virus situation world-wide, immediate update (daily if necessary) is feasible.
• Increased speed of the update process by an order of magnitude. Update time is reduced to minimum. Virus definition updates are transferred via an incremental update file. Download of the current update file is all that is required to update the system, even if the previous updates were, for any reason, missed. The size of the update file is limited to ”reasonable” size, typically less than 100 kB.
• Immediate effect of the update: New virus databases are used immediately after they were downloaded, no restart of a particular computer is necessary. If the resident protection module (Amon) is running, it has immediate access to the updated virus databases (no restart necessary).
• Update management features for network administrators. Control Center is an easy to use multi-level management tool for update management in network environment.
• Incident reporting: easy management of incident/event reports sent to system administrator automatically. Reports can be sent to multiple recipients. Eset support and analysis available.
• Two levels of updates/upgrades: a/ virus signature update and, b/ sytem application environment upgrade (system restart required).
   

2. Setup of the Automatic Update - Stand-Alone Computer

1. Automatic Update - Stand-Alone Computer Connected to Internet
   • Who should use this setup
     This setup is for a standalone computer with internet connection
   • Setup outcome
   • This setup will enable a licensed computer to monitor availability of new updates and/or immediate update of NOD32 Antivirus System from the Eset server.
   • How to setup your computer (Note: When NOD32 program is run for the first time, the user is prompted to setup the system.)
     1. Click at NOD32 Control Center icon (CC) located on the main system taskbar. Main setup window of NOD32CC will open. Make sure the Update Tab is selected.
     2. Keep the default server name www.nod32.com intact. Enter your private username and password. The username and password was assigned to you after you purchased the program license. Select the Save password checkbox.
     3. Click at Connection Setup button. If you use modem Internet connection, select the Dial-up option. If you use fixed (leased) line or LAN, select LAN/Fixed line option. Click at OK button to confirm your selection.
     4. You may also set one of the three available Update options:

• Minimum – this type of update provides actualization of the system so that its virus detection capabilities were current. The files having no direct influence on the detection capabilities (e.g. application environment) are not updated unless they are necessary to secure the functionality of the core of the system. This option may be a good choice for a limited transfer rate capacity (such as cellular phone modem connection).
• Full – all files with available update will be updated. This will be a preferred option for computers connected to Internet via a leased line, LAN or those updated by means of a CD-ROM.
• Ask – in this case, a user has full control over the update process. Detailed information on a particular update is displayed and the user is prompted to select a specific update scenario. This update option is appropriate for those users who wish to have full control in the update process, and it can also be used when the connection to the update server is very slow, since less frequent update can be selected. An update of both virus database and application environment is equivalent to a Full update scenario.
1. Finally, you may want to check the Automatic Update option and enter the corresponding time of update frequency. Alternatively, manual update – Update Now can be selected to trigger the update process right away.
    
2. Setup of the Automatic Update - Stand-Alone Computer Without Internet Connection
   This type of setup is used when no internet connection is available and/or the user selects to install new update on a particular computer by means of a CD-ROM/LAN, as an alternative option.
   1. Click at NOD32 Control Center icon located on the main system taskbar. Select the Update Tab (usually offered as a default option)
   2. Select the CD-ROM drive from the available list of servers (your computer has to have one installed).
   3. Click at Connection Setup button. Select None and confirm selection by clicking at OK button.
   4. Select the Update method. It is recommended that you select Full in this case. For details on Update method, please, see section 2.1 of this manual.
   5. Insert the update CD into the CD-ROM drive and click at the Update Now button.

3. Setup of the Automatic Update in Computer Networks

Although the NOD32 Control Center is very useful tool for a stand-alone computer, its application potential in computer network environment acquires new meaning. Automatic Update of NOD32 in a network environment can be set in such way that the whole process can be controlled and managed by a single network administrator. This is achieved by means of a ”mirroring” mechanism, a process of creation of a certain number of the update copies. NOD32CC (in charge of the process controlled by the system administrator) has to be installed in the administrator mode. After the mirror parameters were set up (by the network administrator) and the update process was executed (triggered manually or automatically), the mirror-generating computer/s is/are updated and the copies of the update file/s are created on the predefined locations available for all network users.

NOD32 provides scalable solution and, hence, can be applied for different sizes of computer network. This chapter is divided into several sections, providing installation instruction for both smaller and large networks. (see sections 3.1 and 3.2). Information on the client computer setup is presented in section 3.3. Finally, the use of the Configuration file is discussed in section 3.4.

Trial installation of NOD32CC on a limited number of computers is recommended. If the automatic update is set up correctly, the following message will be displayed on a particular (trial) computer after clicking at the Update Now button: ”Current version of NOD32 system available on this computer. No Update necessary.” On the other hand, if the current NOD32 version installed on a trial computer is older than the one available for update, the update process should commence.
 

1. Automatic Update - Small Computer Network
   This type of update will typically be used in a network environment managed by a single network administrator. Network administrator sets up the NOD32CC parameters to automatically download the update files and create the copies of the update files in a predefined directory. All client computers within a particular network will subsequently be updated using the update files in the aforementioned, predefined directory. (NOTE: If the directory for update files (mirror) is selected on a machine with NOD32 Control Center installed in the administrator mode, do not select (for the location of the mirror) the UPDATE directory - located in the Eset directory.)

   In general, the network administrator has two basic options:

   • NOD32 with its administrator’s Control Center will be installed on a computer (server) and the copies of the Update files (serving as the update source for other network computers) will be stored on this server (see Case 3.E.1 bellow)
   • NOD32 with its administrator’s Control Center will be installed on a ”non-server” computer. Control Center will create update mirrors (update files) on a server and all network computers will update their NOD32 systems from the server. In this latter case, the server serves as a storage media for the mirrors and NOD32CC is not running on the server. (see Case 3.E.2 bellow)

   
   Setup of the Automatic Update in a small network:

   1. In the first step, the network administrator will select a computer within the network with Windows 95 / 98 / ME/NT/2000 operating system. The selected computer will (after proper installation – see below) run NOD32CC in the administrator’s mode. Install (or reinstall) of the NOD32 system will be performed on computer selected. During the (re)installation, the process of creation of the update copies is enabled by selecting the option: I want to install support for creation of Update copies in LAN (for network administrators). This option appears before the installation is completed and, as a result, installed version of NOD32CC runs in the administrator’s mode. In the case, when NOD32 system is being reinstalled, the checkbox: I want to change other settings too(automatic Update, automatic execution of Amon...) needs to be selected. Consequently, the setup program prompts the user to change the current program settings. Since, NOD32CC, after this (re)installation runs in the administrators mode, a new button – Mirror Setup, located in the Update Tab of the main panel of the Control Center will appear. Creation of the update copies and the details of this process are set in a window that opens after clicking at the Mirror Setup button.
   2. New, NOD32 Control Center Icon appears on the main system taskbar after the installation described in the previous section. To start the setup process of the NOD32CC module, click at the Control Center icon. Two main features need to be selected to run the Control Center properly:
      • Setup of the parameters/options for creation of the Update copies (mirror) pursuant to applicable situation described in section 3.E.1 or 3.E.2. Follow the steps described therein to set the parameters for creation of the mirrors/update files.
      • Setup of the downloading parameters controlling creation of the update copies for the network administrator as specified in chapter 2.1 and/or 2.2.
   3. Create the update files (mirror) clicking at Update now button located in the Update Tab.
   4. Finally, follow instructions in section 3.3 to set up NOD32CC parameters for the network end-users.

Case 3.E.1
1. Each administrator will have to replace the parameters used by an alternative options, applicable for his particular situation. For example, let us assume that the name of the administrator’s computer is ADMIN_C and the shared disk is the D: drive. The assumed name of the shared disk is D-DISK. Let us further suppose that the name of the directory on drive D:, used to save/store all the update files will be NOD_UPD. This directory needs to be created manually.
2. Click at the Mirror Setup button and enter the Path for updates of the copies as follows:
   D:\NOD_UPD
3. In the entry line for Access path for clients enter:
   %CurrentPath%
   or, more specifically:
   file://ADMIN_C/D-DISK/NOD_UPD
4. Keep the Username and Password blank since you will not need them to access your local disk when saving the mirror.
    
Case 3.E.2
1. Each administrator will have to replace the parameters used by an alternative options, applicable for his particular situation. In this example, let us assume that the administrator’s computer name is: ADMIN_C and the server name (computer where the mirrors will be saved/stored) is: SERVER_C. Further, let us assume that the access to a shared disk E: (located on the server) is via the name: E-DISK. Let the directory (located on disk drive E:) where the updates will be saved is NOD_UPD. As in the previous case, this directory needs to be created manually.
2. Click at Mirror Setup button and enter the Path for updates of the copies entry as follows:
   \\SERVER_C\E-DISK\NOD_UPD
3. In the entry line for Access path for clients enter:
   %CurrentPath%
   or, more specifically:
   file://SERVER_C/E-DISK/NOD_UPD
   Hence, you may use the select the Use the same path for clients checkbox.
   Do not use the access via mapped disks. NOD32CC runs under different account (LocalSystem) on Windows NT and Windows 2000 platforms. This account does not recognize the mapping information of a currently logged user. In addition, each user can have different mapping. It is more convenient to use the UNC path.
    
4. Username and Password can be left blank provided no user needs to log on to SERVER_C, or else, enter the Username and Password of a user with write privileges for SERVER_C\D-DISK\NOD_UPD. If the update computer is located in a different domain, enter the name in the following format: DOMAIN\NAME, with DOMAIN being the name of the domain where SERVER_C belongs to and NAME is the valid name in the domain with DOMAIN name.
    
Note.: In Case 3.E.2 two different sharing options of the NOD_UPD directory can be set: a/ for reading only- NODUPD_R and, b/ for writing- NODUPD_W. Consequently, the paths will be set as follows:
Path for updates of the copies: \\SERVER_C\NODUPD_W
In the entry line for Access path for clients enter:
%CurrentPath%
or, more specifically:
file://SERVER_C/NODUPD_R
2. Automatic Update Setup - Wide Area Networks
   Support of the wide area network automatic update by NOD32 Control Center is achieved using the multi-level mirroring mechanism. The principal network administrator downloads the Update files from available source (www.nod32.com, CD-ROM, etc.) and creates a proper mirror on a selected local or network disk. Lower level network administrators create new mirrors for their dedicated end-users.

   Alternatively, mirroring can be set by the principal network administrator and the mirrors can be replicated to appropriate servers available to end-users for update of their computers.

   (NOTE: If the directory for update files (mirror) is selected on a machine with NOD32 Control Center installed in the administrator mode, do not select (for the location of the mirror) the UPDATE directory - located in the Eset directory.)
    

   1. Setup of the multi-level mirroring system
      Setup of the multi-level mirroring mechanism encompasses, in the simplest case, two steps. Principal network administrator performs the first one while the lower level administrators carry out the second one.

      Mirror Setup by the Principal Administrator

      1. Computer and file names selected for this example will have to be replaced by alternative options, applicable for particular situation within particular network.
         Let us assume that the administrator’s computer name is: ADMIN_C and the server name (computer where the mirrors will be saved/stored) is: SERVER_C. Further, let us assume that the access to a shared disk D: is via the name: D-DISK. Let the directory (located on disk drive D:) where the updates will be saved is NOD_UPD. As in the previous case, this directory needs to be created manually.
      2. Click at Mirror Setup button and enter the Path for updates of the copies entry as follows:
         \\SERVER_C\D-DISK\NOD_UPD
      3. In the entry line for Access path for clients enter:
         %CurrentPath%
         or, more specifically:
         file://SERVER_C/D-DISK/NOD_UPD
         Hence, you may use the select the Use the same path for clients checkbox.
      4. Username and Password can be left blank provided no user needs to log on to SERVER_C, or else, enter the Username and Password of a user with write privileges for SERVER_C\D-DISK\NOD_UPD. If the update computer is located in a different domain, enter the name in the following format: DOMAIN\NAME, with DOMAIN being the name of the domain where SERVER_C belongs to and NAME is a valid name in the domain with DOMAIN name.
         Note: The mirrors can be saved/located in the administrator’s local disk. In this particular case, the Path for updates of the copies might be, e.g.: C:\NOD_UPD, and the Access path for clients will read %CurrentPath% or, file://ADMIN_C/C-DISK/NOD_UPD.
      Mirror Setup by the Lower-level Administrators:
   1. Let us assume that the lower-level administrator’s computer name is: ADMIN2_C and the name of the computer where the mirrors will be saved/stored is: SERVER2C. The shared disk is the drive E: and its name is: E-DISK. Let the directory (located on disk drive E:) where the updates will be saved is NOD_UPD2. As in the previous case, this directory needs to be created manually.
   2. On the ADMIN2_C computer, in NOD32CC program, click at Mirror Setup button and enter the Path for updates of the copies entry as follows:
      \\SERVER2C\E-DISK\NOD_UPD2
      In the entry line for Access path for clients enter:
      %CurrentPath%
      or, more specifically:
      file://SERVER2C/E-DISK/NOD_UPD2
      Hence, you may use the select the Use the same path for clients checkbox.
   3. Username and Password can be left blank provided no user needs to log on to SERVER2C, or else, enter the Username and Password of a user with write privileges for SERVER2C\E-DISK\NOD_UPD2. If the update computer is located in a different domain, enter the name in the following format: DOMAIN\NAME, with DOMAIN being the name of the domain where SERVER_C belongs to and NAME is a valid name in the domain with DOMAIN name.
   4. Return to the Update Tab and click at Servers. Enter file://SERVER_C/D-DISK/NOD_UPD, which, as defined above, is the server with principal administrator’s mirror. Click at Add server. Close the window clicking at Close.
   5. In the Update Tab, select the \\SERVER_C\D-DISK\NOD_UPD\ from the list of servers. If the name and password is necessary to access the \\SERVER_C\D-DISK\NOD_UPD\ directory, enter the corresponding values into Username a Password lines in the Location group. For an access to a computer in a different domain, use the following format: DOMAIN\NAME.
      Finally setup the NOD32CC on the computers of the end-users pursuant to section 3.3 of this chapter.
   2. Setup of the Mirroring Mechanism via the Replication Approach
      Setup of the mirroring is performed on the principal administrator’s computer. This computer will save the mirror on a disk of a network computer that will automatically replicate the mirror onto other same-level servers. Automatic replication is provided by other (system) utilities.
   
   Setup of the mirroring on by the principal administrator:
   1. Let us assume that the administrator’s computer name is: ADMIN_C and the name of the computer where the mirrors will be saved/stored is: SERVER_C. The shared disk is the D: drive and its name is: D-DISK. Let the directory (located on disk drive D:) where the updates will be saved is NOD_UPD. This directory needs to be created manually.
   2. On the ADMIN_C computer, in NOD32CC program, click at Mirror Setup button and enter the Path for updates of the copies entry as follows:
      \\SERVER_C\D-DISK\NOD_UPD
   3. In the entry line for Access path for clients enter:
      %CurrentPath%
      The above path must be a generic one, since this mirror will be used on different servers. This path will be replaced by NOD32CC on a particular end-user machine based on the server setup in the Update Tab.
   4. Username and Password can be left blank provided no user needs to log on to SERVER_C, or else, enter the Username and Password of a user with write privileges for SERVER_C\D-DISK\NOD_UPD. If the update computer is located in a different domain, enter the name in the following format: DOMAIN\NAME, with DOMAIN being the name of the domain where SERVER_C belongs to and NAME is a valid name in the domain with DOMAIN name.
      Finally setup the NOD32CC on the end-user machines pursuant to section 3.3.
3. Setup of the Automatic Update on End-user computers
   NOD32CC of the end-user needs to be set up in such way, that it is automatically updated from its corresponding, proper server. If the mirroring mechanism was set for a small network (pursuant to section 3.1), all end-users Control Centers will use the same parameters, otherwise, each end-user’s Control Center will require its corresponding update/mirror server.
   Setup of the end-user computers can be performed automatically or manually. For an automatic method, please, see section 3.3.2 below. The manual setup is described in the following section (3.3.1).
    
   1. Manual setup of the automatic update on end-user computers
      1. Let us assume that the administrator’s computer name is: ADMIN_C and the name of the computer where the mirrors will be saved/stored is: SERVER_C. The shared disk is the D: drive and its name is: D-DISK. Let the directory (located on disk drive D:) where the updates will be saved is NOD_UPD. The update files should have already been created in this directory by means of creation of the mirror.
      2. On the end-user computer, in NOD32CC program, click at the Mirror Setup button and the Servers button. In the New server line enter file://SERVER_C/D-DISK/NOD_UPD and click at Add server. Click at Close button to close the window.
      3. Select the \\SERVER_C\D-DISK\NOD_UPD\ from the list of servers in the Update Tab. If the username and password are required to access the \\SERVER_C\D-DISK\NOD_UPD\ directory, enter correct values into the Username and Password entry lines (located in the Location group).
      4. Click at Connection Setup and, for the Internet connection, select None
      5. Select the update type. Full update is recommended for the end-user computers. The network administrator can control the update type by modifying update type on his (administrator’s) Control Center.
      6. Setup the update interval and allow the automatic update.
          
   2. Automatic Setup of the End-user Computer Update by means of the Configuration File
      In the environment of a large computer network, manual setup of the end-user computers might be very time consuming and cumbersome. NOD32 Control Center avoids the manual process introducing a Configuration File allowing automatic setup of the end-user computers.
      The Configuration File can be used during the first installation of NOD32 on an end-user computer, or when the old update system is being replaced by a new one. It can also be used when the end-user setup needs to be changed. Application of the Configuration file is mostly recommended for the end-user computers. Detail information on creation and application of the Configuration file are presented in section 3.4.

4. Configuration File
    
   1. How to create the Configuration file
      1. To create the Configuration File run the NOD32CC in the administration mode. Click at the Mirror Setup button and Check the Use the Configuration file for workstations checkbox. (Create Update mirror needs to be selected during the whole aforementioned procedure).
      2. Click at the Browse button to select the location (directory) of the Configuration file. Selection of the following directories should be avoided:
         • \Program Files\Eset\Update - this directory is the NOD32CC working directory.
         • Directory selected to save the update files (NOD32CC will copy the Configuration file into this directory automatically)
         • Directory used for the old type of automatic update (version 1.52 and older) This is the directory that could be configured in Amon module by means of the following commands: Amon -> Setup -> Network -> Change the directory for Update file.
         It is recommended that the Configuration file is created on a local disk. (E.g., in the NOD32 installation directory a CFG subdirectory can be created for this purpose.)
      3. To modify the parameters of the configuration file, click at Modify the file button and carry out desired modifications. Description of the available options is presented in the following section.
          
   2. Modification of the Configuration file
      To modify the Configuration file, click at the NOD32CC icon to open the main program window. In the Update Tab, click at the Mirror Setup button, and the Modify the file button located in the Configuration file group. This action will open the Configuration file dialog window with 8 checkboxes without name located in the left side of the window.

      If a ”name-less” checkbox is selected, access to the corresponding options on the right side of the window become available. Selection of any available option (or no selection, for that matter) will be ”imposed” on each end-user machine updated from the server with this Configuration file after application update of the system is performed.
      On the other hand, if a ”name-less” checkbox is not selected the corresponding parameters on an end-user computer will not be effected in any way.
      In what follows, the meaning of particular Configuration file options are discussed in the order as they appear in the file dialog window.
       

      1. Run Amon at startup and Install NOD32 for Outlook/Exchange checkboxes provide automatic execution of the resident antivirus protection module – Amon, and installation of protection of the MAPI compatible e-mail client programs.
      2. Path to the Update file represents the path to the update server set on a particular end-user machine. To set the path click at the Mirror button. The system will use the path defined in the Mirror Setup window, in particular, the path defined in Access path for clients.
         Important note! If the %CurrentPath% was initially used then, after clicking at the Mirror button, the path that would appear in the dialog is, obviously: %CurrentPath%. This default value must be replaced by a specific server name used by a particular end-user to download the updates. If, for example, the name of the server where the mirrors are located is SERVER_C and the updates are located at
         \\SERVER_C\D-DISK\NOD_UPD, than the path that needs to be entered into the dialog is file://SERVER_C/D-DISK/NOD_UPD.
          
      3. Check the checkbox in the section with Username and Password. The Username and Password could be left blank. In this case, the clients will log on to the mirror server using the implicit username and password, i.e. the password and username that the Windows system remembers from the last connection to this server. This method may not work on a network with Windows NT computers. It is recommended that a Username be specified so that NOD32CC could use it to access the server. In some cases, the following format of the Username has to be used: DOMAIN\USERNAME. To secure safe installation, it is recommended to test the access on a sample computer/s. It is also possible to create a special name (e.g. NOD_USER) with special privileges to access the update directory.
      4. Select the update type options. It is recommended that the network user use the Full update option. Control over the update type can further be influenced by administrator’s NOD32CC setup. If, e.g., the administrators chooses to update the virus definition database only (on the mirror server) the end-users will only be able to receive this type of update.
      5. To receive information on occurring errors or incidents on any network computer, you may setup a feature providing e-mail notification to a predefined user/address. Parameters of this option can be set in the Send messages via SMTP dialog. Detailed description of different options available can be retrieved from the program help files. To access the information, press F1 button.
      6. If no warning messages are to be seen by the end-user, Silent mode can be selected.
      7. Lock settings can be selected in the next group. To do that check the Lock settings button. Click at Change password to password protect the settings. The password will lock the settings of the NOD32CC, Amon, and the Network Tab in NOD32 module.
      8. Checking of the Initial installation setup dialog checkbox is done upon the first installation of NOD32 on the end-user computers. This option determines the location of the NOD32 installation on a particular computer. Standard (default) value %ProgramFiles%\Eset\ is recommended. The parameter %ProgramFiles% is than replaced with a specific path to the program files on a particular computer.
         Note: Modification of the Configuration file for the end-user computer has no effect whatsoever on the settings of the NOD32CC on the administrator’s computer.
          
   3. Application of the Configuration File
      Configuration file can be used in three situations:
      1. Upon initial (first) installation of NOD32.
      2. New installation of NOD32CC supported version on a computer with version supporting old automatic update feature (version 1.52 and older).
      3. Update of a computer with NOD32CC supported version (1.53 and higher).
      Each of the aforementioned situations is described the following sections.
       
      1. Application of the Configuration file upon the first NOD32 installation
         Save the Configuration file into a shared network directory (manually), jointly with the NOD32 installation files. Provide for execution of the installation on the workstations running the setup.exe program with the following parameters: /auto_script=”CONFIG” and /silent_install, where the CONFIG parameter is the path to the Configuration path with the file name. The set of the installation files consists of setup.exe and setup.ini, data1.dat, data2.dat files. On a Windows NT and Windows 2000, the execution of the installation must be performed with administrator’s privileges.

Example: setup.exe, setup.ini, data1.dat, data2.dat and the configuration file nod.cfg will be saved on a server SERVER_C, in particular on its shared disk D:, in the directory NOD_INST. Then, on a particular workstation the following command is executed:
\\SERVER_C\D-DISK\NOD_INST\SETUP.EXE /auto_script=”.\nod.cfg” /silent_install
2. Application of the Configuration file for a workstation with old automatic update system in place (”old” – version 1.52 and older)
   The newly created Configuration file copy manually into the directory currently used as the ”directory for update” and rename the file to read setup.cfg. Save the new update files (updnodnt.dat or updnod95.dat) into this directory as well. The workstations with the old update system in place will be updated and will use the settings defined in the setup.cfg file. NOD32CC will commence to use the new update system.
    
3. Application of the Configuration file to update workstation/s with currently installed NOD32CC
   Click at Mirror setup on the Update panel of NOD32CC on the administrator’s computer. select the Use the Configuration file for workstations checkbox (if this is greyed out, you will have to click at Create update mirror first). Set a correct path to the Configuration file. When the mirror is created, NOD32CC will include and provide the transfer of the Configuration file into the mirror directory from the directory selected.
4. Application of the Configuration file in large network environments
   In a multi-level hierarchy of a large computer network, the Configuration file can be created by the principal network administrator. The ”template” of this file can than be sent to lower-lever network administrators who may modify the file to reflect their specific needs.

   Included below is an example of a Configuration file created by the principal network administrator. If a lower level administrator wants to introduce any changes, the following procedure can be applied: 1/ the file is saved in a directory on their computer, (e.g. \Program Files\Eset\Cfg), 2/ in the Mirror setup (in the Configuration file group) this file is selected, and, 3/ clicking at Modify the file the Configuration file dialog window will open allowing proper changes to be made.

   Lower-level administrators will have to change the Path to the Update files, to secure update of the end-user workstations from the correct server, that is from the server where a given lower-level administrators creates the update mirror. The server username and password should also be changed.

   In the example presented below, definition of the SMTP messages is defined as well. One of the messages is sent to the principal (main) administrator MAIN_ADMIN@AAA.BBB , the second one is sent to a specific administrator in charge of particular end-user workstation. In the example, the principal administrator has also defined the password to lock the settings. The lower level administrators don’t need to change the password. Unlocking of the settings may be the over entire network.
    

   EXAMPLE of a CONFIGURATION FILE:

   [setup]
   Auto_Update=1
   Start_Amon_Automatically=1
   Install_Nod_For_Exchange=1

   [update]
   UpdateServer=file://SERVER_1/D-DISK/NOD_UPD
   UserName=NOD_USER
   PassLength=0
   Password=00
   UpdateType=1
   AutoUpdate=1
   UpdateFrequency=24

   [common]
   LockSettings=1
   LockPassword=31879
   Use_SMTP=1
   SMTP_Server="XXX.YYY.ZZZ"
   SMTP_Address_Sender="%ComputerName%@AAA.BBB"
   SMTP_Address_Virus="ADMIN1@AAA.BBB;MAIN_ADMIN@AAA.BBB"
   SMTP_Address_Error="ADMIN1@AAA.BBB;MAIN_ADMIN@AAA.BBB"
   SMTP_Format_Virus="%TimeStamp% - Virus alarm of %ProgramName% on %ComputerName%: %InfectedObject% infected with VirusName%."
   SMTP_Format_Error=" %TimeStamp% The following error message: %ErrorDescription% has occurred on %ComputerName% workstation, while %ProgramName% was executed! "
    

1. The system temporarily hangs up while updating.
   If an Automatic update is selected and Amon (the resident protection module) is running, a temporary hang up of Windows may occur while Amon is being updated by the new virus signatures. Although the time necessary to carry out this operation is relatively small, some systems may be sensitive to such temporary lack of response and may result in application output problem. (This might happen on a computer while recording the files onto a CD, capturing the video, or a similar time critical application.) It is recommended that the Update every X hours option is not selected on such systems. Manual update (or the Ask option) should be selected.
2. Problems occurring at an attempt to access the network computer when update is to begin.
   Check the server name, located in the Server field and Actualization Tab of NOD32CC program. Also check the username and password used to log on to this server. The user has to have the read privileges (from the selected directory). Try to use the Username in the following format: DOMAIN\USERNAME with DOMAIN being the domain or a workgroup a particular update server belongs to, and the Username is the name of the user who can log onto this workgroup.
3. Problems occurring at an attempt to access the network computer when mirror is to be created.
   NOD32CC works as a service under LocalSystem account on Windows NT and Windows 2000 systems. Hence, it does not have the authorization of a user who is currently logged on (e.g. the administrator). As a result, NOD32CC can run and create mirrors even without the administrator being logged on the system. The following problems may occur while the mirror is configured:
   • If you attempt to set the Path to Update of the copies by means of browsing, the given server may be unavailable.
   • The mapping of the network disks created by the user currently logged on the system may not be accessible.
   If the above problems are observed the Path to Update of the copies needs to be entered manually in a format as follows: \\SERVER\SHARE\DIRECTORY. Fill out the username and password necessary to access this server. If the server rejects the username it needs to be eneterd again in the following format: DOMAIN\USERNAME.
4. Problems occuring at the process of creation of the update copies (mirrors)
   Incorrect selection of the directories for the creation of the update copies (mirrors) may lead to the following problems:

• Incorrect specification of the Path of update of the copies (directory) and/or Access path for clients in the Mirror Setup dialog window
• Both paths must refer to the same directory. Path of update of the copies is the path used by the administrator to access the directory for creation of the update copies, whereas the Access path for clients is the path used by the end-users (or lower level administrators) to access the same directory. Hence, the network administrator will create one directory only.
• Incorrect specification/location of the directory (specified in the Path of update of the copies)
  If the Path of update of the copies is to be locatd on the disk of the computer generating the update copies (mirrors), do not use the Program Files\Eset\Update directory for this purpose. This directory is NOD32CC working directory. New directory has to be created fot this purpose.
• Incorrect location of the Configuration File
  Before the Configuration File can be used it has to be created in the Mirror Setup dialog window. Select the location of the Configuration file and, subsequently, create the file clicking at the Modify the file button.. The following directories should not be used:
  • Program Files\Eset\Update
  • Program Files\Eset
  • shared directory used for the old type of the Automatic Update (version 1.52 and lower) specified in Amon or NOD32 in the Network Tab.
  The Configuration file could be saved in, e.g. Program Files\Eset\CFG directory.
   
For any inquiries and support, please, contact us at: support@nod32.com