Jump to content

ajal

Members
  • Posts

    11
  • Joined

  • Last visited

About ajal

  • Rank
    Newbie
    Newbie

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 issues with black Screen for connecting users from internet, check this link! regards
  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 Default - i think) Any News about Exclusions in 6.4.X ? ...the same thing i am missing with "Scheduled Tasks"
  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 Default - i think) Any News about Exclusions in 6.4.X ?
  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 a ticket for this issue - today. Is there more Information about this issue? What can we expect from ESET? Other Workarounds ? Thank you
  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 ERA 6. I use ESET ERA Version 5 now for more than 4 years... I saw the great potential of ESET with the new architecture, the new policy-based and dynamic Management of their products, but ERA6 was not more than BETA and the documentation was deficient (it's better now but partially still insufficient). In my opinion, ESET has released ERA6 too early. Now, with the ERA Version 6.4+, we can start deploying these great security products - growing day by day. With the new more-dynamic way Managing everything, and the possibilities we got with ERA6 - i don't miss my good old ERA5-Console at all. I am also one of those admins, who still work with vSphere Client and not the WebClient, but this is another Story The great thing about Web-Based Software is, you can use it on any Client - but it must be fast! And hey, my ERA6 Webinterface running on a ERA Appliance (CentOS Linux) is not slow at all - and surprisingly, I am a Windows-Guy! Currently. you still need to create a lot of "Dynamic Group Templates", some "Dynamic Groups", a good static Groups structure, and all your Policy-Sets for your different agents, products, Servers and Clients, but the ESET-devs have done a great Job - also between V6.3 and V6.4 and now offers a better overview of policies. And I am sure, there will be more Built-In stuff in future, so you don't need much time to get ready to GO. Most of the time I used to prepare my ERA6-Setup was "Policies". You must create all your Policy-Sets (Agents, Security Products, FileSecurity, MailSecurity etc...) for your needs, starting with Common-Settings, and than get more specific, depending the Product and role of your EndPoint. You need to lear and understand the dependencies of the Settings and Subsettings of the products (there are still dependencies of Subsettings-Settings not considered and implemented yet in the wizards). My best practice: Do this in a LAB - use an appliance (you don't need to be a tux), take snapshots and play! All admins out there, who understand policy-based model will be very happy with ERA6 - and the others (the console-push-rightnow), will need to learn the new dynamic way of managing. Even though I often use the "Send Wake-Up Call" button during Policy-Creation to test the resultant-set-of-policies For us lazy Admins , the goal is: Create a (almost) full-automatic Deployment, Configuration of all ESET products and components in our Multi-Tentant or single Environment - in a "Set It and Forget It"-Way!!! After all this, set the focus on Monitoring, Reporting and Alerting!!! Later, we can use ERA for more than just manage ESET products, we have a good base-product with an thin Agent we can use for more exciting things like Deploy SW and run Scripts and provisioning in general. The new MSP-License-Model (and ELA) and the integration into ERA is also a great Thing - I love it, not to document and manage all the license Infos in Excel. With ERA6, all this cool stuff is possible right now! I also agree with cssinfo: Don't expect ERA6 work like ERA5 - start now learning the new power of ERA6 !!!
  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 can be used during MSI install, to reach this. It is difficult enough to push Agent, Products with ERA 6, and YES I have read all docs and articles that are available until now. So please guys, make us life a little easier!!!!
×
×
  • Create New...