GBO

I manage client licenses through Eset Administrator. The license pool is activated, all clients on the local LAN activate, get updates, etc I have a number of computers on a customers domain, with a network link between my office and theirs. With limited access through firewall rules. These computers have their own internet access but connection to the Eset Activation Servers is blocked. They were activated previously via a wireless dongle, everything had been ok for the last 12 months. The license was renewed on the server and local computers successfully. But the remote computers have not automatically renewed. They are connecting to my Eset Admin server, getting updates regularly. When I try using the Activate Task on the Admin server, it fails. Should the activation function work ? Is there a different port required to be open through the firewall to allow the activation to occur ? Or do all of the remote clients need access to the Eset Activation Servers via the Internet Thanks

Thanks for the response. When the computer is connected to my network, Eset is fully functional and listed on the ESMC as pc1.company.local When I move it to the Customer's network, the actual host/computer name is the same but it's DNS/FQDN is pc1.customer1.net. Eset is no longer functional, pc1.company.local is still listed on the ESMC with a connection date/time relative to when it left my network. I can ping the Server, the Port is open through the firewall back to my network. What other 'troubleshooting of AGENT connectivity' should I try ? My workaround is disconnect the Ethernet so I am temporarily isolated from the customer network. Plug in a 4G Dongle, which gives me full Internet connectivity. Within one or two minutes, Eset is now fully functional. Disconnect the 4G Dongle, re-connect the Ethernet. Within 20 minutes, it is listed on the ESMC (pc1.company.local has been automatically renamed to pc1.customer1.net). The updates then get deliver ok and I can apply policies as required. You mention 'manual approval is required in ESMC console -> this should be visible in "questions" section'. Where is the "questions" section ? Again, thanks for you help.

When I re-locate it to the customer domain, it has a different DNS suffix and a different IP address, and it does not show up on the ESMC - even though the server is accessible via the Firewall. Is because the DNS and IP Address are different, that the ESMC is not recognizing it ? All the groups I have are static, should I be using Dynamic instead ?

Depending on requirements I often move computers from my domain to a customer's domain, where communication for Eset traffic is allowed through the Firewall. For explanation, called them company.local and customer1.net In all instances they report back to the ESMC in my network So I could build a computer called pc1, install Eset Business Security, it gets activated and is displayed in the ESMC as pc1.company.local I remove the computer from my domain and plug into the computer's network and join their domain. The DNS is now pc1.customer1.net. The problem is that while the computer has general Internet access, activation is blocked through their Proxy. The computer loses its activation, hence Eset is not functional. Is there any way I can change the configuration, so the computer retains it activation ? Hence the ESMC recognizes the new name to match the old one. Thanks Greg

I upgraded some clients to Management Agent 7.2.1266 and Endpoint Security 7.3.2032 After this I cannot enable the Firewall The previous version was Management Agent 7.1.717 and Endpoint Security 7.2.2055. They are in the same folder on the ESMC as before, so no policies have changed. Are there any changes i need to make to the Policy to force firewall on ? Thanks

I used the Mirror Tool to create a offline repository. I wanted an English, Windows version of Antivirus Security. I used the following commands: MirrorTool.exe --mirrorType regular ^ --repositoryServer AUTOSELECT ^ --intermediateRepositoryDirectory E:\Temp\IntermediaryFiles ^ --outputRepositoryDirectory E:\Temp\FinalRepository --languageFilterForRepository en_US ^ --productFilterForRepository Antivirus Security ^ --offlineLicenseFilename c:\temp\Esetendpointsecurityforwindows.lf But I also get the files for Linux, Mac and all Languages. Am I doing something wrong ? Thanks

So, are you saying it is not possible for the clients to get their updates directly the ESMC server ? We did it this way in v5

The machines do connect to the Internet via a proxy, but the customer decides what web sites are accessible. I realize some features such as Live Grid will not be available So the clients show up on the ERA Console, reporting that they are connecting every 20 mins. But they are not receiving updates. Does all of the update communication between the client and the ERA go via 2222. If not which port does it use. Looking at this diagram https://help.eset.com/esmc_install/70/en-US/ports_used.html, I assume all updates would go via port 2222 ?

Hi Marcos, My email to support was initially blocked because of the log file. The case number raised is 376091, support advised us how to create and apply an Offline activation. It seems the client is now activated – but the Endpoint fails to update the Modules. Times out, trying to find the server. Although the Console is showing the client as connecting every 20 mins When I create the installer from the ESMC, do I have specifically configure it so the updates come from the ESMC. Or is this automatic ? What else can I check to establish why it is not finding the update server ? Thanks

I have ESMC version 7.1.12006.0 Server was installed with standard port of 2222 Operating System is Windows Server 2016 Standard All clients on the same LAN as the server install and activate ok, and are fully functional Clients (mix of Windows 7 and Windows 10) on a remote customer’s network have a restricted connection to my local LAN. Port 2222 is open to allow traffic. From the client computer, I can ping the server. After installing the client, it fails to activate. Although the clients are listed on the ESMC console, but show errors because they are not receiving updates When run a repair on the Eset Management agent, it confirms that the connection to the server is Server: 2222 The clients connect to the Internet through a Proxy. From a browser, when I enter https://edf.eset.com/edf it displays the xml code <ecp:message xmlns:ecp="hxxp://www.eset.com/2012/02/ecp"> <ecp:response> <code>20101003</code> <message>Unsupported Content-type: unknown</message> </ecp:response> </ecp:message> From the client, I have also tried to activate the client via my license key After a long delay, if fails and says it could not reach the activation server with an error code of ECP.20003 When I try to activate via the Security Admin Account login, I get this screen about ‘Unit Distributions’ ? I also logged the above message via the web site, and direct to au.support@eset.com but did not receive any confirmation that a support case is created. Note, everything worked fine previously with v5 of the ESMC and v5 clients. Please help, what else do I have to get this clients activated ?