|
Push Installation Requirements and Checklist
NOD32 Remote Administrator allows remote installations from the Remote Administrator Console to any workstation on the network with a Windows NT/ 2000/XP/2003/Vista operating system. This function is called a Push installation. The steps in this document describe the main requirements for configuration of this process.
While installation to standardized networking environments is relatively simple, problems can arise due to differences in architecture and configuration from network to network.
The following can be used both as a requirements check list for configuring a push installation as well as a trouble-shooting guide during the remote installation process. Verifying each of the tasks below is strongly recommended before performing the first trial installation on the client's network:
1.
The workstation where you are trying to install NOD32 client remotely must answer a ping from the computer where Remote Administrator Server is installed.
2.
If both the workstation and the server are in a mixed environment of Domain and Work Group (or if the server where Remote Administrator is installed has Windows 2003), the Use simple file sharing (located under the Tools → Folder Options → View) option should be disabled.
3.
Both the server and the workstation must have the TCP/IP protocol installed.
4.
Workstation must have the shared resource ADMIN$ activated (Start → Control Panel → Admin Tools → Computer Mgmnt → Shared Folders → Shares).
5.
The user performing the remote installation must have administrator rights.
6.
The user with administrator rights cannot have a blank password.
7.
The firewall on the network must not block communications or file-sharing between the servers and the workstation.
8.
The (Remote Administrator) server must allow data reception through ports 2222, 2223, and 2224. If the server has any of these ports blocked, communication with the workstations is not possible.
9.
For WinNT/2000/XP/2003 operating systems, verify the following:
-Client workstations are visible in both the server and the workstation connection.
-“File & Print Sharing for Microsoft Networks” must be enabled (Control Panel → Network Connections → Network → Properties)
-The Remote Procedure Call (RPC) service needs to be running on the target.
-The Remote Registry service needs to be running on the target.
-The RPC Locater service should be set to “manual” and need not be running.
10.
IMON should not be enabled on your server. IMON's primary functions are to control HTTP communication (web-browsing) and detect possible infiltrations encountered through using internet email (POP3). Given that the server will not be used as a typical workstation, it's recommended that the module be disabled. NOD32's other modules will provide your server with back-up layers of protection against these threats.
11.
If installing onto WinNT/2000/XP machines via logon script or email, a logon name and password must be defined in the RA console. To set it up, click the Remote Install tab and in the Set Default Logon for E-mail and Logon Script, click the Logon button.
If your network configuration meets these requirements, remote installation will be accomplished without communication problems between the server and the workstations.
Related NOD32 FAQ Category:
Business Edition/ESET Smart Security/Antispam module
Business Edition/ESET Smart Security/Linux/BSD
Home Edition/ESET Smart Security/Linux/BSD
Related NOD32 FAQs:
Adding/Editing/Deleting a Whitelist entry
Push Installation Errors
GLE error code 997
What does that GLE error code mean?
Email, Spamming, Hoaxes, Phishing
How to recognize spam
What is the ESET Smart Security Antispam Module?
|
