Jump to content

ajal

Members
  • Content Count

    11
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Switzerland
  1. Hey MichalJ In my case, I used the "restart Service"-method of the Agent-Service for updating policies, think like GPUPDATE. Now, when your "push"-method also pulls the new policies - that would be great. It should be like the "update" Button to update signatures. thank you
  2. Hey Evertjan I have no such issues with FS Version 6.3.12010.0. What Version of EFS 6 do you use? Did you disable the GUI on your RDS-Servers? Here is the ESET article about Terminal Servers: Recommended settings for ESET File Security installed on a terminal or Citrix server (6.x) Another question: Do you use ClassicShell StartMenu on your RDS 2012 R2? What happens, when you push "Windows"-button from your Keyboard, trying to start the startmenu? In the past, I had this issue Windows 2012 RDS (no R2) in combination with ClassicShell Startmenu. There were also some common RDP
  3. Absolutly agree with tomha. I noticed the same today. Should really be implemented asap! In my view, this is something you cannot without it. I would like to see this possibilities with Exclusions, especially regarding let's call them "local client exclusions" : - Ability to add local client exclusions on the Client-UI (means, add exclusions directly on Client, not in ERA) - Ability to define Exclusions (in ERA) to force ERA Exclusions (replace or make local client exclusions useles) - Ability to define Exclusions (in ERA) and merge with local Client Exclusions (should be the De
  4. Absolutly agree with tomha. I noticed the same today. Should really be implemented asap! In my view, this is something you cannot without it. I would like to see this possibilities with Exclusions, especially regarding let's call them "local client exclusions" : - Ability to add local client exclusions on the Client-UI (means, add exclusions directly on Client, not in ERA) - Ability to define Exclusions (in ERA) to force ERA Exclusions (replace or make local client exclusions useles) - Ability to define Exclusions (in ERA) and merge with local Client Exclusions (should be the De
  5. Hey filips Thank you for your reply. I use the Defaults for now, seems no Impact on Exchange Services. Regarding "Shadow-Redundancy"-Queue This Problem started as soon as we installed MailYSecurity 6 on our Exchange Servers. One interesting Point is, only filtered Mails by ESET MailSecurity stuck in the Queue. For us, waiting for AutoDiscardInterval is no solution - we have different Monitoring scripts an Tools checking the Queue. Also, when I take on of the DAG-Members in Maintenance - the Queue is also checked, and must be empty - so big Impact in our production. I opened
  6. Hi again I tested ESET MailSecurity in a Exchange 2013 DAG - 2 x Exchange Servers. All Mails in the Quarantine-Manager are also in the "Shadow-Redundancy" Queue - and the Queue is not getting empty. Is this a known issue in Version 6.3.12010.0? Thank you
  7. Hi I am also waiting for the answer. There is no word about Exchange DAG in the documentation. Any recommendations for Exchange DAG-Setups? Thanks
  8. Hi there I use ESET MailSecurity 6.3.12010.0 on 2 Exchange 2013 Servers - in DAG. I noticed the same as katbert - when we customize the ports, there is no way to get the webinterface. Changing them to Default ports 443 and 80 - worked. So, ESET is not using IIS for web quarantine?
  9. Same here ! I'm a VERY happy costumer of ERA 6 for 1200 seats across 3 licenses ! From what I read , most of the user complaining about ERA 6 simply didn't read the documentation. They just excpect it to work like ERA 5 without even trying to understand that it's a completely new product. For my part I think ERA 6 is WAY better than ERA 5 . But before moving from 5 to 6 I took time to read ALL the available documentation, and the deployment was a breeze. Hi all Now, about one year after the first tests with ERA6 (it was a nightmare) , I am also a happy customer of
  10. We also need this param for MSI installation. There is a property named "P_REPLICATION_INTERVAL" which is maybe what we need. But we do not know what values it accepts. Usecase: When the agent cannot successfully connect the ERA Server the first time(server down, firewall issues etc.) , it should retry reconnection asap. It is important for BulkDeployments to know some MSi Properties that can be used during installation. Some of them are used in "agent live installer" batch that is generated, and we use these to set certs, password etc. Please provide the reconnection values that ca
×
×
  • Create New...