Upgrade infrastructure with ERA 6.5 Proxy

The ERA Proxy component is discontinued since ESMC 7. There is a replacement proxy solution available. During the upgrade of your infrastructure (Server and Agents), you have to migrate your proxy solution.

Before the upgrade, read the information below.



Be careful about connection compatibility:

ERA Version 6.x Agent can connect to ESET PROTECT Server.

ESET Management Agent (since version 7) cannot connect to ESET PROTECT Server via ERA Proxy.

ESET Management Agent (since version 7) cannot connect to ERA.

The communication protocol between Agent and ESET PROTECT Server does not support authentication. Any proxy solution used for forwarding Agent communication to ESET PROTECT Server and requiring authentication does not work.

Do not upgrade ERA Agents (connecting via Proxy) before a proper proxy solution is set up.

Upgrade scenarios

If you are running an environment which is using the ERA Proxy component, follow one of the scenarios below to upgrade your infrastructure to ESET PROTECT 8.

ERA Proxy installed on Windows (this page)

ERA Proxy installed on Windows (Knowledgebase article with more detailed instructions)

ERA Proxy deployed on Linux or as a Virtual Appliance (Knowledgebase article)

Upgrade infrastructure with ERA Proxy installed on Windows

1.Back up your ERA Server.

2.Upgrade your ERA Server to ESET PROTECT 8 via Remote Administrator Components Upgrade Task. (Server, Agent and Web Console are upgraded)

3.Wait approximately 24 hours to make sure that the upgraded environment runs smoothly.

4.Upgrade the ERA Agent on the ERA Proxy machine via ESET PROTECT Components Upgrade Task.

5.Install Apache HTTP Proxy on the machine where the ERA Proxy is installed. Use the pre-configured ESET version of Apache. (download link)

6.Modify Apache HTTP Proxy configuration file httpd.conf located in C:\Program Files\Apache HTTP Proxy\conf.

a.By default, the port 2222 is used for communication with the ESET Management Agent. If you have changed your port during the installation, use your port number. Change the 2222 in the line: AllowCONNECT 443 563 2222 8883 53535 for your port number.

b.Add a separate ProxyMatch segment:

I.The address which your Agents use to connect to the ESET PROTECT Server.

II.All other possible addresses of your ESET PROTECT Server (IP, FQDN)
(add the whole below code; IP address and hostname hostname.example are only examples to be substituted by your addresses. You can also generate the ProxyMatch expression in this Knowledgebase article.)

<ProxyMatch ^(hostname\.example(:[0-9]+)?(\/.*)?|10\.1\.1\.10(:[0-9]+)?(\/.*)?)$>

Allow from all


c.Restart the Apache HTTP Proxy service.

7.Create a new policy on your ESET PROTECT Server.

a.In the ESET PROTECT Web Console click Policies > Create New.

b.In the Basic section, type a Name for the policy.

c.In the Settings section select ESET Management Agent.

d.Navigate to Connection > Server connects to > Edit server list.

e.Click Add and enter the address the of the proxy machine (the machine where the ERA Proxy is installed) in the Host field. Click OK.

f.Repeat the step above and add the address (the address must match what was used for Agent configuration) of your ESET PROTECT Server.

g.Click Save.

h.Navigate to Advanced Settings > HTTP Proxy and set Proxy Configuration to Different Proxy Per Service.

i.Click Replication > Edit and enable the Use proxy server option.

j.Type the IP address of the proxy machine to the Host field. (the IP address is only an example, replace it by your address)

k.Leave the default value 3128 for the Port.

l.Click Save and Finish to save the policy. Do not assign it to any computer yet.



It is absolutely necessary to have both IP addresses in one list applied on the client. If the Agent does not have this information on one policy, it will be unable to connect to the Proxy and Server after the upgrade. Such an Agent must be fixed manually by running a repair installation and using the correct ESET PROTECT Server address.

If HTTP Proxy setting is not applied in the policy, the Agent will not be able to connect the ESET PROTECT Server.

8.Choose one computer which is connected via ERA Proxy and assign the new policy to that computer.

9.Wait a few minutes until the policy is applied and check if the computer is still connecting the ESET PROTECT Server.

10. Run the ESET PROTECT Components Upgrade Task to upgrade the client.

11. After the client is upgraded to version 8, check if it is still connecting to the ESET PROTECT Server. If the computer is successfully connecting after the upgrade, continue to upgrade other computers.



If you have a larger network, begin the upgrade at departments with IT experienced users or those who are physically closer to computers to make the troubleshooting easier.

12. Apply the policy (from step 7) to other computers connected via the ERA Proxy.

13. Wait a few minutes until the policy is applied and check if clients are still connecting to the ESET PROTECT Server.

14. Run the ESET PROTECT Components Upgrade Task on these clients.

15. If all clients are connecting to the ESET PROTECT Server after the upgrade is finished, you can proceed with next steps.

16. Modify the policy (from the step 5). Navigate to Policies > click the gear icon next to the policy you want to modify and click Edit.

a.In the Settings > Connection click Edit server list and remove the address of the ERA Proxy machine.

b.Click Save.

c.Click Finish to save and apply the policy.

17. Remove the ERA Proxy using Tasks > Software Uninstall.