Jump to content

mmadeira

Members
  • Content Count

    9
  • Joined

  • Last visited

Profile Information

  • Location
    Portugal

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Just replying to not keep this un-solved. ESET staff was also clueless why none of the alternatives were not working. I can only assume that these tools are not reliable enough. Solution was manual installs with about ~8 Safe Mode uninstalls, because the upgrade did not work initially. Edit: I managed to get GPO working without staff assistance. I used this to install the latest SMC Agent version. It turns out there are some missing pieces in the KB that are often required on business-grade networks. It boils down to: - 'Error 1274 appears in the target machine’s Windows s
  2. I handled this issue with ESET support staff. Deployment tool does not work because administrative share is not enable as it shouldn't for security reasons. Cannot use AD on these computers, because of IT policy. Only way is the manual way, which is unfortunate, because if it were better documented I could have updated the agents on the version that SCM/ERA was at last week. Edit: I managed to find a solution on my own after a lot of pain. See
  3. i have created the following thread to cover those ~100 agents that I cannot install automatically using ESET's provided software and alternatives. This issue does not fit the original question in this post.
  4. Hello Michalj, The component upgrade task did not work, because I selected the the only agent version available on the repository, which is the latest (7.2) or close to it, which I later found out that is not a viable upgrade as per the links in my initial post. Additionally, the 'Software Install' task does not list any relevant Management Agent, so I assume that the component upgrade is the only viable upgrade method? I am not ready to try the 'alternative' upgrade method via the command task. By EP, I assume you mean Endpoint. About 100 of 6.3.2016.1 , 6.2.2033.2 or 6.3.2016.
  5. Greetings, I need to install a bunch of the agents on computers that have had ESET Antivirus 6 for a compuple of years but have never had either SMC Agent or ERA Agent. This is in followup to this post. I cannot use AD reliably, because only about half of the devices are domain-aware. I have tried using the remote deployment tool with all computers on several networks (still about 100 devices to go) without success. I always get following roughly translated error: Deployment failed "Network path not found". (WNetAddConnection2 failed with 0x35) Additionally, I have tried this
  6. Hello Michalj, The component upgrade task did not work, because I selected the the only agent version available on the repository, which is the latest (7.2) or close to it, which I later found out that is not a viable upgrade as per the links in my initial post. Additionally, the 'Software Install' task does not list any relevant Management Agent, so I assume that the component upgrade is the only viable upgrade method? I am not ready to try the 'alternative' upgrade method via the command task. By EP, I assume you mean Endpoint. About 100 of 6.3.2016.1 , 6.2.2033.2 or 6.3.2016.
  7. Thanks for the though material. I will pick this up if this is still interesting at some point. To update my post. Today random computers starting losing connection to any and all services that use TCP. This is what started the ESET agent updating frenzy, because it happened to about 5 computers last week. Today, I found out the hard way that ~40 desktops and laptops using ESET 6.2/6.3 were blocking all TCP traffic to any and all services, but they were at least reachable by RDP or VNC. In all cases, what solves it is a reinstall of newer ESET 7.X. It has just occurred to me that I did no
  8. Hello, Is there any recommend way to deal with 6.X agents prior to 6.5. In particular, I would like to upgrade the agents to the latest SCM agent. Problematic agents are versions 6.2 and 6.4. The target devices are a mix of Windows XP,Vista,7,10. Some are within the Windows domain and others are not. The SCM server is not on the domain. Options I have tried: - deployment tool. Does not work: - network path not found (tried both with a local path and a public network share on the same subnet) - GPO for Domain-aware computers - never upgrades to agent 7.2 even a
  9. Hello, Is there any way to disable the warning "Backup user not set up" in the status overview page? Seems pretty silly when I have multiple administrative users as a backup. I have event tried creating users named 'mutealertX' without success. Maybe the SQL query is not correct 😆 See attachments for version and error details. Thanks, mmadeira
×
×
  • Create New...