Jump to content

davidpitt

Members
  • Content Count

    44
  • Joined

  • Last visited

Profile Information

  • Gender
    Female
  • Location
    U.K.

Recent Profile Visitors

532 profile views
  1. So after speaking with support they told me to try HIPS in training mode. When that didn't work, they told me to just disable HIPS, which I've tested and does work. I've tried disabling every option under HIPS but the only thing that works is the disable the entire HIPS module. I even tried creating a HIPS rule that allows 'agent_x64.msi' full access to everything. Also for my test machine, I created brand new blank Eset policies, did a clean install of windows 10, no config changes, installed v6.6 of the agent and then v7 of the Endpoint and still had the problem upgrading agent to v7 with HIPS enabled. Very annoyed now, It baffles me how your own product can block it's own update, ridiculous! i'm really going off Eset and it doesn't help I'm getting pressured from my new bosses (With have recently merged) to ditch Eset and go with their BitDefender. To be honest the thought of having to update 1418 agents now to v7 and the problems I will face is making BitDefender very tempting possibility. Frustrating because I think the core AV of Eset is better and it's faster than BitDefender. Ever since the product was re-written and introduced the agent mechanism for v6, we've had nothing but problems with updating Agents. Any calls to Eset support has always ended up the same way, with the support agent not being able to fix it and having to run the Eset uninstall tool in safe mode. Apologies for the rant, just hoped by v7 these Agent issues would've been fixed :(
  2. Hi, Would I be better logging this direct with support rather here on the forums?
  3. Hi, Disabling HIPS has worked and Agent got updated. Checking the policy, there are no special rules in place, other than 2 custom 'Allow' rules for LogMeIn and Hamachi. All HIPS options are enabled and Filtering Mode is set to Automatic. I'd prefer not to have to disable HIPS, wait for a restart, push out new agent, enable HIPS again on all devices if there is a fix for this issue?!? Thanks
  4. Here's the log... Thanks ra-upgrade-agent.log Have you had chance to look at the log yet? Thanks
  5. Here's the log... Thanks ra-upgrade-agent.log
  6. Hi, I've recently upgraded our ERA to v7 (From 6.6) and now trying to get the agents on the clients updated, however I'm running into issues! I am trying to update Eset Agent from v6.4.283.0 to v7.0.577.0 using the "Security Management Center Components Upgrade" However on several devices it is failing with the errors below.... Windows event logs show --------------------------------------------------------------- The description for Event ID 0 from source era-updater cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: era-updater Execution finished with 0x643: (0x643), Fatal error during installation --------------------------------------------------------------- Eset Trace log shows --------------------------------------------------------------- 2019-01-21 16:01:16 Error: CSystemConnectorModule [Thread 1c7c]: ReadUpgradeStatus: Upgrade of Agent from version '6.4.283.0' to '7.0.577.0' failed. Unexpected updater service Win32ExitCode 0x435 --------------------------------------------------------------- Any ideas? Thanks
  7. Sorry but I don't have a solution but I dread every time I have to update an agent on a PC as 90% of the time it fails with this exact issue. No matter the version of the agent v6 through to v6.6, if on domain, work group, under local admin account, etc. All have problems. Even when I call their support they don't know how to fix it, other than to use the uninstall tool in safe mode. We gave up trying in the end as with 1500 clients it caused too much work and now users only get the latest agent when their PC gets replaced. I have no idea why these companies make it so difficult to use their products!
  8. Description: I would really like the ability install/Update Endpoints without the clients NIC disconnecting... if that is at all possible?! Detail: This way I could roll out updates/installs to to our 75+ individually managed sites much more easily, hopefully silently in the background without the user even knowing it was happening. Having to call the customers to arrange installs/upgrades out of hours is difficult or having them log off their PCs so that no programs are affected during the network disconnect is a real pain. Multiply that over 75+ individual Eset Server setups with a combined total of several thousand PCs and it becomes impossible!
×
×
  • Create New...