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 system event logs' after each reboot when there is an agent install policy - Enable the policy '“Always wait for the network at computer startup and logon”' - Set the policy "“Startup policy processing wait time” to something like 90 seconds. Less than that is usually not enough Reference: https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClPZCA0 Some additional considerations: - if an agent of version 6.2 or 6.4 is already installed, you cannot use the GPO to upgrade in-place. You must first uninstall existing versions (e.g. through SMC). Of course, you only want to uninstall on AD-aware devices. I wish this was easy to filter by. - I have no idea what are the compatibility issues of the Agent with some older versions of Windows - there is no information about the network share configuration. I managed to use a public (not the Public folders; access allowed from Domain Computers) read-only share on a Windows File Server - all of these GPOs must be configured to apply to Domain Coimputers in order to be useful
  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.0 that still need to be upgraded to 7.3 (a few XP/vistas tha cannot). Unsure whether all of these will start losing connectivity like the others, because these have not had any issues and they do not have the agent installed. Thanks, mmadeira
  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 with: - public (without credentials) and domain share. Share as read and execute permissions. - pointing to the file on the local filesystem to the SMC server - using domain credentials - using local admin Success rate is 1/100 so far. I have added the GPO per documentation and I have also managed to install the Agent on 1/60 computers. Ir required a gpupdate and a couple of reboots. For those computers that it does not work as expected, the gpresult mentions that changes need to happen prior to login, but they never finish because the Agent is not listed in Control Panel > Programs. Also have to deal with computers routed over L3, because of remote workers that I will not have the chance to manually upgrade. At this point I am installing agent by hand using the All-in-one package with latest Antivirus + Agent, because of my fear of computers losing connectivity as per the referenced thread. Thanks, mmadeira EDIT: Using the forums, because I did not get an engineer to look at my concerns. So far I have only been told to upgrade and I have been migrated from ELA to EBA after the connectivity issues came up in the other post.
  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.0 that still need to be upgraded to 7.3 (a few XP/vistas tha cannot). Unsure whether all of these will start losing connectivity like the others, because these have not had any issues and they do not have the agent installed. Thanks, mmadeira
  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 not try to turn of the SCM/ERA server. I will try that if the issue persists in a few hours. I got a chance to run wireshark on the device since I did not get a product engineer to engage with this issue. No traffic seen on the device after the TCP Handshake, yet I could see that it was receiving traffic sent from the gateway or local services depending on the routing. All ICMP types and UDP are fine. TCP DNS does not work while UDP DNS works 😆 Other symptoms in the affected devices: - often have network access after reboot for around 2-10 minutes. Some users mention the problem is resolved after rebooting, but comes back after a few hours. - ESET application becomes unusable after a few clicks - cannot login to domain accounts (stuck in welcome screen after entering credentials), unless this is done in that 2-10 minute window - on some computers could not even uninstall ESET or other programs. All installers get stuck eternally. Even on very modern workstations - on some computers cannot open powershell or cmd - on some computers start menu is empty (no tiles, programs, settings app) - on most computers, restart are eternal. Have to tell users to press the power button. - on all computers. Cannot use any web browser. If there is any proxy in use, it is the ERA/SCM one - on most computers cannot even do basic things like contact the AD for domain-aware devices or access any fileservers (SMB and other protocols). This is all kinds of FUN with remote workers that do not have local admin privileges and the fact that the only cached credentials are of one of the domain admins that was used to link the computer to the domain. Hey at least I was able to generate the All-in-one package of Antivirus + ESET, so there is no need to type in the license code every time 😆 Of course this sort of spontaneous combustion hinders all possibility of log analysis.
  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 after gpupdate and multiple reboots. gpupdate always mentions that some tasks need to be done prior to logon. - the GPO is working to some extent, because computers without any ESET product are getting the latest Agent installed. 32-bit and 64-bit Right now I have wasted a bunch of time that I could have used manually updating agents to 7.2 by waking up at 7AM before users get on their computers. These are the notes I wrote while reading documentation: - cannot upgrade ERA agent to SCM Management Agent on client computers pre-6.5 - the task runs successfully but https://help.eset.com/esmc_admin/71/en-US/client_tasks_upgrade_components.html - does it work or not ... https://support.eset.com/en/kb7465-upgrade-eset-remote-administrator-agents-65-or-eset-management-agents-70-to-the-latest-eset-management-agents-71-using-the-components-upgrade-task - ah, does not work because it is not 6.5: https://support.eset.com/en/kb6819-upgrade-eset-remote-administrator-63-and-later-to-eset-security-management-center-version-7-using-the-web-console - I imagine this is why the GPO deployment of SCM Agent did not install on computers with existing existing ERA installations (6.4 or older) I am attaching versions of SCM. Thanks, mmadeira EDIT: further context on agent environment: - around 60 outdated agents (some crossover between domain-aware and not) - total of 140 agents that I want to deploy for now (a bit more than half are domain) - more agents to come in the future, so it would be interesting to use the remote deployment tool on the latest versions of Windows 10 both domain-aware and not
  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...