Jump to content

ict@flinter.nl

Members
  • Content Count

    5
  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling
  • Location
    Netherlands
  1. Hi, I am having the same issue. I do not want to push this with GPO so i am going to try and work with the dynamic groups in ERA itself. I guess with correct filters it should be possible to start this task on targets in the right AD group, which do not have the agent installed and are online (responding to ping or whatever). Will report back if i am succesful.
  2. What i found out is that certain firewall settings have to be enabled. If the target machine is closed off the remote install will fail, what i have done is enabled the firewall settings File and Printer Sharing (Echo Request - ICMPv4-In) and File and Printer Sharing (SMB-In). In our case I restricted these settings to domain only and to a certain network range, but that depends on your network/domain setup. After these changes, remote installs went fine.
  3. We are having the same issue, action center on the machines reports everything OK, in ESET i see 3 problems.. Only on windows 7 machines btw. Any case it is not acceptable to just switch off the policy settings. So any update on this matter?
  4. We also are having the same issues. No reply from support no help at all. Guess it is time to look elsewhere.
  5. Hi, Just rolled out v6 2 weeks ago with some test machines and agent version 6.2.171. Now a bit further in the deployment there is a new agent (6.2.190), most of the machine were upgradable but some refuse any and all attemps. Neither upgrade component, remote installation tasks works. Even trying to uninstall this damned thing fails with an Access denied error (logged in as local or domain admin). The result is a programdata folder that is utterly undeletable. Cant upgrade or remove the remote agent.. My only solution is at this point to a) stop monitoring these clients b) do a f
×
×
  • Create New...