bbahes

You can use a server product (EFSW v6) right on the server to create a mirror. As for controlling mirror, since v3 there hasn't been an option to control it except enabling or disabling the mirror function. This is still workaround. With ERAv6, the instructions in SOLN82 are for an agent push install. Once agent has been installed, it will download an Endpoint installer from ESET's website. Endpoint install is not done as a push install from ERA so the requirements from the mentioned KB do not apply. If it is failing for whatever reason, it would most likely fail even if installed locally using msi. In such case, the install logs will need to be analyzed to find out the cause of the install failure. This could be down to my lack of information on how and from where agent downloads installer for endpoint, since we have strict policy on how our workstations communicate to Internet. The default Administrator account has the logout timeout pre-set. You can create another administrator account that you will use and that will have the timeout set to whatever value you like. Then it's not missing feature...it's a bug. By now we have found alternative Antivirus solution, and we await to read release notes on your future releases. At least ESET has great support!

You can use a server product (EFSW v6) right on the server to create a mirror. As for controlling mirror, since v3 there hasn't been an option to control it except enabling or disabling the mirror function. With ERAv6, the instructions in SOLN82 are for an agent push install. Once agent has been installed, it will download an Endpoint installer from ESET's website. Endpoint install is not done as a push install from ERA so the requirements from the mentioned KB do not apply.If it is failing for whatever reason, it would most likely fail even if installed locally using msi. In such case, the install logs will need to be analyzed to find out the cause of the install failure. The default Administrator account has the logout timeout pre-set. You can create another administrator account that you will use and that will have the timeout set to whatever value you like. May I ask that you make live public webcast where you install ERA v6 on Windows server and deploy Endpoint Antivirus with Agent to client in workgroup and point it to Proxy for update?

It is still possible to create a mirror using Endpoint v6 and control it via ERA. However, it will download more data than the proxy server would as every single update file would have to be downloaded even if 90% of files were not needed by clients. Also the http server integrated in ESET's products has never been capable of serving a larger number of clients at a time so for larger networks using a 3rd party http server was recommended in such cases. Apache HTTP proxy doesn't require any manual configuration so it's not clear why would you have to edit certain files manually. This is workaround. Why would I want to use workstation to serve Antivirus database to entire network? And still without control over what gets on that v6 Endpoint and what and when gets distributed to clients. There are many ways how to install the agent on clients. It should be possible to send Live Installer via email and ask users to run it or simply run it from a network share. The agent will connect to ERAS, receive groups, policies and tasks so with the appropriate install and activation tasks for dynamic groups (ie. groups with no ESET product installed or with non-activated clients) the install and activation tasks can be accomplished automatically with the installation of Endpoint on those machines. I was able to make .bat file and install agent on test machine. However when I try to use task to deploy Endpoint Antivirus i get ambiguous message that task failed. After reading KB Solution ID: SOLN3605 I found out that even though client has agent installed it still has to be configured in specific way KB Solution ID: SOLN82. But, maybe I was not that clear, what I meant was that I expect single bundle .exe or .msi file with agent and endpoint product of my choice (in my case Endpoint Antivirus) to be installed in single click with preconfigured connection to ERA. It's not clear what you mean as it's only the agent that you deploy on clients. Installation and activation of Endpoint can be accomplished automatically using task for dynamic groups. What I meant was that by pushing agent installation on client (either through ERA or .msi/.exe files or .bat in your case), agent has to do all it needs (KB Solution ID: SOLN82) automatically. If I have to make additional configuration changes to client beside agent installation than it's waste of my and clients time. If you create a new user, you can specify the timeout for automatic logout. But there is no way to change timeout on current user. I can't find it. Or it does not exist? If it does not exist would you agree it's feature that's expected in web application?

This is most likely due to performance counters that the agent uses. This issue should be addressed in the next service build. Can you be more specific on next release date? At the moment we are on hold for v6 upgrade, mostly because of features missing, bugs and lack of documentation. There's no exact date set for the release, however, my personal estimation is that it won't take longer than a month. As for missing features, could you be please more specific? Of course, the current ERA v6 is not a finished project and we will continue to improve it and bring new features and enhancements over time. Regarding the documentation, it's been improved since the official release and we are continually improving it based on the queries from users. Also I'd like to bring the following topic into your attention which is regularly updated with new KB content concerning ERA6: https://forum.eset.com/topic/4469-latest-knowledgebase-articles-videos-for-era-6/. As critical missing feature I would say you are missing central update server(something like Update Mirror used to be). No Proxy will make me stay on ESET. But if you plan to stick with Proxy, my guess is that it would be better accepted if you provide control from admin console, rather than make me edit files manually. Second missing feature is option to deploy single activated package to clients (agent+endpoint product) via file share. My situation is not pleasant since I have near 100 windows workstations without domain and no simple solution to deploy. Third missing feature is to make push installation process require just agent to deploy. The agent has to be there to setup workstation in every possible way to communicate to ERA. Fourth. I don't know why people feel that web interface is way to go for security products, but you should reconsider making mmc console for people who look at antivirus console more that few minutes, and I have not found option to reduce logout timeout on your web console. Web interface is not responsive as classic console. Did it refresh page? Is http service up? If server receives many http requests I don't wan't to be locked out. For these reasons I can't reconsider ESET as my Antivirus solution next year. Sadly other solutins cost more and take performance from my workstations as I'm in process of testing them. Kind regards.

I am in process of replacing ESET with some other antivirus solution, because of problems you have and much more and I have only 100 clients. I am waiting every day for some good news, but it seems that won't happen. Still have less than year until it expires. Good luck with v6.

This is most likely due to performance counters that the agent uses. This issue should be addressed in the next service build. Can you be more specific on next release date? At the moment we are on hold for v6 upgrade, mostly because of features missing, bugs and lack of documentation.

Shawkins- I'd just like to point out that at mirror server can be configured on a client with Endpoint Security or Endpoint Antivirus 6 installed. The process is very similar to ERA 5 and the process is documented here. We also have documentation available for Apache HTTP Proxy, which as Marcos explained, has been introduced as a more complete solution than the previous Mirror server arrangement. I have tested ESET Remote Administrator 6 Virtual Appliance on Hyper-V with single Windows 8.1 client. After two day test I have concluded: 1. I DEMAND solution that gives me APSOLUTE control over endpoint Antivirus from my server. If I want clients to update only from my server than you have to give me that option. If I want to change port over which clients get updates than you have to give me that option. I will not accept this as solution hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN3641 2. Making security software is complex job that needs to give me as end user simple step-by-step process from end to start. Making me take additional steps outside installation process and possibly first run setup wozard is missed security goal. I will not accept this as solution: https://forum.eset.com/topic/4255-setting-up-the-clients-update-with-eset-6x/#entry24611 hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN3637 You should consider consulting people in IT security business regarding how to make your products more professional. 3. Not making configuration exportable from v5 to v6 looks to me as amateur job. 4. Not making simple single upgrade process looks to me as amateur job. 5. You have made my life so complicated with v6 that I have chosen to stay on v5 version for less than one year until license expires. Then If I don't see changes in right direction I will switch to other antivirus solution. I'm really sad that I have to consider leaving you but you have made big mistakes with this release and leave me no option. Kind regards.

How do you control updates with ERA5? Even after upgrade to v6, you can create a mirror like with v5 using a v6 Endpoint product. Might I just add that even though I have moderate knowledge of using Linux servers I have never seen so complicated process of creating update server for Antivirus clients. This has to be GUI wizard based process that takes place during installation of product or later during first start of service.

How do you control updates with ERA5? Even after upgrade to v6, you can create a mirror like with v5 using a v6 Endpoint product. At the moment my machine for Antivirus server code is single machine on network that can get updates from your servers. This gives me control over what current version is on your side, my server and clients. Also I can change update port that clients use since they don't access Internet.

It hasn't been complexified although it may seem so at the first glance. The main role of ERA is to manage Endpoint clients, not to take care of distributing updates and doing other unnecessary stuff. Therefore various functionalities have been split into several components as of ERA/Endpoint v6. Instead of the small http server previously integrated in ERA, now you can take advantage of Apache HTTP proxy which has several advantages over the previous solution. Unlike ERAv5, Apache HTTP proxy doesn't download all available update files (380-400 files) but it caches those that are actually downloaded by clients. It's also much more powerful as the number of systems updating at a time from the mirror was limited in older versions which might have caused issues in large networks. Still, those who want to use the standard mirror can enable the mirror function in Endpoint v6. If I can't control from server side updates that clients are getting than this is mayor design fault. The people who suggest that server caches Antivirus databases from clients have no knowledge of security. Also our environment prevents clients accessing Internet or restricts them to specific content. If this will not change soon I will have to change Antivirus solution next year. I plan to stay on ERA v5 until then. I have also few friends that share same thought.

After a extensive diagnostics on client and gateway side I can say that PST corruption did not occur due to ESET product. Turn's out that our corporate gateway IPS policy (Intrusion Prevention Security Policy) was blocking specific incomming e-mail messages. Due to nature of POP3 protocol PST files got corrupted. But in your case since you are using 443 protocol it could be that ESET is scanning HTTPS traffic and blocking connection. It has to be turned off in several places. You should try running extensive diagnostics in Outlook and ESET. The both provide option to log activity.

@kenny.hoh Are you using Linux mail server? Dovecot?

@Marcos It has everything to do with ESET Products. @kenny.hoh Try changing "Disable checking upon inbox content change" option. I've had so many problems with large .pst files and ESE Endpoint Antivirus in my Company. Finally I found that changing this option helps.