How to connect a linux server with Remote Administrator?

[Moriort 0]

Hello, I have a doubt, inside my business network everything is running normally when using the agent and Eset endpoint (Windows), but I want to know how to use the agent and the endpoint in a File Server or (CentOS), in addition I have File Security and Mail Security, but if the computers are on an external or virtualized server, what is the procedure to administrate the server from Eset Remote Administrator?

[MichalJ 434]

You have to deploy ESET Remote Administrator agent on the Linux Server. You can achieve this in the simplest way by generating an agent live installer script, that you will execute on the machine, where Mail / File Security is installed. You have to have a network connection established between the ERA Server and the Linux machines.

Once ERA agent is installed, just connect the Linux Server product to connect to a remote management server on "localhost" and port "2225", as that is the way how older products (V4/V5) can interact with ESET Remote Administrator agent.

Since the product is connected, you can manage it in the same way as the Windows Endpoints.

PS: We would appreciate some patience. Majority of the ESET People and community here is located in Europe, meaning during the time you have asked your question, there was a deep night. Also, in case of any question, always feel free to contact your official ESET customer care representative, based on the country of your residence.

[Moriort 0]

I do not understand, I have on the same ERA server, a virtualized computer with MVware (CentoOS 6.9), install the agent using the certificate provided in the administration panel, but it still does not appear in the ERA administration. If this does not work with a virtualized machine, I find it difficult that I can achieve it on a computer external to my network.
 

[MartinK 384]

1 hour ago, Moriort said:

I do not understand, I have on the same ERA server, a virtualized computer with MVware (CentoOS 6.9), install the agent using the certificate provided in the administration panel, but it still does not appear in the ERA administration. If this does not work with a virtualized machine, I find it difficult that I can achieve it on a computer external to my network.
 

Please follow AGENT connection troubleshooting steps described in documentation. I would recommend to start checking status.html as it will contain connection relevant error. Also check timestamp of this log, as it is possible that AGENT is not even running, and log may be outdated.

Regarding administering computers outside of your network, there are few critical requirements you have to handle (most common issues):

• you have to configure your network/firewalls so that port 2222 is accessible from managed machines. Port may be changed in ERA Server configuration.
• You ERA Server certificate must be signed for external hostname/IP, i.e. "Host" field of certificate must contain either * (asterix = any hostname will work) or external hostname used by AGENTs to connect. In case certificate is not signed for required hostname (or does not use *), new certificate has to be created, and ERA Server has to be configured to use it.
• When AGENT installer are generated, it is possible to override "Server hostname" field with your external hostname or IP address. Otherwise AGENT will be connecting to default hostname, that was detected during ERA installation -> and this may not be working with AGENT in external network.

[Moriort 0]

I have solved this problem thanks to the above mentioned indications.

Thanks very much!