21 Apr 2012

Many home users have already found out how great NOD32 is for your PC's protection against viruses and trojans.  The NOD32 client is very lightweight, uses very little system resources with a low CPU overhead, while keeping your machines protected on all levels.  Businesses can leverage the power of ESET Nod32 in the ESET Nod32 Antivirus Business Edition for both servers and workstations.  This article outlines some of the steps to get you up and running at your business. 

Table of Contents

Part 1-The Setup

The configuration and setup will ultimately allow you to remotely install nod32 clients on your network.  There are four steps to be performed. 

1.  Download ESET Remote Administrator and ESET Nod32 Antivirus

First we download the files for the client.  To access these files you will need the userid and password given to you when you made the purchase. 

Now that you have those, you will need the ESET Remote Administration portions:

 

2.  Install the ESET Nod32 Antivirus on the Server

Now we have to do the install of the Nod32 client that we will distribute on the server itself. 

So we run the appropriate installer that we downloaded in step 1.  Double click the installer and click Next to proceed:

Next we can choose Typical or Custom, where custom will give you more control over advanced settings, but those settings can be changed later, so lets choose Typical and click Next.

The next step is to provide the Username and Password given to you by ESET and click Next.

We choose to enable the ThreatSense.Net Early Warning system and click Next (recommended).

We also should use the option "Enable detection of potentially unwanted applications" and click Next and the installer will proceed to install and then finish once you click Install on the next screen.

3.  Install the ESET ERA Server

Now that we have installed the client portion, for distributing the client from the Server.  We install the ERA Server, which we have already downloaded.

Double click the ESET Remote Administrator Server install file, click Next and accept the license terms.

Now, again, we have the option of doing a Typical install or a customized/advanced one.  If you choose Advanced, you can specify specific ports for the Server portion and database options along with different paths to direct the installed files to.  Here we choose Typical and Next.

Next we browse to our license file provided by ESET and click Next.

Next we are given the opportunity to set passwords for the various areas of administration.  These can be modified later in the Options in the Console.

On the next screen we provide the username and password given to us by ESET for the downloading of updates and click Next.

Next we choose Install and the Server installs.

4.  Install the ERA Console

Now that the server portion is done, we can install the admin console on the Server (and you can also install it on any workstations will you will do administration from).

Click Next and accept the license agreement.

Once again, we have the option to do an advanced setup, with more control over options, here we choose Typical.

You are given an opportunity even on the Typical setup to install to a different location.  Click Install, the installer will go through the setup and finish.

Part 2-Optional:  Configure a Mirror Server

By default, your client computers will get their updates to the Virus Signature database from ESET's servers.  Having them all connect to ESET individually will create unnecessary traffic across your local area network (LAN).  Hence, we have the option of installing a Mirror server on the LAN, so they connect to one source.

Note:  ESET recommends a max of 400 clients per single mirror.  They state if the mirror needs to be centralized on a single server, to use another type of HTTP server such as Apache or IIS.

Open the ESET RA Console and choose Tools, Server Options.  Click the Updates tab and enter your ESET-issued username and password in the fields.

Select the Create update mirror check box in the middle window.  Select the Provide update files via internal HTTP server checkbox.

Now click the Update Now button to display confirmation and click Yes.

We can verify that the Mirror server is working by going to a client workstation and browsing to it.

For example:  http://testserver:2221/update.ver

If it was successful you will see a web page with text as below.

If you don't see this, check things like firewalls in Server 2008 or hardware firewalls to see if that is causing the issue.

*Note you could also choose to store the update files in a path, rather than using the HTTP method.  For that to work you would go back to the updates tab and provide a path for updates in the "Folder to store mirrored files", such as C:\updates and UNCHECK Provide update files via internal HTTP server.

Part 3-Configure a default policy

Before we begin pushing out the clients, we should set a policy, that defines the options used to configure the client computers.  From the Remote Administrator choose Tools, Policy Manager.

If you click on the "Server Policy (machine name)", you can then click the Edit button on the far right.  This launches the ESET Configuration Editor, the tool to customize your clients' antivirus settings.

One thing we will want to do is to lock down the clients' ESET software to prevent changes.  Near the top of the tree, click "ESET Smart Security, ESET NOD32 ANtivirus, ESET kernel, Setup, Protect Setup Parameters."  If you click on Password to unlock, on the right you can click Set Password to set the password.

You can also go to ESET Smart Security, ESET Kernel, Setup, Default user interface values and highlight Suppress User Settings and check off the box that says Yes/No.  This way your users' will not have messages popping up that aren't needed.  You can aolso click on Show Splash-screen at startup and change the value to No.

Another setting to change would be the option to Configure clients to update from the Mirror.  Goto Update Module, Profile (My Profile), Setup, Update Server.  Choose the Custom Update Server from the Value drop down, and in the value put something like:  http://testserver:2221 and click the Save diskette icon to save the configuration then click Console to exit the editor.

 

Part 4-Pushing out the Clients

Now that you have everything else ready to go, its time to get the client out to your workstations.  Some things to check:

  • Before you begin make sure that any previous anti-virus packages have been removed from those machines.
  • In Windows Explorer, on the workstations, Use Simple File Sharing should be disabled.  Verify this by going to Tools, Folder Options, View and deselect if it is selected.
  • Another thing that must be enabled is that the client workstation must have the ADMIN$ shared resource activated.  Confirm by going to Start, Control Panel, Administrative Tools (classic/full view), Computer Management, Shared Folders, Shares.
  • Verify IPC on the workstations by typing:  Net use \\servername\IPC$ (where servername is the name of the server running ERA)
  • Verify there is no blocking of communications from any firewalls on the network
  • Ports 2221 through 2224 must be open.
  • On Vista, UAC must be disabled
  • File and Print Sharing for Microsoft Networks needs to be enabled via Control Panel, Network Connections, Network, Properties
  • The RPC (remote procedure call) service must be enabled in services

Creating a Package

Create the package by clicking Start, All Programs, ESET, ESET Remote Administrator Console.  At the bottom of the window, click the Remote Install tab.  From there right click a workstation listed and click Manage Packages.

From here we can click Add.. and browse to the .msi installation file that was saved to the desktop previously.  You then click Save As and give the install package a name.  Then click Save and Close to return to the ERAC window.

Pushing out a Package

Now you can click on the Remote Install tab at the bottom again and right click any workstation choosing Push Installation.  In this next window you can click the machine name in the upper left, then click Set on the right to set the logon information for the machine(s) then choose Next..

On this window we can choose the Package we just made from the Name drop down, then click Next and give the Remote Install task a name and click Finish.

Now we wait for the clients to install and can click on "Clients" at the bottom to see them appear when finished.

Troubleshooting failed pushes

*If some clients immediately fail, this is due to the policy not reaching them yet.  It can take up to one hour for this to occur.

*In other cases it may be necessary to go to services on the server and the "ESET Remote Administrator Server" service and change it from using the local service account to a domain admin account.  In doing this the push should then work.

*Other times clients can fail because of previous anti-virus software remnants that still exist.  Using the anti-virus company provided uninstaller usually fixes the issue, but often you must manually delete registry keys or use a program like CCleaner to clean things up.  Troubleshooting the client can be done from the "Remote Install" group in the console, then from the "Install Tasks" tab at the top of that area.

*You may notice errors related to inability to setup an IPC connection to some clients.  Check those workstations Services to ensure that the Remote Registry is started and working or that a firewall is not blocking the connection.  Other possible causes can include the Server Service not being started or that Use Simple File Sharing is enabled on the target machine.

Doing a Manual Install of the Client

In other cases you may have to just run the latest Nod32 installation msi file directly on the client, choosing to set update parameters later.

Once the client is installed, you need to drill into the advanced setup tree and click on Update on the left hand side (Setup on the left hand side, then "Enter entire advanced setup tree..." on right.  There you can click "Edit" and enter the address of the ESET Remote Administration Server as below:

Finally, goto the Miscellaneous section on the left hand side and click "Remote Administration".  Check off "Connect to Remote Administrator Server" and put the address of the server and the port (if you specified a different port during setup, enter it here).  If authentication has been set, then enter that password here as well:


Use this QR code in a QR reader application on mobile to open quickly on a mobile device

blog comments powered by Disqus

Flight-Stew Now Live

Be sure to visit our newest site, Flight-Stew, now active!

Recently Added

Subscribe

Poll

Which Game Console will you buy?


Show Results

[forcestyle][nozoom][nocaption]

Donate

       Support Tech-Stew
   [nozoom]
        Make a Donation

Recent Comments