Jump to content

Baramine

Members
  • Content Count

    6
  • Joined

  • Last visited

Profile Information

  • Location
    France
  1. Maybe authentication is juste the licence key include in EMS ? Ok thanks you, I look forward to hearing from you on this important issue.
  2. Please can you describe this step : enter a username/password into EMS to authenticate against that computer.?
  3. Is it a policy into ERAS ?
  4. Mirror internal created by Eset File Security with Authentication enabled : no em032_32_l2.nup present, only nod... file
  5. Ok i will test your instructions but for information, i have installed an application to see the traffic on my Device: It search em032_32_l2.nup , but this file is not present on my mirror .... GET /mobile-sta/mod_032_mobile_perseus_1053/em032_32_l2.nup HTTP/1.1 Accept: */* User-Agent: EMS Update (Android; U; 32bit; TDB 9042; BPC 2.2.13.0; OSR 8.0.0; PLOC FR_FR; x32c; APP eesa; HWF: jdnN2xbxFXhsSPlEhB8Fv5Eaym4=; BEO 1; PCODE 710.27.0) Eset-Spread-Control: yes; domain=production X-NOD32-Mode: passive X-ESET-UpdateID: EAV-43028278 Authorization: Digest username="EAV-XXXX", realm
  6. Hello everyone, I have created a mirror local on my ESET ERA Server for update worsktation client with this tool : https://help.eset.com/era_install/65/en-US/index.html?mirror_tool_windows.htm Everything works well except my Android devices which display an error : 4612... i have checked Http request on the server, seems to be OK: "GET /update.ver HTTP/1.1" 200 142531 "-" "EMS Update (Android; U; 32bit; TDB 9042; BPC 2.2.13.0; OSR 8.0.0; PLOC FR_FR; x32c; APP eesa; HWF: jdnN2xbxFXhsSPlEhB8Fv5Eaym4=; BEO 1; PCODE 710.27.0)" Any ideas ? Thanks
×
×
  • Create New...