Jump to content

circumpunct

Members
  • Content Count

    18
  • Joined

  • Last visited

Profile Information

  • Location
    Saudi Arabia

Recent Profile Visitors

392 profile views
  1. The main thing I'm not happy with in the current release is the way it serves up alerts to historic errors that have gone away. Here is an example: We have a lot of laptops that get carried around. When they are on site, the are on our LAN and the agent talks to the ERA - and when off site they do not. As soon as they get on the LAN after a trip outside, the ERA starts showing 'could not connect to server' errors. Obviously they could not connect to our server when they were off site and the time of the 'errror' reflects this. But as soon as they are back on site they connect and the
  2. Problem solved. It was showing in the 'not connected' report of ERA, but it seems to have been old data. We deleted it from ERA and let it recreate itself and now all is fine.
  3. Yes, that is the tail of the log file including the last line. Status file shows all green. No errors.
  4. Thanks Jim. What am I looking for? No mention of the errant machine by name or ip. Just yards of this sort of thing: 2015-06-17 06:48:34 Information: SchedulerModule [Thread a4c]: Received message: RegisterTimeEvent 2015-06-17 06:48:34 Information: CDynamicGroupsModule [Thread a7c]: Refreshing static groups after replication 2015-06-17 06:48:35 Information: CDynamicGroupsModule [Thread a7c]: Retrieving currently matching dynamic groups with static groups path to root 2015-06-17 06:48:35 Information: SchedulerModule [Thread a4c]: Received message: GetRemainingTimeByUserDataReque
  5. We have ESET File Security 6 running on Windows Server 2008 R2 Standard, and ERA 6 running on a separate dedicated Win 7 PC in the same domain. ESFS won't talk to the ERA. No errors. Just it does not make contact. All other PCs talk to the ERA with no problem. We suspected the Server firewall, but nothing obvious shows up and the agent has a free pass though both machines. I'm not yet up to speed on the ver 6 logs, but nothing jumps out. It just looks like the agent isn't trying. Where is a good point to start investigating this?
  6. Sorry, I don't really have time for this. We have installed another product.
  7. And... ? This is driving me nuts. We now have five machines doing this at least a coupel fo times per week.
  8. On a few workstations I am getting: "Virus signature database update ended with an error. General compiler error" Clearing the cache, rebooting the workstation and updating the sig again always clears the error. However this is happening repeatedly and is becoming a pain. Any ideas? Virus signature database: 11749 (20150607) Rapid Response module: 6136 (20150607) Update module: 1056 (20150113) Antivirus and antispyware scanner module: 1456 (20150512) Advanced heuristics module: 1154 (20150129) Archive support module: 1227 (20150511) Cleaner module: 1108 (20150424) Anti-Stealth
  9. Reports about an out of date OS from agent may be useful in cases when agent is already deployed and an admin wants to make sure that the OS is fully updated before continuing with Endpoint deployment (e.g. to prevent serious issues from occurring when certain hotfixes are missing). I'm trying to be constructive and not unreasonably critical, but I can't see that makes any sense at all. If it's a pre-installation check and it is so load-intensive, why keep running it after EES is installed? And what use is it as a pre-installation check if it can generate false alarms for 18 hours
  10. If I understand you correctly, you have TWO separate systems on each PC checking that the OS is up-to-date? (Why duplicate a system that you have already said is resource-intensive?) One of them will incorrectly report to the dashboard for 18 hours that the OS is out of date if it happens to run just before an OS update? The other will check the OS, but will not report it to the dashboard? I really hope I have misunderstood something here, because that sounds quite ridiculous. I've been an EST fan for decades, but I'm seriously thinking of jumping ship. If the ERA is so borked
  11. I had the same issue. Could never get the task to work. Solved it by installing 6.1.444 ERA component directly from the .msi on the local machine.
  12. A further comment: What has the agent to ERA server connection got to do with resource use? The EES already knows the OS is up to date and is reporting this correctly on the local machine. It is just the ERA that has outdated information. Surely all the agent needs to do is pull the info from the ESS and send to ERA? Can't be more than a byte or two at most, and all on the local LAN. Why does it need to wait 18 hours to do that to 'save resources'?
  13. Thanks for the quick reply. Option one is a bit confusing. I can supress the ERA OS update check by policy, but ESS iteself will take over OS update checks? I presume what you mean is ESS will do update checks but will not report them to ERA? If so, that's not an option. It's basically just turning off the feature - unless I inspect the PCs manually. Option two seems a bit of a cludge. Presumably this means running a perhaps unnecessary OS update job, just to force an OS check? Again, not particularly satisfactory. No way to force the check without the update? Is there at lease an
  14. This is probably just misunderstanding of how v6 works. By default, agent reports system issues you've mentioned, howe ver, youcan disable these reports via agent's policy. If you look at the details of the alerts, you would most likely see agent as the source. Then please explain how it works. Hey, I'm on your side. I used to sell the previous version and made a good living off it. But I can't figure this out or find any documentation to explain it. Here a sample issue. Please tell me how to resolve it. I'm getting a lot of alerts on the dashboard telling me there are problem
×
×
  • Create New...