Jump to content

Glitch

Members
  • Posts

    59
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by Glitch

  1. 2 hours ago, Marcos said:

    EFSW 6.5 reached EOL in December 2022: https://support-eol.eset.com/en/policy_business/product_tables.html

    I was under the impression that you have reported the issue for EFSW 9.0.12017. Please clarify.

    Correct it is about version 9, i have sent you the log file via a private message. 

     

    I was referring to the certificate expire with previous eset products as it happend before sometimes just overnight. 

  2. We suddenly have a lot of customers complaining about that HIPS is not functional on their  9.0.12017.0 install of Server Security. 
    How can we upgrade to V9 latest version or V10 latest version? Without manual interaction of removing the old ESET? 

     

    We do get tired of ESET running in certificate issues these last few years. And we as an MSSP have lost users due to that so  that we have to carry an alternative product next to ESET. 

  3. On 12/11/2023 at 1:55 PM, Marcos said:

    Many of our users have probably already updated to the latest v9. It is crucial to keep the product updated, in this case at least to the latest version v9 if not to v10. We had been notifying about the expiring Entrust certificate and the need to upgrade the product and the OS to an ACS-compatible version throughout this year.

    Please advise HOW we have been notified we have a 1000 servers with this issue at the moment, we are getting sick and tired of ESET and their certification errors time and time again.  Is there a hot fix that we can use from 9.0.12017.0 to 9.0.12019.0 ???

  4. 8 minutes ago, Marcos said:

    It is possible to disable application feature updates in the advanced setup. This won't work for security and stability updates as well as when the product goes EOL and there's a risk that module updates for your product version will be terminated which would expose your computer at risk.

    Exactly off is off and not force it. For example the update of windows server 2012 for example if you forced that it would have wrecked our environment. ESET should learn to in some cases those updates should not be allowed and that is why customers turn it off. Now it is like it is off but when we think it should be on it will be on.  

  5. For our network implementation we use the offline license files to activate ESET Antivirus or Endpoint security depends on the network topology. 

    However with version 10..0.2034.0 release when we do that same command we get: Error Executing command. 

    Has this procedure changed? We can't find it in the release note of this version release. As it is a very large group that we manage by doing it like this we definitely need this to work. 

  6. All clients are managed via our own tooling and RMM we don't use the ESET solutions as they are too difficult for users to install remotely, too data hungry etc.  And the bandwith is too narrow to correctly maintain those.  No problem in general but it appears that ESET is forgetting a big chunk of the market.  

     

    For version 9.1 we have issues with updating and micro updates for example. File not found etc. 

  7. Hi Marcos, 

    I understand but where the problem "Full Support is granted to the latest release of the latest major version and the latest release of the earlier major generation (for only one year after the release of a new product generation)."

    A end user does not know which version will be the latest major within a generation it can be 8.1.2001 for example or 8.1.3001 etc. As this is unclear the user has to use basic business principal that the version he purchases at that moment is the latest version and thus has the long support period. We have a few screenshots that  version 8.0.2028.0 was Limited support until version 9 + 3 years.  however when version 9 was released it was suddenly changed to end of november this year. Version 9 was released in November of 2021 meaning that the version according to the own EOL should be supported till late 2024 and not EOL it 2 years sooner. Also when buying a product and thus the support etc the EOL at purchase is valid so that can't be changed. It can only be changed when the user would have known that version 8.1.XXX would be the latest major version. 

    V8.jpg

    V9.jpg

  8. 4 hours ago, MichalJ said:

    We have many customers, that have "air gapped" environments, but setup in a way, that the entire environment is air gapped. So in such case, it would make sense to have the management console. I understood that in your case, the individual machines have no network connectivity, so they can´t connect even to the management server. 

    Correct and as a 30K+ seat owner of ESET we do find it disturbing that its getting so difficult to obtain a normal installer.  Anyway as we already have found a few bugs in the latest 9.1 release we will hold the upgrade for now. 

  9. Not sure where to post this but ESET is breaching their EULA and thus is liable for support.

    Reason : ESET is not clear with their EOL policy. Basically when a business license is sold the moment that a license is sold the EOL policy that is used is valid.  To explain:


    We received a support case in which an Endpoint V8 indicates that it will no longer receive support at the end of this year. This message was/cannot be clicked away and is also very special. ESET states according to their EOL statement on their page that an old version is supported +3 years after the release of a new version, but something suddenly goes wrong, long live the wayback machine.
    V9 launched in November 2021
    With that, version 8 should be supported until November 2024!
    If we now suddenly look at the website, V8 is supported until the end of this year for limited support, which is not correct.  

    This has to do with that ESET says their latest major version is supported for 3 years after a major Vx release however as it is no known on the moment in time if a version is the last major version it would mean that the version available at the said time a customer is purchasing the product that is the latest version which will receive that support of 3 years. 

    Currently ESET is changing the rules of the game because nobody knows what will be the last version before a new major release is done so I as as a customer today look at the site and will see version 9.1 is supported for 3 years after V10 release however if version 9.2 is released it will suddenly drop from 3 to 1 year which by law is not allowed.  How to deal with this?   

×
×
  • Create New...