Jump to content

johnnybon

Members
  • Posts

    19
  • Joined

Posts posted by johnnybon

  1. 3 hours ago, TheSkymanDC said:

    Thanks for the reply but that doesn't tell me how important it is to install this upgrade.

    Given the sparse changelog I would say it's a mission critical update. I would just do a standard rollout.

  2. 17 hours ago, Michael_Loemm said:

    Hi,

    same error today on customer side, after a little research I found the solution!

    The installed ESET AV product blocked the agent!
    https://help.eset.com/era_install/65/en-US/component_installation_agent_windows_uninstall.html
    "If there is an ESET endpoint product on the same machine, it will not be possible because of an enabled Self-Defense."

    My solution
    1. Uninstall the AV with appwiz.cpl
    2. Uninstall the Agent with appwiz.cpl
    3. Install the new Agent and AV

    Best regards

    Michael

     

    I thought it'd be something like that, as if it's done through the console (ie agent upgrade followed by rollout from the repo) it works fine. Thanks for the investigation though

  3. Hi,

    I've got one Windows Server 2012r2 that is failing in its upgrade from v6.5 to v.7.x. The problem seems to happen during the Management Agent portion of the install, and fails every time with the Error Code: MSI.8257588. The specialized cleaner doesn't work.

     

    image.png.e1f1162f55eb5bc3012ede1bda116b28.png 

    I've uninstalled everything, rebooted, and it still fails.

    I've then removed all trace of the software using the ESET Safe Mode Uninstaller Tool, but still nothing. 

     

    Has anyone else had this situation? Any help would be much appreciated, thanks.

  4. 44 minutes ago, CMS said:

    I can't install ESMC as it's asking for a database administrator username and password, which I have no record of. The admin username and password don't work. Not sure if the issue is this, or the connection credentials, but have logged a support ticket.

    Hi CMS, 

    Try 'eraadmin' without the '' as this is the default account, but this should have been changed during the initial set up.

  5. 4 minutes ago, MusicWallaby said:

    Could I be lazy and ask which specific setting that is in the client?  Lots of options..!

    Unfortunately I'm not at a computer with access to the Remote Administrator at the moment, but I suggest installing that and then releasing policies to your clients. There is a built in policy for silent install/running I believe.

  6. 2 minutes ago, MusicWallaby said:

    Thanks mate and yes, of course, fully understand that, but that's not really the situation here.

    If I take a laptop home, switch it on, but don't connect it to my home Wi-Fi it feels kind of pointless getting told "Couldn't contact the update server".

    I'm trying to avoid hundreds of tickets from confused staff when it's pretty obvious that if you're not connected to a network you won't get updates on your antivirus :)

    It's just normal coming and going with intermittent network/internet connectivity like people do with laptops these days.

    Haha we did exactly the same.

    To resolve it, we basically set ESET into silent mode on endpoints, and that it doesn't pop up on the users screen so that it only alerts us if anything critical happens. Then within the Remote policies on Remote Admin, we set it to not warn us about things such as intermittent connections, or that Windows Defender was reporting it as not working when it was, that Windows wasn't up to date yet etc.

    Much easier and cleaner for us, and also means you can do scans in the background with minimal bother to the user.

  7. Hi MusicWallaby, if I can add my two cents, it's an error by design. The product will need to be connected to an update source to get its updates, as it's the updates that ultimately define how secure the software is. 

    Within the settings is an option to either connect it to a mirror/proxy combination that can distribute the updates on a closed network.

    The preferred way is to download the latest definitions, put them on a usb device, and then tell a mirror/proxy computer to look for updates that are on a USB, and then distribute them among the closed network.

    I'm sure there is a way within the settings to not alert you to this, but it's critical that your product gets updates.

     

×
×
  • Create New...