Jump to content

Agent install fails - ERA 6.1.444.0


KeithWilliams
 Share

Recommended Posts

Good day all,

 

I have installed ERA ver 6.1.444.0 with web console ver 6.1.334.0 on a VMWare Windows Server 2012 R2 server.

I have been able to deploy the agent to one computer that is on the network, but it will not push to any other system. With each attempt I am getting the FAIL message and states to generate a report, or check the trace.log file for details. The report that is generated, just tells me to generate a report, or check the trace.log file. So, I set the trace log verbosity to ERROR, but I am unable to even find a trace.log file. 

 

Things I have checked and verified:

The server sees the computers on the network.

The computers see the server on the network.

The computers are tractable in DNS and register in AD.

The registry settings are correct.

The ERA ports are set correctly.

One computer has successfully had the agent deployed.

 

Have I missed something?

 

Thanks,

 

Keith

 

Link to comment
Share on other sites

  • Administrators

First of all, please send an ERA Component Upgrade task to the computer with ERAS installed so that it upgrades to the latest version 6.2 which contains a lot of improvements and fixes. How did you deploy agent on the client? Using a push install, agent live installer or agent mst transformation file deployed through GPO?

Link to comment
Share on other sites

The deploys were done from the ERA WebConsole, directly from the computer list (Left click, Deploy Agent, Deploy Agent from ERA server), and also from the Admin tab, under Server Tasks and Agent Deployment and setting up a specific task. The first system (a test) to which it was done was successful. Then, I set a task to deploy to all computers on the network (215 total systems) and this failed. So, I tried it in blocks of 20 systems, then 10 systems then 1 system at a time. Attempted this on about 10 different systems and it failed individually on each one. 

On the first test deployment, which was successful, I simply deployed the agent, as this is a new install on this network and all of its computers and servers. The first deployment worked fine, as did the remote install of the Endpoint AV. I did not have to send an ERA Component Upgrade Task (Again, this is a brand new install of ESET software to this network.)

Edited by KeithWilliams
Link to comment
Share on other sites

  • Administrators

Push installation requires a bunch of conditions to be fulfilled to complete. Would deploying agent live installer through GPO or mst file be a problem?

Link to comment
Share on other sites

Yes. I saw the list of requirements. They were met before I did the test push, which is why, I assumed, that it was successful.

 

I can do it through GPO, but am not the biggest fan of how GPO works in 2012, so I would prefer not to use it, unless absolutely needed.

Link to comment
Share on other sites

I have managed to get the report to be created and discovered that the problem is a permissions issue. I am logged into the server as the administrator. However, the USERNAME and PASSWORD that I am using has permissions to all of the systems on the network, and it failed. I have also tried the local admin accounts, which also failed. I have even tried the ERA admin account for the push, which failed. You cannot leave the fields blank, so I cannot use that as an option.

 

At a loss here. Anyone have any other ideas?

 

Thanks

Link to comment
Share on other sites

This is the note from the generated report -

 

Windows network remote deployment failed because remote ACCESS WAS DENIED to the target WINDOWS machine. Verify that:
 
1. 'XXXXXXXX' has administrator rights or use local 'Administrator' account that is enabled on the target machine. (XXXXXXXX being the admin account name - and this has been done.)
 
2. 'XXXXXXXX' password is not blank. (The password field is not blank)
 
3. You can remotely log on to the workstation from the server. (This has been verified)
 
4. From server machine you can access 'net use \\computername.COMPANYNAME.local\IPC$' from the Command Prompt. (This has been verified)
 
5. Change 'ESET Remote Administrator Server' service credentials from 'Network Service' to user with domain administrator permissions temporarily for deployment. (This has been done.) (edit - Yes, I stopped and started the service after changing the credentials.)
Edited by KeithWilliams
Link to comment
Share on other sites

  • ESET Moderators

Hi,

Actually, deployment via GPO or SCCM is preferred, as the communication with the client computer is already in place and does not have to be enforced by setting several permissions, etc.

As the push installation only uses the existing Windows platform with its possibilities (and limitations), the troubleshooting of this method needs to be done on the system level, not on ERA level.

Link to comment
Share on other sites

  • ESET Moderators

No, this is the advantage of the Agent. Once it is running locally on the client PC, it receives commands from the ERA server and can execute the installation of the Endpoint, without the need of pushing the installation remotely.

You basically have an "insider" on the PC with local administrator rights and you direct this Agent via tasks from ERA.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...