Jump to content

jonathan.deane_UK

Members
  • Posts

    19
  • Joined

  • Days Won

    2

Posts posted by jonathan.deane_UK

  1. I created a dynamic group with, contains Agents v7 AND v6 are both installed, then run 2 x Run Commands (1 for each of the reg deletes) when clients joined the group.

    This resolved the issue for me 95% of the time, i did have to manually rerun the task a few times and had to manually remove one of the reg entries as it was being stubborn and not deleting on at least two machines.

  2. The ESET UK office is relocating to a new office building this weekend, as a result the current office is now closed and due to reopen on Monday morning of the 18th December.

    For urgent support please e-mail helpdesk@eset.co.uk, or call 01202 405 405.

    Please be patient while we complete the relocation to the new premises at which point normal service operations will resume.

    Jonathan

     

    Please note that the office move completed over the weekend and full server was resumed on Monday morning as planned.

  3. Hi

     

    If you want to put the computer in to an OU and have ESET auto install then firstly create a GPO to install the ESET Agent Live Installer hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN3595 (you can edit the batch file to search for /qr and replace with /qn to make it completey silent) and assign it to the OU, once the Agent is installed then the ERA can do its thing.

     

    Create a Client install task to install the ESET software and licence etc and assign it to the OU Group and set the 'Trigger' for when Joined/changed depending on the wording for the version of ERA you have installed.

     

    I normally create a Dynamic group based on 'is there is another AV installed', a client task removes this, another dynamic group for 'no other AV and no ESET', a sub dynamic groups for workstation and server OS and then assign the client install tasks for installing EEA/EES or EFSW depending on the server.

  4. If you disable the firewall are you able to access the ERA server as expected?

     

    When I enabled the firewall on my test 2008R2 server with ERA along with firewall logging enabled I was able to see ports 443 and 2222 get blocked, I created a simple port rule to allow 2222 and 443.

     

    I was then able to access the console as expected without any issues appearing.

     

    Checking the firewall log I could see the port 443 was accessing c:\program files (x86)\apache software foundation\tomcat 70\bin\tomcat7.exe

    and port 2222 was accessing c:\program files\eset\remoteadministrator\server\service.exe

     

    Also remember that the link should https://ip.address.of.server/era  (not putting /era will result in a blank page as you are getting)

     

    Jonathan

×
×
  • Create New...