Jump to content


  • Content Count

  • Joined

  • Last visited

Profile Information

  • Location
  1. Hi MichalJ. Thanks for you answer. The group indeed is a static group and that's the reason I asked. We extensively use dynamic groups as this is a really great feature of ESET, and "Approved" is the only static group we use. Our intention is to not activate the product automatically but only after someone checked what device it is and then moved it to the "Approved" group. The trigger description generated make us think that it will work as intended. However whenever we create a trigger on that group the TARGET TYPE is shown as "Dynamic Group". We checked multiple times with same result.
  2. Here the behaviour is absolutely reproducible. Does anybody know if this is only a cosmetic problem?
  3. Hi. We created a trigger on a static group, which should be fired whenever a computer joins this group (for the first time). However what is strange is, that when displaying the trigger properties the target type is displayed as "Dynamic Group". Any idea what could be wrong?
  4. Here is a workaround for the problem: Add a path rule for "C:\Program Files". Although this sounds stupid as there is already a default rule in place which covers this directory, there is a difference. The default rule specifies a registry key where the path is stored to be whitelisted, whereas the rule you have to add directly specifies the path. There seems to be an incompatibility with MS SRP if a software loads a DLL in a certain way which leads to a path rule not correctly evaluated if it is specified via registry key. Took a long time to find it out, so others having the same problem can adopt this workaround. Although 99,9% of software is not affected by this problem, ESET add-in however is, so be prepared. Cheers.
  5. Hi. We have the problem that the ESET Outlook Add-in does not work together with Microsoft Software Restriction Policies. The ugly thing is that normally when something is blocked by SRP you will find a detailed message in the event logs. However with Office add-ins this is not the case, so it is nearly impossible to track this down. When all places where users are not allowed to write are white-listed the ESET Outlook add-in still fails to load. I have to white-list C:\ to get the add-in to work which is similar to disabling SRP at all. Any suggestions why this fails and how to track down. it is the only Office add-in not working with SRP here so far. Thanks for your help.
  6. @Roger Nock Updating still works here also.
  7. @Marcos What you ask for is the workaround I found out and which I posted here: As you can see, for others it seems to work so far. Link
  8. @Roger Nock That's great. Please post back you findings, as ESET support is now also aware of this forum thread.
  9. Can you please try the following: Modify the scheduler settings in the following way. Within policy management you will find it at: Settings/TOOLS/SCHEDULER/Scheduler/Edit/Regular automatic update/Edit. On the 4th dialog named "Skipped task" set it from "At the next scheduled time" to "As soon as possible". Here this seems to fix the problem. However we have to further observe this as reaplplying scheduler settings with any settings fixed the problem in the past but only for a short time. Here it works since yesterday evening. Cheers.
  10. Would be nice if someone else affected by the problem could try the new release. For us it does not fix the problem.
  11. Just installed the new version and the problem still persists. I'm really getting disappointed about that software. Don't get me wrong but an endpoint protection software which omit to update its signatures is a security problem.
  12. I have a support case open with ESET. They told me that a hotfix will be release this week which will addresses the problem. Regards
  13. Just opened a ticket with ESET support. From what they said the hotfix should be released tomorrow.
  14. We are running 7.3.2032. Yes the hotfix would be worth a try. Currently we are still in the evaluation phase for replacing an existing AV solution for all our customers. Without this problem being solved it would be impossible to deploy it to our customers. Cheers.
  • Create New...