ESET PROTECT is the renamed ESET Security Management Center (ESMC), the new name is used since version 8.0. It uses the agent/server communication protocol introduced with ESMC 7.0. The communication protocol uses TLS and HTTP2 protocols to go through proxy servers, self-recovery features, and a persistent connection that improves overall communication performance.
ESET provides a pre-configured Apache installer. The user can also use other proxy solutions (besides Apache HTTP Proxy) that fulfill the following conditions:
The configuration of other proxy solutions is not provided or supported by ESET. Other solutions may not support caching of ESET Dynamic Threat Defense (EDTD) communications.
The ESET PROTECT Virtual Appliance contains a correctly pre-configured Apache HTTP Proxy. We recommend you use the new appliance instead of upgrading the old one.
To keep your proxy safe and well configured, replace your old ERA Proxy - Virtual Appliance with the new version. ESET PROTECT does not provide a stand-alone proxy configuration as ERA 6.x did. We recommend you deploy a new ESET PROTECT Server - Virtual Appliance. The new server is not used as an administrative server but as a proxy. The correctly configured Apache HTTP Proxy is included in the ESET PROTECT Virtual Appliance download.
Replace the hostname and password values with actual values from the main ESET PROTECT Server. For more information, refer to the Agent installation - Linux topic in the ESET PROTECT Online Help Guide.
|System V init||Systemd|
To prevent ESET PROTECT and MySQL services from starting after reboot, disable them:
AllowCONNECT 443 2222and change
2222to the number of your port.
systemctl restart httpd
Click Settings, select ESET Management Agent.
Expand Connection, click Edit server list next to Server connects to.
In the Host field, type the applicable address (the address must match what the agent uses in the configuration) of your ESET PROTECT Server and click OK.
In the Policy settings drop-down menu, select Append.
Expand Advanced Settings. In the HTTP Proxy section, select Different Proxy Per Service from the Proxy Configuration drop-down menu.
Next to Replication (to ESET PROTECT Server), click Edit.
Choose one computer that is connected via ERA Proxy and assign the new policy to that test client.
After a few minutes, verify the computer is still connecting to the ESET PROTECT Server.
Verify the client is connected to the ESET PROTECT Server. Continue upgrading the remaining clients.
After the policy is applied, verify all clients are connecting to the ESET PROTECT Server.
Run an ESET PROTECT Components Upgrade Task.
If all clients are connecting to the ESET PROTECT Server after the upgrade is finished, proceed to section V. below.
In the Policy settings drop-down menu, select Replace.
Click Finish to save and apply the policy.