Jump to content


  • Content Count

  • Joined

  • Last visited

Profile Information

  • Location
  1. This may be a basic question. I am looking to install ESET on a Veeam Backup server. Which product should I install on the server, and what folders/files should I exclude? Thanks, James
  2. I disabled them both, but no luck. I rebooted after each change I made. I created a static group, applied a policy to that group, moved the PC into that group, and then disabled things one by one to try to narrow in on what was causing it. So far, I have not found anything that lets the PC continue. I just tried uninstalling 7.2.2055.0 and then installed 6.6.2089.2. The problem does not seem to occur with 6.6.2089.2.
  3. It does persist after disabling Protocol Filtering. I also tried adding the ZENworks folder to the Exclusions list, but no luck.
  4. We are starting to have PCs that hang during the ZENworks login process. If we remove ESET (7.2.2055.0), the problem goes away. We are using ZENworks 14.1. The PC hangs at the "Processing User Source..." message from Zen. The PC doesn't lockup, but it won't go any further. The only way to get past this is to disconnect the PC from the network, login locally, and then remove ESET. I have tried disabling everything I can find in ESET, but the problem persists. :-( I would like to keep ESET, but I have to find a solution to this issue ASAP. Has anyone else seen this?
  5. I'm not sure how to do a manual activation with the business license. I'll give it a try though. Thanks.
  6. We are a business customer running ESMC v7 with clients running Endpoint Security v7. We have some old machining equipment that must run on XP. (I know, I know). Anyway, I have installed Endpoint Security v6.5 on the XP machines, but I can not Activate them through ESMC. The activation fails. I thought that the v7 licenses would activate any of the previous versions as well. Is it possible to run two different endpoint versions using the same license pool? Thanks, James
  7. "as well as the updates KB4474419 and KB4490628 are required" That's interesting, because I have found that several of the machines giving the error, needed KB4490628. I'm not sure how that one gets missed. Once I installed that, the remote install worked as planned. For now, I am making sure they are fully patched before trying to install ESET.
  8. Yes. I also downloaded the newest version of the Antivirus product and tried to install it manually. The error from the software-install.log is: "Product: ESET Endpoint Antivirus -- ESET Endpoint Antivirus is no longer supported on your outdated version of Microsoft Windows." I am also seeing a 1603 error in the log "Installation success or error status: 1603."
  9. I am upgrading from 5.x to 7.x and I have run into some problems with a lot of PCs. The agent pushes out fine and upgrades to the latest version. Then when I push out the new version of the Antivirus product, the task ends with an error 0x643. The details say that the ESET Antivirus product is no longer support on your outdated version of Microsoft Windows. I get basically the same message if I try to install the software manually. The PCs are running Windows 7 Pro, and they are up to date on updates. Any thoughts? Now that I have removed v5 Antivirus, and v7 won't install, I don't
  • Create New...