Jump to content

TomasP

ESET Moderators
 View Profile  See their activity

  • Posts

    917

  • Joined

  • Last visited

  • Days Won

    45

 Content Type 

Posts posted by TomasP

    Reinstalled Win10, License error ACT.33

    in ESET Internet Security & ESET Smart Security Premium

    Posted

    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

    HOTFIX - ESET Enterprise Inspector version 1.3.1145.0 has been released

    in ESET Inspect On-prem (Detection and Response)

    Posted

    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:

    Eset Mail Security - research about dangerous file extension and log entry not 100% visible

    in ESET Products for Windows Servers

    Posted

    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

    EMA API - GetReports ReportName?

    in ESET Licensing for Business

    Posted

    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>

     

    ekrn.exe launches firefox

    in ESET NOD32 Antivirus

    Posted

    11 hours ago, itman said:

    Another thing that is not just adding up right in my mind is this attempted Eset root CA certifcate add into Firefox would make sense if FireFox was opened manually by the OP. As he posted, FireFox is not his default browser and it is assumed this browser, whatever it may be,  is what he is using for Internet access.

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

    ESET Windows home products version 12.2.30.0 have been released

    in ESET NOD32 Antivirus

    Posted

    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.

    ESET Windows home products version 12.2.30.0 have been released

    in ESET Internet Security & ESET Smart Security Premium

    Posted

    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.

    HOTFIX - ESET Enterprise Inspector version 1.3.1128.0 has been released

    in ESET Inspect On-prem (Detection and Response)

    Posted

    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:

    Current versions of ESET Endpoint for Mac and ECA, ERA 6.x and ESMC 7.0 Management Agents will not support the upcoming macOS 10.15 Catalina

    in ESET Endpoint Products

    Posted

    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

    Current versions of ESET Endpoint for Mac and ECA, ERA 6.x and ESMC 7.0 Management Agents will not support the upcoming macOS 10.15 Catalina

    in ESET PROTECT On-prem (Remote Management)

    Posted

    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

    Upgrade to Windows 10 version 1903 may cause boot error on Windows 10 with ESET Endpoint Encryption

    in Encryption

    Posted

    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/

×
×
  • Create New...