Help with ESMC + ESET Endpoint + Agent (Latest Version)

[agent47 0]

Hi All,

A newbie here for ESMC and ESET stuffs. Would like to share my problems and seek for any inputs and assistance. I would provide as much details as I can so please bare with me

-- Everything down below are joined into a Domain --

• 1) ESMC installed on Server 2012 R2 (used an All-in-one installer) and configured the basic one so meaning no proxy etc because Im on a testing phase for this version
• 2) Desktop or client-side are Windows 10 Pro
• 3) Firewall Policy are all set for this testing so meaning the Server to Client all services allowed vice versa
• 4) Client-end Windows Firewall turned off completely
• 5) ESET Server and Client can see each other

 

What I have done so far by means of exploring and playing around and such + Problems encountered

• 1) Manually installed on client-side the agentx64.msi + eea_nt64.msi file to PC7 = ESMC able to see the PC7

• 2) Manually installed on client-side the agentx64.msi + eea_nt64.msi file to PC9 = ESMC are not able to see the PC9

• 3) Tried to use GPO Push installation for PC7 and PC9 and It was verified working upon testing frequently. However ended up the same as above issues.. ESMC cannot see any products installed for PC09 only..
• 4) Uninstalled everything using a .bat file to wipe Agent and EEA application and to completely remove "C:\Program Files\ESET" folder to start a new test but unfortunately, problem was still there..

I am confused and stuck up. This only happened when I upgraded from the latest version of EEA 7.2 and Agent 7.1 as well as the ESMC Server 7.1.717.0

Quote

I do not have this kind of issue on my previous version. ESMC and Clients (800+) are all reporting and sync on my servers. I can manage them all at once If I wanted to using ESMC.

I have installed the latest ESMC All-in-one already and perform the basics as aforementioned

Another thing is I cannot perform Task Activation on PC7 even if I followed the guide from here.

Please see the attached Server Log and PC7 Log.

pc07.rar server.rar

Edited December 2, 2019 by agent47
spelling

[Marcos 5,074]

The log from the client shows

ERROR: InitializeConnection: Initiating replication connection to 'host: "localhost" port: 2222' failed with: GetAuthenticationSessionToken: Failed to fetch device session token in time

I assume that it should not be localhost where the ESMC server is running.

[agent47 0]

Hi Marcos,

Thank you for the response. I have checked the Policy for Management Agent and the ESMC Server IP were already added.

I am sorry and Thank you

Edited December 2, 2019 by agent47

[agent47 0]

Hi Marcos,

I have double check the build-in policies. Saw some items that I have missed. Removed everything except the Custom Policies that I have created for this testing.

Will update here for the result.

[Marcos 5,074]

If necessary, reinstall or re-deploy the ESMC agent with a correct IP address of the ESMC server.

[agent47 0]

21 minutes ago, Marcos said:

If necessary, reinstall or re-deploy the ESMC agent with a correct IP address of the ESMC server.

are you referring to installing the "ESMCAgentInstaller.bat" file Sir? I downloaded it from ESMC server and already run-as-administrator the .bat file

OR

should I remove and uninstall first the Agent on the problematic testpc then run this .bat file?

Thank you.

[Marcos 5,074]

It doesn't matter. If you run the batch file, view it and make sure it contains a correct IP address of the ESMC server. Alternatively you can run the agent msi installer and enter ESMC server's IP address in the installation wizard.

[MartinK 378]

From provided logs also it seems that peer certificate for AGENT might not be configured properly - it is not visible from screenshot but in case it is applied by any of your policies, please make sure it is correctly set with proper password if used.

Also as mentioned, as client is configured in a way it won't be possible to connect to ESMC, only possibility is to re-deploy, i.e. perform installation repair with new set of parameters. Technically any deployment method might be used, including manual installation, script based live installers and also bundle installers.