ElJuan

Hello Stefan, because I had the same issues of you..... I posted another ways to deploy the agent+endpoint, and it is working fine in my scenario. https://forum.eset.c...gether/?p=29233 hope this can help.

Great to hear that. anytime..!!!

hello it is not necessary AD for use Transform file and deploy. and thanks for sharing your scripts

What if you use the following expression: OPERATION: AND (All conditions have to be true) Network IP address.Adapter IP address greater or equal 172.17.77.1 and Network IP address.Adapter IP address less or equal 172.17.77.254 In my scenario this rule works fine for dynamics group. Hope this can help.

Hi, I have spent a lot time doing a thousand of different ways to deploy the endpoint, and I found that the smoothest and efficient way is firstly remove the old enpoints, in my scenario the clients computers have ESET smart security version 4 & ESET nod32 Antivirus version 4 installed, you can remove the endpoint in a massive way with pstools deploying the following script (example): start /wait "" msiexec /x \\servername\ESET\SmartSecurity\essbe_nt64_enu.msi /qn /li "C:\%computername%_gp-secx64.log" and yes,, if necessary the reboot to complete the uninstallation. (also I see other comments that if you have eset endpoint 5 the upgrade must work with the single instruction msiexec /x) another way... I have create a gpolicy in active directory, and in the scripts of shutdown options I configured the uninstaller command, then and same policy configure the software installation with the MSI + the MST files. so the client computer during the shutdown process must remove the old endpoint and during the start up process must install the new endpoint. (actually this is the process that is working better). ...... hope this can help

Hello Mfichera I have the same issue. But I found another ways to deploy the agent+endpoint, and it is working fine in my scenario. https://forum.eset.com/topic/5140-another-way-deployment-agent-and-endpoint-together/?p=29233 hope this can help.

good for that one. it is working pretty good I wonder is there a way to add this parameter for installation with gpolicy from active directory ? thanks

Hello Anto 33. I posted another ways to deploy the agent+endpoint, and it is working fine in my scenario. https://forum.eset.com/topic/5140-another-way-deployment-agent-and-endpoint-together/?p=29233 hope this can help.

Hello, could you explain a bit more about how "Export Managed Products Configuration" client task works ? Is this task force to push the configuration to the target pc? If yes, How do you specify what configuration push? I have had some issues when clients that not refresh firewall rules, so for me , the quickier solution is remove and re-deploy the agent + endpoint.

Thanks for share, I had to find another way to deploy instead of ERAS console too. I just create an exe file with winrar and put inside an small script with the following instructions: start /wait " " msiexec /i \\fileserver\sharename\agent.msi /qn TRANSFORMS=\\fileserver\sharename\agent.mst /li c:\agent.log start /wait " " msiexec /i \\fileserver\sharename\endpoint.msi /qn /li c:\endpoint.log Now you can deploy the exe (or the batch file) with pstools. I have made successfully deployments with tools like: pstools, Active Directory-GPolicy and Lansweeper. Note. In the ERAS guide you can find how to create the transform file. Hope this can help.

Hello This tip not fix the warning (in my case). thanks

Hi Jedduff, I have the same issue, and happen with ERA Server & Proxy OVAs. I glad to hear you are using vmware viirtual appliances. although the server is working properly I hope some else have found a fixed for this bug. regards.

Shawkins. I have experimented almost the same issues that you have. and I have spent a lot of time resolving issue by issue, that I would like to share. because my scenario is that we have a classic Squid Proxy for the Internet access, the activation issue was solved adding the following lines in the httpd.conf of the apache server configuration from the ERAS Server : ProxyRequests On ProxyVia On ProxyRemote * hxxp://squidserverhostname:3128 This was successful tested in Windows & Virtual Appliance (Linux Centos 6) also make sure you have this PC client configuration in Advanced setup/Tools/Proxy: Proxy server = use proxy server enabled Proxy server = hxxp://erasserverhostname Port = 3128 you can create an Eset Securty Product Policy to push the above config. This configuration may solve the update definitions issues. I would like to hear if this can help. regards.

Hi Brad. Could you post the information of the following files: status & trace (from a PC Client with the issue) C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs Also maybe you have already tried, if not, turn off the firewall in both sides, PC & ERAS server. regards.

Hello. Where I can find the steps to deploy the OVA from vmware vcenter (using vsphere web client)? During the wizard there are some fields to fill. (About connect the eras proxy with the eras server) Also I would like to know the best practices so the clients computers have redundancy in case 1 eras is down. I really appreciate any help See the attached.

Hello, In my scenario, I have PCs with eset smart security 4 and was not necesary to apply the AVRemover...EXE file. I just apply the following command for make the upgrade to eset endpoint security version 6. msiexec /i "\\servername\sharefolder\\eset_endpoint_security.msi" /qb! REBOOT="ReallySuppress" Note. Remove the password that open endpoint ver 4 in case is configured before apply the command msiexec ..... Hope this can help.

Hi, The Virtual Appliance (OVA) is not an option for you? Saludos.

did you try with the scrips generated from your ERAS server? It is a bat file then you can run manually in the pc clients. Hope this can help. Saludos