TomasP

According to our information, the deliverability issues should be resolved now.

Hello, If you bought the license from one of our official resellers, it is bound to the country the reseller is based in. If this is the case and you later moved to another country and would like to continue to use your license, please contact your local ESET office who can help you with that. However, in case you bought the license from a grey market, we can't guarantee its functionality, as it was probably obtained somewhere else for a cheap price and then sold to you online by an entity not authorized to do so. In situations like this, we can only suggest to contact the reseller who you purchased from, ask for a refund and get the license from an official source, which can guarantee license validity and customer support. Regards, Tomas

Hello, Our service provider is currently having issues with deliverability to certain email domains, yours included; they have raised an issue with their upstream email provider. In the meantime, we apologize for the inconvenience. Tomas

Hello, No, this is not required, as per our documentation at https://help.eset.com/esa/30/en-US/?installation_requirements.html Regards, Tomas

The link leads to the beta section (to which only beta testers have access) and it announces the full release of ESET Endpoint Antivirus for Linux at https://www.eset.com/int/business/endpoint-antivirus-linux/

Thanks for the heads-up, our support page underwent some changes recently and unfortunately, some links were not transferred correctly. The content is available at this link.

Release date: February 11, 2020 Hotfix version of ESET Enterprise Inspector version (1.3.1145.0) has been released. The new hotfix build is now recommended for all customers. It addresses an issue with communication protocol changes that became present after recent LiveGrid updates which caused EEI to stop communicating with our LiveGrid servers. The build 1.3.1145 is now available via standard download on our website and we recommend using this particular build. Changelog: This is Hotfix only and thus all changes and new features remain the same as described in the original EEI v 1.3 release announcement. Release & setup notes: For EEI v1.3 we recommend to upgrade the EEI server first and then to upgrade the EEI agent. Upgrade from 1.2 (1.2.1) should be done via “Software install task” in ESMC, as we do not detect that the old version is not up to date (or upgrade it manually with *.msi file). From 1.3. to 1.3.1 it should now show that product is not up to date (so you can use one click upgrade -> Upgrade ESET products) Upgrade the EEI Agent (via “Upgrade ESET products” task, or “Software install task”, or manually, or GPO, SCCM, etc.) Reboot of the Endpoint is not necessary Known Issues: For a detailed list of known issues, see Known Issues for ESET Enterprise Inspector. Support Resources: Online Help (user guide): ESET Enterprise Inspector

Hello, sorry for the late response. Both Apache and PHP are planned to be updated in the first half of this year. Regards, Tomas

Hello @Patrick van Lier, You just need to remove the corresponding DNS entry (as per the screenshot below) and restart the ESA Core Service.

Hello @Joe-ESET2016, I have an input from our development team as well: a) This has been fixed in the latest version. In previous versions of the product there is a workaround, you need to delete all registry values starting with “mailserver” under the key HKEY_CURRENT_USER\Software\ESET\ESET Security\CurrentVersion\LogFilter b) Ad. “I would like to find out which file extension´s were blocked”: You can use “Log to events” action with macro %Attname% to log the name and extension of the blocked file – useful for “Attachment type” conditions, where the file extension doesn’t need to match the real file type. Regards, Tomas

Hello marco1958, This is a beta for ESET Endpoint Antivirus, i.e. a product for desktop environments. The version you are referring to is probably ESET File Security, i.e. a server product. We just posted the information in this "Linux Servers" forum section as well, because many Linux admins running ESET File Security may be interested in ESET Endpoint Antivirus as well.

Hello, We reached out to our product manager and he recommends the following: The keyword for ReportName is “ERA Usage”, however, we do not recommend to use GetReport call to get info about usage. We recommend to use “Search” where the request could look like this: (use your own LoginID instead of LoginID=xxx and real CompanyID instaed of CompanyID=123456) <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tem="http://tempuri.org/" xmlns:msp="http://schemas.datacontract.org/2004/07/MSPApi.Services.v2015_1.Requests" xmlns:models="http://schemas.datacontract.org/2004/07/MSPApi.Services.v2015_1.ViewModels" xmlns:arr="http://schemas.microsoft.com/2003/10/Serialization/Arrays"> <soapenv:Header/> <soapenv:Body> <tem:Search> <tem:request xmlns:models="http://schemas.datacontract.org/2004/07/MSPApi.Services.v2015_1.ViewModels" > <msp:LoginID>xxx</msp:LoginID> <msp:Token>xxx</msp:Token> <msp:OrderBy> <models:SearchOrderBy> <models:Column>Product.Name</models:Column> <models:Descending>true</models:Descending> </models:SearchOrderBy> </msp:OrderBy> <msp:PageNumber>1</msp:PageNumber> <msp:PageSize>10000</msp:PageSize> <msp:Criteria i:type="models:SearchGroup" xmlns:i="http://www.w3.org/2001/XMLSchema-instance" > <models:Criterias> <models:SearchCriteria i:type="models:NumericSearchParameter"> <models:Column>Company.Company Id</models:Column> <models:ComparisonType>IS</models:ComparisonType> <models:Value>123456</models:Value> </models:SearchCriteria> <models:SearchCriteria i:type="models:SearchGroup"> <models:Criterias> <models:SearchCriteria i:type="models:DateSearchParameter"> <models:Column>Snapshot Date</models:Column> <models:ComparisonType>ON_OR_AFTER</models:ComparisonType> <models:Value>2019-08-01</models:Value> </models:SearchCriteria> <models:SearchCriteria i:type="models:DateSearchParameter"> <models:Column>Snapshot Date</models:Column> <models:ComparisonType>ON_OR_BEFORE</models:ComparisonType> <models:Value>2019-09-01</models:Value> </models:SearchCriteria> </models:Criterias> <models:LogicType>AND</models:LogicType> </models:SearchCriteria> </models:Criterias> <models:LogicType>AND</models:LogicType> </msp:Criteria> <msp:SearchID>10006</msp:SearchID> </tem:request> </tem:Search> </soapenv:Body> </soapenv:Envelope>

Hello officeboy, Please follow the steps at https://support.eset.com/kb3742/ and submit a support ticket with samples of the uncaught emails and ESET Log Collector output for analysis, we will have the issue checked by our development team. Thanks, Tomas

Hello, Initial version of Security for Office 365 will only have basic configuration options, so you will be able to enable Antispam, but there will be no further settings to granularly modify its behavior. These options may come in subsequent versions. Tomas EDIT: It was pointed out to me that you could have also meant hybrid mode of EMSX, in that case the EMSX settings should apply to that as well.

Rather than displaying a pop-up, we'd like to alter the code that adds the certificate, so that it does not invoke any window on the user's desktop.

Certificate import is not done at browser startup, but independently by ekrn.exe, and to all browsers, not just to the default one.

Hello, this could be caused by importing our certificate for scanning the SSL communication. Even if it is not your default browser, we do that for all supported browsers installed on the machine. We do call the firefox.exe process during the certificate import, that's why it could be seen for a split second.

Hello Jackie, Thanks for reaching out to us. We could not come up with a direct answer to this, we will need to have it analyzed, so please submit your question via https://support.eset.com/kb3742/ so that it is tracked and we can have the behavior checked. Thanks, Tomas

Hello, The certificates created by ESMC MDM version 7.0, do not comply with Apple iOS 13 requirements. For more details and recommended solution, please read our support news article on this topic. Regards, Tomas

ESET NOD32 Antivirus, ESET Internet Security and ESET Smart Security Premium version 12.2.30.0 have been released and are available to download. Changelog: Version 12.2.30.0 Fixed: In case previously enabled, periodic scanning by Windows Defender is turned off after upgrade Fixed: GUI issues upon confirming 'Date of Birth' using keyboard Fixed: Various minor bugs and localization issues Known issues: Error in Windows Logs may appear once fix is applied (Error appears only once - during upgrade itself) Upgrade to Latest Version Upgrade my ESET Windows home product to the latest version If your ESET security product has not updated automatically yet, you can enforce product update by manually checking for update in the Update panel or wait until it updates automatically. Support Resources ESET provides support in the form of Online Help (user guides), fully localized application and Online Help, online Knowledgebase, and applicable to your region, chat, email or phone support. Online Help (user guides) Visit www.eset.com/contact to email ESET technical support

ESET NOD32 Antivirus, ESET Internet Security and ESET Smart Security Premium version 12.2.30.0 have been released and are available to download. Changelog: Version 12.2.30.0 Fixed: In case previously enabled, periodic scanning by Windows Defender is turned off after upgrade Fixed: GUI issues upon confirming 'Date of Birth' using keyboard Fixed: Various minor bugs and localization issues Known issues: Error in Windows Logs may appear once fix is applied (Error appears only once - during upgrade itself) Upgrade to Latest Version Upgrade my ESET Windows home product to the latest version If your ESET security product has not updated automatically yet, you can enforce product update by manually checking for update in the Update panel or wait until it updates automatically. Support Resources ESET provides support in the form of Online Help (user guides), fully localized application and Online Help, online Knowledgebase, and applicable to your region, chat, email or phone support. Online Help (user guides) Visit www.eset.com/contact to email ESET technical support

Release date: September 30, 2019 Hotfix version of ESET Enterprise Inspector version (1.3.1128.0) has been released. The reason is a bug occuring only under very specific conditions (not identfied during pre-release testing) causing the EEI Agent to crash. The issue has been identified and fully resolved. The build 1.3.1128 is now available via standard download on our website and we recommend using this particular build. All changes and new features remain the same as described in the original EEI v 1.3 release announcement. Release & setup notes: For EEI v1.3 we recommend to upgrade the EEI server first and then to upgrade the EEI agent. Upgrade from 1.2 (1.2.1) should be done via “Software install task” in ESMC, as we do not detect that the old version is not up to date (or upgrade it manually with *.msi file). From 1.3. to 1.3.1 it should now show that product is not up to date (so you can use one click upgrade -> Upgrade ESET products) Upgrade the EEI Agent (via “Upgrade ESET products” task, or “Software install task”, or manually, or GPO, SCCM, etc.) Reboot of the Endpoint is not necessary Known Issues: For a detailed list of known issues, see Known Issues for ESET Enterprise Inspector. Support Resources: Online Help (user guide): ESET Enterprise Inspector

Hello, We have published an important article about supporting our products on the upcoming macOS 10.15 Catalina. It is available in your ESMC/ECA webconsoles, but we would like to bring your attention to it here as well. All the details and necessary steps are described at https://support.eset.com/news7326/ Regards, Tomas

Hello, We have published an important article about supporting our products on the upcoming macOS 10.15 Catalina. It is available in your ESMC/ECA webconsoles, but we would like to bring your attention to it here as well. All the details and necessary steps are described at https://support.eset.com/news7326/ Regards, Tomas

We have identified a problem when upgrading a Windows 10 system with ESET Endpoint Encryption installed to the 1903 feature update. Installing the update can cause the system to crash (blue screen) when booting. We are currently investigating the cause and recommend not upgrading an encrypted system to 1903 until further notice. Systems that have been affected will need to be decrypted using our recovery tool (if full disk encryption was enabled) and then repaired using the Windows recovery console. See this knowledgebase article for more details: https://support.eset.com/kb7309/