Section 5: Pushing out ESET NOD32
Antivirus to your network
Well, you've installed the Console and the Server components of ERA and you've
set up the Mirror. You've even built a default policy into your Remote Administrator
settings, so no further customization is necessary.
The last big step is getting your ESET security software out to your clients. To do this,
ESET Remote Administrator creates a Package (an installer that can be run remotely)
and sends one out to each computer on your network so you don't have to walk
around from terminal to terminal installing ESET NOD32 Antivirus on each one.
Before you create and "push out" (send) your package to clients, let's briefly confirm
that your network is ready for package installation.
5.1 Push installation checklist
This manual assumes that your client machines all have basically the same
configurations across your network. Therefore, the configuration checklist below
only needs to be fulfilled on a single client machine because all other clients should
look the same.
•
First – and perhaps most important – you need to ensure that any prior antivirus
software is uninstalled across your entire network. Running two antivirus
products can cause your system to be unstable and can interfere with crucial
operations your ESET product needs to perform to protect your network. Follow
the KB connection link at right for more information and a list of common
uninstaller utilities.
Next, confirm that Use simple file sharing (Recommended) is deselected on
all workstations in your network. From Windows Explorer, navigate to Tools →
Folder Options → View and deselect the option if it is selected by default.
•
Next, make sure the client workstation(s) on which you are installing ESET
NOD32 Antivirus have the shared resource ADMIN$ activated. Confirm this by
clicking Start → Control Panel → Admin Tools → Computer Mgmnt → Shared
Folders → Shares.
•
Now, on the client workstation(s), open a command prompt to verify that the
workstation can access IPC. Type :
net use \\servername\IPC$
(where servername is the name of the server running ERA).
If this command returns anything other than 'The command completed
successfully,' contact your network administrator before proceeding with push
install.
•
Your network's hardware or software firewall must not block communications
or file sharing between the servers and the workstation. Contact your vendor for
support. This also applies to the Windows Firewall.
•
Ports 2221-2224 must allow ESET Remote Administrator to communicate. If the
server has any of these ports blocked, communication with the workstations is
not possible.
•
For Windows Vista machines, User Account Control (UAC) should be disabled.
•
The clients and the server must be visible on each other's Network browsers.
•
Confirm that "File & Print Sharing for Microsoft Networks" is enabled by checking
Control Panel → Network Connections → Network → Properties.
•
Click Start → Run on the workstation and type services.msc. You will need to
confirm that the Remote Procedure Call (RPC) service is started and that
the Remote Registry service is also started. Then, confirm that the Remote
Procedure Call (RPC) Locator service is set to 'manual' .
Estimated time: Varies based on
installation checklist, number of seats,
prior AV uninstall. Up to one hour.
KB connection
Check the ESET Knowledgebase for more info:
Push installation requirements and checklist
http://kb.eset.com/esetkb/
index?page=content&id=SOLN82
KB connection
Check the ESET Knowledgebase for more
info:
Uninstallers (removal tools) for common
antivirus software
http://kb.eset.com/esetkb/
index?page=content&id=SOLN146
5
페이지 인쇄