Gakusei 0 Posted June 15, 2018 Share Posted June 15, 2018 We have installed ERA onto a brand new VM. Everything installed fine and I set up a new Agent install task through ERA. I was able to push the Agent to 2 of 7 servers. 1 server failed, which can be expected, but then the task sat for two days running before it timed out. No more servers were touched by the task. Weird. So after it timed out, I modified the task to only push to one server and started the task. Now it's stuck on 'Starting task' and it hasn't made any further progress. It doesn't even show as running - just simply Starting task. I created a second agent task and put a few other servers on it. Same thing - ERA Agent Installer stuck on starting task. So I created a 3rd agent installer task, this time pointing to the server that failed. I figured it ran then. But that too doesn't run - it stays stuck on 'starting task'. Any ideas? In the mean time I will keep poking around. Link to comment Share on other sites More sharing options...
Bishop200 0 Posted June 18, 2018 Share Posted June 18, 2018 Just got that problem with 2 computer. It was the Windows Firewall who, even if disabled by GPO, was bloking some port needed for the agent install. I added a rule to allow inbond connection for the port needed and the install have worked correctly even if the firewall was still off at that point... Still wondering if MS did something silly with a update. Link to comment Share on other sites More sharing options...
Gakusei 0 Posted June 19, 2018 Author Share Posted June 19, 2018 On 6/18/2018 at 12:05 PM, Bishop200 said: Just got that problem with 2 computer. It was the Windows Firewall who, even if disabled by GPO, was bloking some port needed for the agent install. I added a rule to allow inbond connection for the port needed and the install have worked correctly even if the firewall was still off at that point... Still wondering if MS did something silly with a update. Hmm. Do you remember what port(s) you had to whitelist? I had turned the Firewalls off thinking this was the issue, but it still didn't work. Of course, I have seen the firewall block ports despite being off, but its rare. Link to comment Share on other sites More sharing options...
Administrators Marcos 4,694 Posted June 20, 2018 Administrators Share Posted June 20, 2018 Deploying agent via GPO should prevent many potential issues with push installation. Or use psexec : For more information about methods of deploying agent, please refer to https://help.eset.com/era_smb/65/en-US/deployment_tool.html. Link to comment Share on other sites More sharing options...
Recommended Posts