Jump to content

TheSkymanDC

Members
  • Posts

    86
  • Joined

  • Last visited

Posts posted by TheSkymanDC

  1. ESMC is showing a new version is out.  Used an existing "install latest" task as I always do on a test machine.  Task runs, says complete.  Test machine says I need to reboot.  But the version installed is still 7.3.2044.0.

    Is there a new procedure?

  2. 2 hours ago, Command IT said:

    Of the 30 test machines I've upgraded from v7.3.2032 to v7.3.2036 only 2 have had a yellow restart recommended alert. All the rest have had a red restart required alert

    That's about what I'm seeing here.   I'd be interested to know what the difference is.

  3. Marcos - in the past we've been told that a minor upgrade as 2032 to 2036 would not require new install.  Is this still true.

    And I'm with Roger on this - having to reboot after a minor upgrade is really unexpected and somewhat painful.

     

  4. We have a group of computers that are on our network and may or may not have access to the Internet based on who is logged in.

    If the logged in user has access to the Internet then no problem.

    If the user does NOT have access to the Internet ESET update on the computer shows:

    Modules update failed

    Could not connect to server

    Product update failed

    Could not connect to server

    This has happened since the install of 7.2.2055.0

    I am used to these computers showing ESET LiveGrid is not accessible - that is not a problem.

    Any ideas?

  5. The upgrade on many of our computers is failing with the following error:

    GetFile: Error reading HTTP response data (0x4e33)

    Trace.log shows

    2018-11-27 17:07:20 Error: CSystemConnectorModule [Thread f7c]: Software installation failed: GetFile: Error reading HTTP response data (0x4e33)

    From the problem computer we are able to access

    hxxp://repository.eset.com/v1/com/eset/apps/business/eea/windows/v7/7.0.2091.0/eea_nt64.msi.eula/eulaenu.html

    I think that tells me Internet connections are OK.

    Trace.log is attached.

    Any ideas?

    Thanks!

     

     

     

     

    trace.log

×
×
  • Create New...