Jump to content

ewong

Members
  • Content Count

    79
  • Joined

  • Last visited

  • Days Won

    1

ewong last won the day on December 13 2018

ewong had the most liked content!

Profile Information

  • Gender
    Not Telling
  • Location
    Hong Kong
  1. I'm seeing the following in Status.html (as well as the trace.log): Error: CReplicationManager: Replication (network) connection to 'host: "192.168.8.25" port: 2222' failed with: Receive: NodSslWriteEncryptedData: Incorrect/unknown certificate or key format. Which I think might help. Edmund
  2. To answer my own question: c:\Documents and Settings\All Users\Application Data\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs
  3. Hi Marcos, What is the equivalent directory on XP? Edmund
  4. Hi, Versions: ESET Security Management Center (Server), Version 7.0 (7.0.577.0) ESET Security Management Center (Web Console), Version 7.0 (7.0.429.0) I've synchronized SMC with the AD so the SMC now has the list of systems. While the majority systems have checked in, I still have some that are still at "Unknown" status. I've set the GPO policy to set the firewall to allow the agents to connect to the SMC; but still, they aren't connecting. I have 4 XP systems and 1 Windows 7 and 1 Windows 8.0 systems not yet connecting. Aside for the DNS/rDNS setup and the firewalls, what other things should I look at? Thanks! Edmund
  5. Description: Showing (or downloading) debug logs when tasks fail. Detail: Somewhat similar to my previous feature request, having the debug log generated during the task (akin to trace.log) and when it fails, there is a link to download the log file for that particular process. Rationale: It's to allow the Remote Administrator to figure out what is going on within the process without needing to go into the client's workstation.
  6. Description: Running tasks progress Detail: Currently (well I'm upgrading to the latest 7.x ERA with the 6.x component upgrade task), when I go to Client Task Executions, it states that the task is running. If there is a way (particularly with the Eset product-based tasks, for some sort of progress showing (and even an ETA (but I suspect this might be a bit tough)).
  7. I'd like to add to the Sorting/filtering item. Description: The current filtering prepositions are limited and a little confusing. Detail: I was looking at the "Last Connected" report template on the Dashboard, and I had recently added a whole bunch of rogue systems to a subgroup under "Unknown" static group. By default, the "Last connected" report includes all systems. I wanted to filter out the "unknown" static group and its subgroups. I tried creating a filter: Static Group; Static Group Parent Hierarchy in Unknown which obviously isn't what I want; but there's no "not in". And there's no obvious way of setting "All" computers but exclude the static group "Unknown". So I thought I'd try: Static Group = All Static Group; Static Group Parent Hierarchy not equal Unknown. That didn't work. So having more prepositions (if that's what you call them) would help a lot.
  8. Description: Able to determine the "reason" why the task failed in the Task Execution History. Detail: Right now, suppose a task failed for a particular system. In ERA, you go to that system, go to "TASK EXECUTIONS", select the task entry, and then right click and select "History", it would show something like: 2018 Mar 22 16:06:58 Security product Failed Task failed Task failed in the security product There's no way to find out "why it failed" until I go directly to that system and do a manual check. Having some sort of reason why it failed helps the sysadmin to figure out how to get it updated, if it is at all possible.
  9. Interesting that I came across this topic as I'm currently wondering about this exact same issue. I have one particular instance in which I have a list of PUWAs and I have no idea how to just kill them without manually going to the particular workstation and regediting it or deleting it. So yes, I would appreciate a strict cleaning mode in which PUWAs are eliminated with extreme prejudice. Alerts should only be sent to the administrator as end-users are 'normally' clueless with what to do with them.
×
×
  • Create New...