stalowekk
-
Posts
8 -
Joined
-
Last visited
Posts posted by stalowekk
-
-
7 minutes ago, MichalJ said:
Hello, you will have to troubleshoot the agents connection. You can find out the status of the agent on the machine that you want to connect, in programdata/eset/remoteadministrator/agent. Try to search for "status.html" that should inform you about what is wrong. Also the "trace.log" might include any communication errors. As an ESET customer, you can entitled to contact ESET distributor for Poland, Dagma, that should be able to help you with your troubleshooting.
Thank you for your answer.
In programdata/eset/remoteadministrator/agent I don't have status.html and trace.log files
-
19 hours ago, MichalJ said:
Hello, after you synchronize the Active Directory, you need to deploy the management agent and a security product. You can use various methods for deployment, like GPO / SCCM, remote deployment tool or manual deployment by using a generated installer. None of the tasks will be working, before the machine is actually managed = agent is installed on the target computer.
I ping the ESET Security Management Center machine and it's OK. When I ping my PC from the machine, I can't see it. Does this have something to do?
-
-
It looks like there is no connection to any computer
-
Yes, that's what I mean.
-
When I tried to search for computers, I entered the data in Access Directory and the computers are visible. When try to turn off one of the computers remotely, nothing happens. Anything else I need to configure?
-
Hi.
I installed ESET Security Management Center on my CentOS. How can I add all the computers in my network now? I can see in the panel only CentOS server.
ESET Security Management Center how add all computers from my network
in ESET PROTECT On-prem (Remote Management)
Posted · Edited by stalowekk
In the path C:\Program Files\ESET\RemoteAdministrator\Agent I don't have a folder EraAgentApplicationData It probably wasn't created during installation.
EDIT: in centos (eset management) i have status.html and trace.log