Installing Enterprise Edition and Remote Administrator

[Blackspear]

Welcome to the “Installing Enterprise Edition and Remote Administrator Tutorial”.

This thread aims to give you a basic understanding of installing NOD32 in a network environment, and its use...

As NOD32 is an ever changing product, you may find this thread has the odd setting disjointed from where it logically ought to appear. This is just part and parcel of a continually improving product. Furthermore, when we learn new things about NOD32, they will also be added to the end of this thread. Hence, it remains a “Work in Progress”.

If you become lost or are unsure of anything, don’t hesitate to start a new thread with your question in the main NOD32 Forum…

All the best…

Cheers

Blackspear ;D



Additional Resources:

Problem Solving (http://www.wilderssecurity.com/showthread.php?t=145827)

Documentation for implementing NOD32 Enterprise Edition on Windows Servers (http://www.wilderssecurity.com/showthread.php?t=120169)

Spanish Enterprise Edition Tutorial (http://computalleres.com/foros/viewtopic.php?t=40)





Table of Contents


CONFIGURATION EDITOR (http://www.wilderssecurity.com/showthread.php?p=792594#post792594)

CREATING A PACKAGE (http://www.wilderssecurity.com/showthread.php?p=798209#post798209)

ERROR CODES (http://www.wilderssecurity.com/showthread.php?p=803997#post803997)

EXCLUSIONS (http://www.wilderssecurity.com/showthread.php?p=934974#post934974)

INSTALLING NOD32 MIRROR VERSION (http://www.wilderssecurity.com/showthread.php?p=792474#post792474)

INSTALLING REMOTE ADMINISTRATOR CONSOLE (http://www.wilderssecurity.com/showthread.php?p=792600#post792600)

INSTALLING REMOTE ADMINISTRATOR SERVER VERSION (http://www.wilderssecurity.com/showthread.php?p=792492#post792492)

LAPTOPS AND DUAL UPDATE PROFILES (http://www.wilderssecurity.com/showthread.php?p=798905#post798905)

NOD32 MIRROR (http://www.wilderssecurity.com/showthread.php?p=792474#post792474)

PUSHING A PACKAGE (http://www.wilderssecurity.com/showthread.php?p=798281#post798281)

UPGRADING or ADDING LICENSES (http://www.wilderssecurity.com/showthread.php?p=833087#post833087)



You will need the following files downloaded and ready for installation:

Standard Edition for NT / 2000 / XP / 2003 = ndntenst.exe

Update Server Mirror Edition = ndntenad.exe

Remote Administrator Server (RAS) = rasrvnten.exe

Remote Administrator Console (RAC) = raconsnten.exe current version is 1.015

XMON – Microsoft Exchange plugin = ndntenxs.exe

RAS License file sent by Eset/Reseller = .LIC

XMON License file sent by Eset/Reseller = .LIC (if you are using Microsoft Exchange)



The workstations have to have certain conditions before an installation:

For XP:

A. Windows Firewall needs to be turned OFF.

B. If NOT on a domain, then simple filesharing needs to be turned off. C Drive: Tools> Folder Options> View> uncheck “simple file sharing” (last in the list).

C. Remote registry editing must be enabled. Start> Run> services.msc > remote registry


Pushing will not work to XP Home Edition.

The RAS can accept all Win9x and up clients connecting and pushing configurations.




Install Update Server Mirror Edition = ndntenad.exe on the Server

1. Click on Extract.

[Blackspear]

1. I recommend making a “Typical” install unless you have previous knowledge of NOD32 and are comfortable wandering through a computer's settings.

2. Click “Next”.

[Blackspear]

1. Click on the Radio Button that says “I agree”.

2. Click “Next”.

[Blackspear]

1. Please LEAVE Server as “Choose automatically”, I say this for many reasons:

* If a particular server is down, Nod32 will NOT be able to roll on to the next server.
* Experience shows us that you will have fewer or no problems with updating using this setting.
* Let Eset do their job and balance loads on the servers.

2. Place in the Username (UN) that your Reseller/Distributor or Nod32 email has provided.

3. Place in the Password (PW) that your Reseller/Distributor or Nod32 email has provided.

ONLY a UN and PW provided to you by Eset will work. These are not personalized entries created by you.

4. Click “Next”.

[Blackspear]

1. Leave this Radio Button as is, UNLESS you use a modem that dials onto the internet.

2. Click “Next”.

[Blackspear]

You have purchased Nod32 for its ability to protect your computer, let’s help Eset to continue in its efforts to do so by leaving “Enable ThreatSense.NET Early Warning System” ticked.

1. Click on “Advanced Setup”.

[Blackspear]

1. Make a choice, I would hope that you participate and as such choose the lower or middle option.

As the information sent is anonymous, you may like to add your email address in “Contact email (optional)”, in case Eset would like to ask/advise you further about what you are sending.

2. Click on “OK”.

[Blackspear]

1. Click on “Next”.

[Blackspear]

1. Leave this ticked so the resident scanner (AMON) will start automatically upon booting your system.

2. Click “Next”.

[Blackspear]

1. Click “Next”.

[Blackspear]

1. Click this Radio Button to restart your system.

2. Click “Finish” to complete the installation.


NOTE: Using the net start nod32krn will allow the service to start without rebooting. Then one only has to start AMON manually after the Control Centre is launched (manually).

An error will appear which is normal.

[Blackspear]

Welcome to Nod32, this is the Nod32 splash screen that first appears upon bootup of your system.

[Blackspear]

INSTALLING A NOD32 MIRROR


Place a NEW folder preferably on your "Data drive" (or where data is backed up) and call it "Mirror".

Right click on the new Mirror folder and share it.


NOTE: The mirror folder does not need to be shared, ONLY if you are using UNC and not the http update functionality.

[Blackspear]

Click on the "NOD32 Control Centre".

[Blackspear]

1. Click on "Mirror".

2. Click on "Setup".


NOTE: IMON must greyed out on a Server.

[Blackspear]

1. Click on "Create update mirror".

2. Place a tick in this box; this is only necessary if you want to create mirrored files with component updates.

3. Place a tick in this box; this is only necessary if you want to create mirrored files with component updates.

4. Place a tick in this box so permission is required in order to perform a program component update.

5. Click on "Folder".

[Blackspear]

1. Browse to your "Data drive" (or where data is backed up).

2. Click on the "Mirror" folder.

3. Click on "OK".

[Blackspear]

1. Place a tick in "Enable access to files via the HTTP protocol".

2. Untick "NOD32 for Windows NT - Sak Interface" unless you are running a NAS (Network Application Storage) Server.

3. Click on "Advanced".

[Blackspear]

1. Place a tick in "Create floppy disk update files".

2. Place a tick in "Create CD update files".

3. Change the "Port used for providing files via HTTP to "8088".

8081 is the default, however Sharepoint services typically use this port as its default. Changing the port to 8088 will eliminate any conflicts as it is not a standard port (unless another application has been changed to use this port).

4. Click on "OK".

[Blackspear]

As you have changed the Mirror settings up comes a prompt box.

1. Click on "Yes".

[Blackspear]

When the Mirror has finished updating itself you will see the following balloon.

[Blackspear]

After first install, you may be presented with the following message.

1. Click "OK".

[Blackspear]

1. Here you are seeing that a Component upgrade is ready.

2. Click on "Upgrade components".

[Blackspear]

Because this system already has the most up to date components installed this Window is advising such.

1. Click on "OK".

[Blackspear]

INSTALLING NOD32 REMOTE ADMINISTRATOR SERVER VERSION



Install Remote Administrator Server = rasrvnten.exe

1. Click on Extract.

[Blackspear]

1. I recommend making a “Typical” install unless you have previous knowledge of Nod32 and are comfortable wandering through a computer's settings.

2. Click “Next”.

[Blackspear]

1. Click on the Radio Button that says “I agree”.

2. Click “Next”.

[Blackspear]

1. Click on this button.

[Blackspear]

1. Click on the dropdown arrow.

2. Navigate to where your RAS (Remote Administrator Server) License is located.

[Blackspear]

1 Click on your license.

2. License name can now be seen.

3. Click on "Open".

[Blackspear]

1. You will now see the license file location.

2. Click on "Next".

[Blackspear]

1. Click on "Next".

[Blackspear]

1. Click on "Finish".

[Blackspear]

CONFIGURATION EDITOR



1. Click on Start> All Programs.

2. Navigate to the Eset Folder.

3. Click on "Configuration Editor".

[Blackspear]

1. Navigate to Update> Profile> Settings> Update Server.

2. Place in the name of your Update Server and the update port 8088. This is the servers name (see No 3.)

The information entered will be similar to this (without the space after http): http ://blackspear:8088

3. The name of your server can be found by Right Clicking on "My Computer" and going to the "Computer Name" tab, as per screenshot.

[Blackspear]

1. Navigate to Settings> Remote Administration Server address.

2. Place in the name of your Update Server

In this post and the previous one I have covered the 2 most important areas of the "Configuration Editor", the rest you can go through and makes choices according to your requirements. Further advice about settings can be found in this Tutorial. (http://www.wilderssecurity.com/showthread.php?t=37509)

[Blackspear]

1. Click on "File".

2. Click on "Save As..."

[Blackspear]

1. Navigate to where the NOD32 Mirror is located.

2. Name your file.

3. Click on "Save".

[Blackspear]

INSTALLING THE NOD32 REMOTE ADMINISTRATOR CONSOLE



Install the Remote Administrator Console = raconsnten.exe on a Computer that you want to Remotely Administer from.

1. Click on Extract.

[Blackspear]

1. I recommend making a “Typical” install unless you have previous knowledge of NOD32 and are comfortable wandering through a computer's settings.

2. Click “Next”.

[Blackspear]

1. Click on the Radio Button that says “I agree”.

2. Click “Next”.

[Blackspear]

1. Click on "Next".

[Blackspear]

1. Click on "Finish".

[Blackspear]

Open up the NOD32 Remote Administrator Console.

1. Click on "Tools".

2. Click on "Console Options...".

[Blackspear]

1. Click on "Add/Remove...".

[Blackspear]

1. Type in the name of your Server.

2. Click on "Add".

[Blackspear]

1. The name of your Server will appear here.

2. Click on "OK".

[Blackspear]

1. Click on "Connect"

[Blackspear]

1. Place a tick in "Remember Password...".

2. Enter a Password for the Server (this is recommended - ensure it is recorded for reference).

3. Click on "OK".

[Blackspear]

1. You will see your Server now connected.

2. Click on "OK".

[Blackspear]

CREATING A PACKAGE



Open up the "NOD32 Remote Administrator Console" (RAC).

1. Click on the "Remote Install" tab.

2. Click on "Packages".

[Blackspear]

1. Click on "Save as...".1. Click on "Create".

[Blackspear]

1. Click on this button.

[Blackspear]

1. Navigate to where you have ndntenst.exe downloaded.

2. Click on the file "ndntenst.exe".

3. The file name will appear here.

4. Click on "Open".

[Blackspear]

1. The file you clicked on will now appear here.

2. Click on "Create".

[Blackspear]

1. Add the following to the command line: /FORCEOLD /REBOOT

2. Click on "Select".

[Blackspear]

1. Navigate to the Mirror folder.

2. Click on the .xml file that was created with the "Configuration Editor".

3. The file name will appear here.

4. Click on "Open".

[Blackspear]

1. Click on "Save as...".

[Blackspear]

1. Name the file, describing it very well.

2. Click on "Save".

[Blackspear]

1. Click on "Close".

[Blackspear]

PUSHING A PACKAGE



1. Click on "Install".

[Blackspear]

1. Click on the drop-down arrow.

2. Choose the Package that we made previously.

3. Navigate to a computer that you want to "Push" an installation to and drag it into the "Client window".

4. This is the "Client Window".


ALTERNATIVELY: you can right click in the client area and add the name of the computer if you know it.

[Blackspear]

1. Highlight what you dragged across.

2. Click on "Install".

[Blackspear]

1. Type in the User name that has administrative rights on the computer you are pushing the package to.

2. Type in the Password that has administrative rights on the computer you are pushing the package to.

3. Click on "Logon".

[Blackspear]

1. You will see the push being installed.

[Blackspear]

1. You will see the message that a successful push has occured.

2. Click on "Close".

[Blackspear]

LAPTOPS AND DUAL UPDATE PROFILES


1. Open up the NOD32 Configuration Editor.

2. Right Click on "Profile (My Profile)".

3. Click on "New Profile...".

[Blackspear]

1. Click on "Update".

2. In the New Profile name, enter "Internet Updating".

3. Click on "OK".

[Blackspear]

1. Click on the new Profile that was just created.

2. Click on "Username".

3. Enter the Username provided by Eset with your license.

[Blackspear]

1. Click on "Password".

2. Click on "Set Password".

[Blackspear]

1. Enter the Password provided by Eset with your license.

2. Re-enter the Password provided by Eset with your license.

3. Click on "OK".

[Blackspear]

Scroll to the top of the Configuration Editor.

1. Click on Scheduler/Planner.

2. Click on "Edit".

[Blackspear]

1. Click on "Add...".

[Blackspear]

1. Click on the drop-down arrow.

2. Click on "NOD32 Update.

3. Click on "Next".

[Blackspear]

1. Type in the following and be precise: Regular automatic update

2. Click on "Repeatedly".

3. Click on "Next".

[Blackspear]

1. Click on "Next".

[Blackspear]

1. Click on "Next".

[Blackspear]

1 Click on "Primary profile".

2. Type in: My Profile

3. You will see the value added here.

[Blackspear]

1 Click on "Alternative profile".

2. Type in: Internet Updating

3. You will see the value added here.

4. Click on "OK".

[Blackspear]

1. Click on the new Scheduled task.

2. Click on "Change ID".

[Blackspear]

1. Type in: 64

2. This explains why 64 was typed.

3. Click on "OK"

[Blackspear]

1. Click on "Close".

[Blackspear]

1. Click on "Save".

[Blackspear]

ERROR CODES



Microsoft System Error Codes can be found HERE (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/base/system_error_codes.asp)

SC Error Codes

1. Error codes of the nod32 setup.

These can be found when the installation fails on the level of the setup. They are displayed during installation/push installation as "installer error" followed by number which specifies the error. Some of them may also appear during Program Component Update (PCU).

#define E_OK 0 //all is OK
#define E_OK_RESTART 3010 //ERROR_SUCCESS_REBOOT_REQUIRED // all is OK, reboot si needed
#define E_OK_RESTART_BY_CALLER 3011 // reboot is handled by calling application
#define E_ADMIN_REQUIRED 101 // required administrator rights
#define E_NO_CFGFILE 102 // cfg file needed
#define E_NO_MEMORY 103 // not enough memory
#define E_NO_REQUIRED_OS 104 // old version of OS (NT)
#define E_NO_TMPDIR 105 // can't create TMP directory to extract files from archive
#define E_EXTRACTION 106 // error extracting archive
#define E_NO_SETTINGSFILE 107 // setup file is missing or corrupted (setup - file with settings of component)
#define E_OLDVERSION 108 // component to install is older then currently installed one
#define E_BADLIBRARY 109 // can't connect to dll
#define E_UNKNOWN_OPER 110 // operation not supported (in dll)
#define E_DISKERROR 111 // cannot create file (on disk)
#define E_BAD_COMPSETTINGS 112 // number of components doesn't match
#define E_UNK_COMPONENTNUM 113 // number of components not set

#define E_BAD_SETUPXML 114 // bad or missing setup.xml
#define E_INCOMPATIBLE 115 // new version is not compatible with the old one, uninstallation needed
#define E_REGISTRY 116 // error writing to registry
#define E_UPDATE 117 // update error
#define E_LANGUAGE 118 // you are installing other language version then the currently installed one, uninstallation needed

#define E_BAD_UNINSTXML 119 // file describing uninstallation corrupted or missing
#define E_SERVICE 120 // error registering service
#define E_INSTALL_COMPONENT 121 // error installing component (details about component in nsetup.log)
#define E_CANNOT_INSTALL_HERE 122 // cannot install component
#define E_EVALONCE 123 // you are installing trial version after date of expiration
#define E_NO_REQUIRED_OS_WNT 124 // OS does not match requirements - Windows NT
#define E_NO_REQUIRED_OS_W95 125 // OS does not match requirements- Windows 95

// dialogue texts
#define P_WAITBEGIN 11 // waiting before start of installation
#define P_WAITEND 12 // waiting after end of installation
#define P_WAITUNINST 13 // waiting after uninstallation

#define P_INSTEND 14 //announcements in dialog window - installation
#define P_REINSTEND 15 //announcements in dialog window - reinstallation
#define P_UNINSTEND 16 //announcements in dialog window - uninstallation
#define P_REINSTBEGIN 17 // waiting for start of reinstallation
#define P_WAITREINST 18 // waiting to finish wizard
#define P_OLDENGINE 19 // older engine is being installed (then currently installed one)


// announcements/questions
#define P_UNINSTALL 201 // uninstall?
#define P_INSERTDISK 202 // next installation disk needed

#define P_CANCELMSG 204 // cancel installation?
#define P_NOTHING_UNINST 205 // nothing to uninstall
#define P_CANCELTITLE 206 // Cancel title box
#define P_PWDREQUIRED 207 // return code if password was needed


#exit code 301 //"Failure during NOD32 Install - exit code 301" newer version of MFC library needed



2. Remote Installation errors

Remote installation can fail even before setup is launched. In that case the error is in form: desciption (SC error code code1, GLE error code code2)

- description contains more specific information
- SC helps us to locate the place in the source code where the error occured
- GLE is the Win32 GetLastError code - this can help to know more about the error.


SC should be one of the following list:

RI_SUCCESS = 0
RI_ACCESSDENIED_ERROR = 1
RI_CONNECTREGISTRY_ERROR = 2
RI_OPENREGISTRY_ERROR = 3
RI_DELETEREGISTRY_ERROR = 4
RI_COMPUTERNAME_ERROR = 5
RI_ADDCONNECTION_ERROR = 6
RI_CANCELCONNECTION_ERROR = 7
RI_PARAMETER_ERROR = 8
RI_COPYFILE_ERROR = 9
RI_DELETEFILE_ERROR = 10
RI_OPENSCMANAGER_ERROR = 11
RI_SERVICENAME_ERROR = 12
RI_ENUMSERVICE_ERROR = 13
RI_QUERYSERVICE_ERROR = 14
RI_CREATESERVICE_ERROR = 15
RI_OPENSERVICE_ERROR = 16
RI_STARTSERVICE_ERROR = 17
RI_DELETESERVICE_ERROR = 18
RI_MEMORY_ERROR = 19

Most frequent are 6 or 11. They mean “access denied” or “server cannot connect to the remote service manager”. Here is list of requirements for push installation:

- Target must respond to a ping from the server
- Administrative user used for install cannot have a blank password.
- If the client and server are in a mixed domain/workgroup environment (or the server is 2003), simple file sharing must be turned off on XP clients
- Client for MS Network (server, client)
- Activated file and printer sharing (client)
- File Sharing permitted on firewall (client, server)
- TCP/IP (client, server)
- ADMIN$ share (Client)
- Remote registry service started (client)
- Account used for installation must have Administrator Rights
- Permitted ports: 2222,2223,2224 (server)

[Blackspear]

UPGRADING or ADDING LICENSES



Open up the NOD32 Remote Administrator Console.

1. Click on "Help".

2. Click on "About NOD32 Remote Administrator Console".

[Blackspear]

1. Click on "Renew".

[Blackspear]

1. Click on "Browse".

[Blackspear]

1. Click on the dropdown arrow and navigate to where your RAS (Remote Administrator Server) License is located.

2 Click on your license.

3. License name can now be seen.

4. Click on "Open".

[Blackspear]

1. Your new license details will appear here.

2. You should see your new expiry date and change of amount of computers if you are upgrading.

3. Click on "Upload to Server".

[Blackspear]

1. Click on "OK".

[Blackspear]

Go to the NOD32 Control Centre that has the "Mirror"

1. Click on "Update".

2. Click on "Setup".

[Blackspear]

1. Enter your new "Username".

2. Enter your new "Password".

3. Click on "OK".

[Blackspear]

EXCLUSIONS


Microsoft recommend the following exclusions (see HERE (http://www.msexchange.org/articles/Properly-Configure-file-system-antivirus-Exchange.html)):

C:\Program Files\Exchsrvr\Mtadata
C:\Program Files\Exchsrvr\Mdbdata
C:\Program Files\Exchsrvr\Servername.log (replace Server Name with your servers name)
C:\Program Files\Exchsrvr\Mailroot
C:\Program Files\Exchsrvr\Srsdata

With Exchange, also add:

%systemroot%\system32\inetsrv
%programfiles%\exchsrvr\imcdata

Further reading: HERE (http://support.microsoft.com/default.aspx?scid=kb;en-us;823166) and HERE (http://support.microsoft.com/default.aspx?kbid=328841)



.