Jump to content


  • Content Count

  • Joined

  • Last visited

Profile Information

  • Location
  1. PS: I think its worth mentioning that the above link is able to be manually downloaded on the client machine.
  2. Good afternoon! I followed your instruction regarding the changes on installer ESMCAgentInstaller.bat and run it on the Workgroup machines. Now I can see them on the console (little win here!) however I cannot manage them remotely. The Console is constantly updated (it can see Endpoint and module versions, if the Windows firewall is up or down etc) but all tasks sent fail. For example when attempting to update through the Console I am getting: GetFile: Failed to process HTTP request (error code: 20014, url: 'hxxp://repository.eset.com/v1/com/eset/apps/business/eea/windows/v7/7.3.
  3. Thank you for your timely response!!! Isn't the agent already installed when using the All-in-One Installer? I have already tried the Rogue Detection however it only sees the local subnet and not the VPN connected one. I checked on all over-VPN clients the status.log and they all have identical reports (attached).
  4. Hello friends! I have a question of correct practice regarding ESET SMC on a client implementation. Said client employs Active Directory workstations on their central premises and has a second location connected to the first one over leased line-VPN, where the workstations belong to a workgroup instead. How should I go about having those PCs discovered by the ESET console (that runs on the central location premises server). I have already installed the endpoints on those workgroup pcs without problem using the All-in-One Installer, and tried adding them to the ESMC using
  • Create New...