gimel

I just installed the ERA 6.5 Virtual Appliance hoping management would be easier compared to my ERA 6.4 installed on Windows. Well, from a first VA installation, I could install agent 6.5 on a remote machine (Win7 Pro) so the target computer is setup correctly (no blocking firewall or anything). Now comes the weird part... For different reasons, I installed again the VA from scratch. I now tried to deploy the 6.5 agent to the same target as before. Here is what happened and some hints to improve ERA: The task fails because of "one of 12 potential problems". Excuse me but if the code fails, it should know which action failed *exactly* and it should tell me which problem it is *exactly* instead of giving me 12 potential problems. As an example, it says "check the server can ping the target" but can't ERA do the ping and tell me if it succeeds or not? Well, the purpose to install a VA and an administration backend is to make my work easier. ;-) Then, 30 minutes later, the same task just succeeded without submitting it again. Why that? Does ERA do several attempts? If so, it should have tell me "failed once, will try again N times".

Here is how I deleted ESET v6 : - restart the computer in safe mode - rename "C:\Program Files\ESET" in ESTold - restart the computer in normal mode - rename the directory back to "ESET" - uninstall ESET from the control panel @Eset support You now owe me a box of chocolate as a lot of users won't bother you with such issues :-D

It works here too. Thanks EdSatori.

And the result is ...?

@Marcos A new dump : ftp://eset:eset@ftp.gimel.fr

One computer just had a freeze while the user was working so the problem might occur not only when the computer goes in standby. :-/ You can download the memory dump from here: After I did the dump, I thought it would have been better to boot into safe mode after the crash/freeze so that I don't load Windows with every program. This way memory has less chance to be trashed. Right?

Thanks. Computers are configured. Now waiting for a crash to occur (probably tomorrow morning).

I just uninstalled Endpoint 5 and installed Endpoint 6 on several Windows 7 machines. Now I have the same problem on several computers: The computer goes in standby and is frozen. The monitor stays in stanby when trying to wake up the computer. Sometimes the monitor awakes and I can see the mouse pointer but nothing else (black background) then after a few seconds the system freezes. I always have to cold reboot the computer. Of course, I could disable the standby on all computers but it's not a good solution. It may be the same as this: https://forum.eset.com/topic/3932-windows-sleepshut-down-problem/ Any information on such issue?

I have the same problem here on several Windows 7 machines, with ESET Endpoint Antivirus 6. The computer goes in standby and is frozen. The monitor stays in stanby when trying to wake up the computer. If the monitor awakes, I can see the mouse pointer but nothing else (black background) then everything freezes. I always have to cold reboot the computer. Who has a solution?

@GreenEnvy22 Your main problem is your bad connection lines. In my company, I installed ERA6 on my server (replacing ERA5). I deployed the ERA6 agent to the clients in my Windows domain, even though they were running Endpoint V5 (both work together). Not all agent deployments worked (I have to send the updates by GPO/login script). All clients running v5 with the agent installed, reported directly to my ERA6. On clients with the agent, I could push the installation of Endpoint V6 that replaced V5 silently (reboot required of the client).