Deployment steps - Linux

These steps apply when performing a local installation of the Agent. If you want to deploy the Agent on multiple computers, see the Agent Deployment section.

Make sure the following prerequisites are met:

ERA Server and the ERA Web Console installed (on a Server computer).
An Agent certificate created and prepared on your local drive.
Certification Authority prepared on your local drive.
The Server computer must be accessible from the network.
The Agent installation file must be set as an executable (chmod +x).

The Agent is installed by running a command in the terminal (see the example below).

Example
(New lines are denoted by "\" to make it easier to copy this string into Terminal)

./Agent-Linux-i686-1.0.387.0.sh --skip-license --cert-path=/home/adminko/Desktop/agent.pfx \
--cert-auth-path=/home/adminko/Desktop/CA.der --cert-password=N3lluI4#2aCC \
--hostname=10.1.179.36 --port=2222

ERA Agent and the eraagent.service will be installed in the following location:

/opt/eset/RemoteAdministrator/Agent

Installation parameters

Attribute

Description

--skip-license

Installation will not ask user for license agreement confirmation

--cert-path

Local path to Agent's Certificate file

--cert-auth-path

Path to the Server's Certification Authority file

--cert-password

Must match the Agent certificate password

--hostname

Connection to the server (or proxy) in one of the following formats: hostname, IPv4, IPv6 or SRV record

--port

Listening port - both for the Server and the Proxy (2222)

To verify a correct installation, run the following command:

sudo service eraagent status

icon_details_hoverNOTE: When you use a certificate that you created, signed by an authority other than the ERA Certification Authority, it is necessary to leave the parameter --cert-auth-path out of the installation script, because the other Certification Authority is already installed on your Linux OS (and also on your Server computer).

icon_details_hoverNOTE: Should you experience problems when deploying ERA Agent remotely (the Server task Agent deployment ends with a Failed status) see the Troubleshooting guide.

You can check the status log on the client machine /var/log/eset/RemoteAdministrator/Agent/trace.log or /var/log/eset/RemoteAdministrator/Agent/status.html  to make sure ERA Agent is working properly.