Jump to content

ewong

Most Valued Members
  • Content Count

    199
  • Joined

  • Last visited

  • Days Won

    1

Kudos

  1. Upvote
    ewong received kudos from mmadeira in Upgrading Agents 7.1 -> 7.2   
    never mind..  Sorry for the noise.  [1] answered my question.
     
    [1] -
     
  2. Upvote
    ewong received kudos from mmadeira in SCM 7.2: How to deal with 6.X agents prior to 6.5   
    In my experience with Pre-6.5 agents on XP machines and in some cases, Win7 machines, I've always had a problem getting the agents on these machines updated.  Even with GPO,  these agents would always fail to update.  I would end up just copying the EsetUninstaller.exe to these machines and running them in safe mode to get rid of the agent and av software.
    I too had spent a lot of time fiddling with ESMC and GPOs to get the Agents updated but gave up and did it the hard way. 
    That said, have you taken a look at the agent logs on the problematic machines?  These logs should at least point you to what's bugging the update process.  That's the way I had figured the XP agents weren't liking the update command.
     
  3. Upvote
    ewong received kudos from Zen11t in Future changes to ESET Security Management Center / ESET Remote Administrator   
    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.
  4. Upvote
    ewong received kudos from katycomputersystems in Future changes to ESET Security Management Center / ESET Remote Administrator   
    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.
     
×
×
  • Create New...