Marcos

It's not about voting in this forum. The staff responsible for making decisions about priorities and resource allocation does that based on market requirements submitted by local partners and distributors. I'd recommend trying out the Windows version first once available to see what features EEI has and if you are interested in a version for Linux and possibly VA, contact your local distributor. The more organizations are interested in a particular feature / product, the higher chance we will be able to deliver it to you.

If a plug-in is not detected as a potentially unsafe or unwanted application, you can't block it as any communication is performed by a browser and blocking the browser completely is not desired.

Currently not. The server will run on Windows only unless there's a high demand for a Linux version too.

We will have a new EDR product called ESET Enterprise Inspector which will enable administrators to receive alerts about suspicious operations performed in a network based on rules (pre-defined or custom) with an option to block suspicious files (currently by SHA1) and to create reports via ERA. EEI is planned to be released in a few months. Currently we're going to deploy a beta to a couple of corporate clients for testing purposes.

I'd also suggest enabling pre-release updates to make sure that you have the most current modules installed. However, don't switch back to release updates, otherwise you'd need to delete one folder in safe mode manually (see https://forum.eset.com/topic/11669-solved-eset-internet-security-v101204-firewall-bug/?page=4). Using pre-release updates on non-production systems is recommended for advanced users as it gives you benefits that I have mentioned in the linked topic.

It's not in the documentation because the documentation was created at the time when a certificate whitelist was not yet incorporated in ESET's products. We are currently considering discontinuing ESLC as it has no noticeable benefits for users after ESET's products have evolved to the extent when they themselves can distinguish between most of trusted and untrusted PE files.

It should be compatible as no substantial changes were made to CU that would prevent previously Win10 compatible versions from working properly. However, I'd strongly suggest to upgrade to EPv6.5 in order to take advantage of new protection features provided by ESET and Windows 10.

Not only outgoing but especially disabling read email can often solve various issues.

It could be caused by a 3rd party tool or possibly by malware. Please generate a Procmon boot log and also collect ELC logs as per the instructions linked in my signature. When done, compress the Procmon log(s), upload the archive together with ELC logs to a safe location and pm me download links.

Please do the following: - enable SSL/TLS filtering - start logging with Procmon and Wireshark - disable SSL/TLS filtering - make ESS connect to an OCSP server - stop logging - compress both logs, upload them to a safe location and pm me download links.

Please collect logs with ESET Log Collector as per the instructions linked in my signature. If the generated zip file exceeds 2 MB, upload it to a safe location and pm me a download link. Otherwise attach it to the pm.

Not sure what version of ESET you had installed before the upgrade but I'd suggest uninstalling it completely, removing ESET in safe mode using the uninstall tool as per http://support.eset.com/kb2289 (may not be needed) and installing the latest v10.1 from scratch by downloading Live installer from www.eset.com and running it.

As per the document http://download.eset.com/manuals/eset_eslc_userguide_enu.pdf : "To update ESET Shared Local Cache, please download the newest installation file from download servers and re-deploy appliance or re-install .rpm.bin package." However, since implementing a certificate whitelist in ESET's products via an automatic module update, ESET Shared Local Cache has no noticeable benefits and it's no longer needed unless you use many unpopular PE files (exe, dlls) on your VMs.

Generally I'd suggest disabling all add-ins but ESET and then re-enabling one at a time. Also try leaving only scanning of incoming email enabled in the email protection setup (ie. disable scan of outgoing and read email).

In EPv6, the Import function looks as follows: Ie. you select a text file with one serial number of a device per line. In the ERA policy editor, the description is missing which will be fixed via a Configuration module update.

What version of Chrome do you use? What version of EMS (tap About in the menu)? What modules (tap ESET Mobile Security in the About window)? Do you have Additional accessibility permissions enabled for EMS in the system Accessibility setup?

Try the following to ensure that the current ESET root certificate is imported into the CA certificate stores: - disable SSL/TLS filtering in the advanced setup - restart the computer - without starting any application, re-enable SSL/TLS filtering - check if the issue is gone.

Yes, normally you can switch back to regular updates. However, currently we don't recommend it due to a possible bug in updater that would not remove the new module em008k_64 unlike other modules and the firewall module em008 on release servers is not currently compatible with the em008k module on pre-release servers. It's possible to do that but one would need to follow my instructions above and delete " c:\program Files\ESET\ESET Smart Security\Modules\em008k_64" in safe mode.

By production machine I mean a machine that you use for everyday work and where outages caused by receiving possibly faulty modules in the first wave (something like Insider program for Windows 10) are not an option. However, due to a low number of users receiving pre-release updates, users with regular updates usually receive the very same modules after a few days or weeks if no issues are reported. I would like to emphasize again that pre-release updates are updates that have been thoroughly tested by ESET QA and that have been installed on many of our production systems too. They are not kind of updates you should be afraid of to use on home systems, especially if you are advanced users. Using pre-release updates gives you the opportunity to report possible issues and have them fixed before they are distributed to all users. Also you have an option to switch to regular updates to quickly fix an issue caused by new modules until we put a fixed version of a particular module on pre-release servers. This is no longer possible once a new faulty module has been put both on pre-release and release servers and only ESET staff can fix it then on update servers.

Should you encounter the issue again, please collect logs with ESET Log Collector as per the instructions linked in my signature. Upload the generated zip file to a safe location and pm me a download link.

The distributor for Macedonia is NORT (http://www.nod32.com.hr). See their website for contact information.

Do you have ESET Endpoint installed on clients? Does temporarily disabling real-time protection on the server (EFSW) or on a client (ESET Endpoint) make a difference? If so, it it enough just to disable scanning of network drives in the real-time protection setup? Anyways, I'd suggest moving this to a new topic as it concerns Windows Server 2008 R2 and not WS 2003 which is discussed in this topic.

Our server products don't include a firewall. A personal firewall is only a part of ESS/EIS and Endpoint Security which are not products intended for servers.

Don't switch from pre-release to release updates yet, otherwise you'd need to manually delete the folder "c:\program Files\ESET\ESET Smart Security\Modules\em008k_64" in safe mode. We'll let you know when it will be ok to switch back (although the best would be if you keep pre-release updates enabled all the time on non-production systems).

Do you have also some other Outlook add-ons installed besides ESET?