ESMC VA 7.1 - can't deploy agent after upgrade

[VlP 0]

Hi.

After upgrade VA to ESMC 7.1 by update management task, I can't deploy agent to Windows Server 2019:

In ESMC agent install task shows that agent is installed fine:

 

But on server nothing is installed. So a searched for problem and see this in /var/log/messages on ESMC VA:

I tried deploy agent on WS2012R, and the same error ...

VP

 

 

Edited December 3, 2019 by VlP
cleanup image

[MartinK 384]

Could you specific whether you just upgraded ESMC in existing appliance or used upgrade method that involves migration to newly deployed appliance? Also could you verify that operating system in appliance is updated?

Also I would recommend to enable full tracing on ESMC and re-try deployment. It is possible that error is not relevant to SMB connection as indicated in provided system logs.

[VlP 0]

I have upgraded ESMC in existing appliance via management upgrade task. I have upgraded Centos in appliance via yum update and CIFS VFS error disappeared, but agent deployment to new machine still don't work.

What logs do you want to send after deployment?

 

[MartinK 384]

I would start with:

C:\ProgramData\ESET\RemoteAdministrator\Server\EraServerApplicationData\Logs\trace.log

which might indicate possible problems from ESMC perspective, but I guess there will be no issues reported directly as is reported as successful.

As a second step I would try to verify locally on problematic client whether AGENT is actually installed and not connecting, or installation itself is problematic. In case there will be no remnants of AGENT on target machine, it is probable that either installation of AGENT failed or deployment was interrupted during installer package download - for this I would verify that ESET repository servers are available form client machine.

As a last resort, it would be helpful to create AGENT live installer in ESMC (BAT-script based installer) which is identical to script executed during remote deployment - local execution on problematic client might indicate where problem is and might help to resolve deployment to other machines.

[VlP 0]

Its Centos VA, I assume you think

Quote

/var/log/eset/RemoteAdministrator/Server/trace.log

I set trace log verbosity in ESMC server to "trace" and run agent deployment task. I attached log.

Existing agents are connection to ESMC fine, only new deployent on new windows installs don't work.

trace.log

[VlP 0]

When I run agent installation via agent live installe .bat file it throws also error:

Quote

ESMCAgentInstaller.bat
Installing ESET Management Agent...
Installation failed with error code 30

 

[MartinK 384]

Thanks, error code 30 means that it is not possible to download installer package. We have recently discovered that HTTP proxy parameters are ignored during package, which would result in failure in case there is no direct connection to internet - could be this the case? Packages are by default downloaded from http://repository.eset.com/v1/ in case you have not changed it in ESMC configuration.

Also there is one long-term issue which ignores download/installation errors and reports deployment task as successful even it was not.

[VlP 0]

Yes, we have only access to internet via proxy which runs on ESMC server (only ESMC iself has direct access to internet). I look into .bat file and http proxy settings are set there:

Quote

echo.P_PROXY_HTTP_HOSTNAME=192.168.222.16 >> "%installConfigFile%"
echo.P_PROXY_HTTP_PORT=3128 >> "%installConfigFile%"

192.168.222.16 is ESMC server.

Before upgrade this scenario works without problems

[tomasS 5]

The PROXY setting you have mentioned is used for replication, not for downloading the installer(msi) package.

The batch file has to be modified, please add the following lines into it: 

set http_proxy_hostname=
set http_proxy_port=
 

[VlP 0]

After modifying script:

Quote

set http_proxy_hostname=192.168.222.16
set http_proxy_port=3128

It works, agent is installed.

Will you release patch for this?