Jump to content

Matt G

Members
  • Posts

    2
  • Joined

  • Last visited

About Matt G

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    New Zealand

Recent Profile Visitors

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

  1. Edit to above: it looks like I had ERA6 Client installed during this entire process. Trying an upgrade from v5 to v6.6 was successful. It seems the ERA6 Client caused the installer to hang during finalizing.
  2. Hi Peter, v6.6 is something we're looking forward to due to our recent issues upgrading from v5.0.2225 to v6.5 on Windows 10 (I believe there was a problem with Windows Defender that should be addressed in this release?). To provide context we installed our v5 clients with a config file that points it to our internal update server. I tested the v5.0.2225 to v6.6.2031 upgrade and found that the v6.6.2031 installer hangs at 0% of finalizing installation. However closing the installer manually at this point seems to leave me with a working client. This is an improvement on my experience with v6.5, which would hang at "starting services" and leave my computer with no entry in Installed Programs, and cause the PC's performance grind to a halt. Other items of note are: I installed ERA Agent and our ERA6 host picks up the client as expected. I was able to run a task to activate the client with our license. I notice now that ESET Endpoint now generates a critical warning if Live Grid is disabled. The client's update page shows a "Modules update failed - File not found on server", I assume this is due to the computer being managed by our ERA6 host? Let me know if there's any information I can provide to work through the upgrade hang issue. I've previously been told to try upgrading to the latest v5 before moving to v6, but your website suggests upgrading from v5.0.2225 is a perfectly normal workflow. Regards, Matt G
×
×
  • Create New...