Jump to content

VlP

Members
  • Posts

    60
  • Joined

  • Last visited

Posts posted by VlP

  1. Hi.

     

    I migrated to new ESET VM appliance v10 (Centos 7.9) via pull database and installed ESET Bridge, but it didnt work. I see error in centos when starting ESET Bridge:

    Nov 25 20:07:22 eset01 Bridge: /opt/eset/bridge/bin/Bridge: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /opt/eset/bridge/bin/Bridge)
    Nov 25 20:07:22 eset01 Bridge: /opt/eset/bridge/bin/Bridge: /lib64/libc.so.6: version `GLIBC_2.27' not found (required by /opt/eset/bridge/bin/Bridge)
    Nov 25 20:08:22 eset01 Bridge: /opt/eset/bridge/bin/Bridge: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /opt/eset/bridge/bin/Bridge)
    Nov 25 20:08:22 eset01 Bridge: /opt/eset/bridge/bin/Bridge: /lib64/libc.so.6: version `GLIBC_2.27' not found (required by /opt/eset/bridge/bin/Bridge)
    Nov 25 20:09:25 eset01 Bridge: /opt/eset/bridge/bin/Bridge: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /opt/eset/bridge/bin/Bridge)
    Nov 25 20:09:25 eset01 Bridge: /opt/eset/bridge/bin/Bridge: /lib64/libc.so.6: version `GLIBC_2.27' not found (required by /opt/eset/bridge/bin/Bridge)
    Nov 25 20:10:28 eset01 Bridge: /opt/eset/bridge/bin/Bridge: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /opt/eset/bridge/bin/Bridge)
    Nov 25 20:10:28 eset01 Bridge: /opt/eset/bridge/bin/Bridge: /lib64/libc.so.6: version `GLIBC_2.27' not found (required by /opt/eset/bridge/bin/Bridge)
    Nov 25 20:11:31 eset01 Bridge: /opt/eset/bridge/bin/Bridge: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /opt/eset/bridge/bin/Bridge)
    Nov 25 20:11:31 eset01 Bridge: /opt/eset/bridge/bin/Bridge: /lib64/libc.so.6: version `GLIBC_2.27' not found (required by /opt/eset/bridge/bin/Bridge)
    Nov 25 20:12:34 eset01 Bridge: /opt/eset/bridge/bin/Bridge: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /opt/eset/bridge/bin/Bridge)
    Nov 25 20:12:34 eset01 Bridge: /opt/eset/bridge/bin/Bridge: /lib64/libc.so.6: version `GLIBC_2.27' not found (required by /opt/eset/bridge/bin/Bridge)

    Why newly deployed appliance didnt support ESET Bridge? 

  2. 21 minutes ago, GregA said:

    Same here, luckily only about 30 computers. But the files are fairly important, as they are used to add the Windows 7 extended ESU license each year.
    C:\windows\system32\slmgr.vbs
    C:\windows\sysWOW64\slmgr.vbs

    Task failed error:  CNodcommChannel: Send request failed with 14, Command failed - Make sure that Agent runs with Administrator privileges.

    Why are the files on Windows 10 machines?

  3. 1 hour ago, gustlik102 said:

    Yes, but as far as I can see, Windows try to restore this file from WinSxS after delete from SysWOW64. When ESET try to replace this file after restore from Windows repository, you got access denied information, because TrustedInstaller is above SYSTEM user (SYSTEM have read only permission to this file). It is no problem when ESET didn't clean this file also in WinSxS. If ESET clean also this file in this folder, Windows will restore empty VBS file and ESET cannot replace it to correct file.

    When I restore items from quarantine, restore item task has failed on every PC..

  4. Yes, we have only access to internet via proxy which runs on ESMC server (only ESMC iself has direct access to internet). I look into .bat file and http proxy settings are set there:

    Quote

    echo.P_PROXY_HTTP_HOSTNAME=192.168.222.16 >> "%installConfigFile%"
    echo.P_PROXY_HTTP_PORT=3128 >> "%installConfigFile%"

    192.168.222.16 is ESMC server.

    Before upgrade this scenario works without problems

  5. Hi.

    After upgrade VA to ESMC 7.1 by update management task, I can't deploy agent to Windows Server 2019:

    In ESMC agent install task shows that agent is installed fine:

    image.png.aa4abae98f283fece34f9c636b2394c9.png

     

    But on server nothing is installed. So a searched for problem and see this in /var/log/messages on ESMC VA:

    image.thumb.png.b9582111a9c30b7f293da5bd3b846575.png

    I tried deploy agent on WS2012R, and the same error ...

    VP

     

     

×
×
  • Create New...