Jump to content

j-gray

Members
  • Content Count

    274
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by j-gray

  1. I updated the client to 7.0.2091 and rebooted last night. Today I attempted to run the log collector again. Still get the same timeout error. Any suggestions how to troubleshoot log collector failures? Does the log collector create its own logs somewhere?
  2. @Marcos I've attempted to get the logs over several days, but each time I get the following: "Failed to start application | Log collector command timed out and was terminated" Didn't find any details why it's failing. Other tasks appear to be running without issue. Any suggestions how to troubleshoot this?
  3. I have a Windows workstation (latest agent, AV = 7.0.2091.0). It has been scanned three times over two days. Each scan reports the same: 'Critical': 48 infected, 0 cleaned. When I go to the linked client details, it shows only 2 warnings for PUP's in the Threats/Quarantine section. In the ERA console view, the workstation shows with a green check showing status 'OK', but also reflects the two active threats. The 'High severity scans in last 30 days' reflects the three scans each showing 48 infections. I haven't yet found a report or view that details what items are infected. My questions are: Where can I look to see what items are infected and/or why they were not handled? If the system is infected, why is not flagged as such? It shows status 'OK' and only reflects the two PUP warnings. Nothing else in the client view indicates any infections or issues otherwise. Thank you.
  4. Exactly. Though I view wake-up call more like wake-on-lan, requiring network broadcast, which is not a good practice across multiple subnets. I'm looking for a simple 'send policy' that doesn't require network broadcast. Even if it's a basic command I can run from the client (remotely).
  5. Description: Mechanism to force policy refresh on client(s) from ERA console. Detail: There doesn't appear to be a way (that I've found) to force a client to pull a new policy. We either have to wait for the policy refresh interval or create a new policy with a shorter refresh interval and apply it. It would be great to have a right-click option from the ERA console to force an immediate policy refresh.
  6. Description: Better method for detecting unmanaged clients Detail: RDS is not a practical solution in environments with multiple LANs, it can't be installed on OS X, and relies on outdated/unsupported software (WinPcap). A simple ping-sweep tool that works across multiple subnets and shows unmanaged clients, or better yet, a dynamic group that does the same so that an agent install task can be run when client joins the group. This would be awesome, especially for OS X where Group Policy automated install is not an option.
×
×
  • Create New...