Jump to content

ma77y88

Members
  • Posts

    43
  • Joined

  • Last visited

About ma77y88

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    U.K.
  1. OK, so when is the support in ESET Protect due? It seems bizarre to announce a feature but not allow the capability within the console!
  2. So why was this listed as a feature for 10.1.2046.0? New: Support for forced check of product auto-upgrades via ESET PROTECT console
  3. @Marcos Please could advise on this feature please and where in the console you can force the check?
  4. We've already got all that set, this feature is supposed to force a check for the auto-upgrade as currently it is random when it happens and the only way to manually do it is on the client itself which is obviously not practical in a large environment.
  5. This seems to have worked for us on-prem. Clear C:\ProgramData\ESET\Bridge\Proxies\Nginx\data\eset_cache
  6. The ESET Protect Console is now showing both 10.1.1288.0 and 10.1.1292.0 as up-to-date.
  7. I'm not sure what you mean - what exactly do we need to do or do we just need to wait for something to be fixed in ESET Bridge and if so, how long?
  8. Do we need to turn spread control off or is this centralised?
  9. Our OS is Microsoft Windows 10 Enterprise LTSC 2021 on latest patches and using ESET Bridge also.
  10. Same issue too, upgrade task completes with no update of the agent.
  11. Hi, following on from this, in 10.1.2046.0 there was a feature named in the change log... New: Support for forced check of product auto-upgrades via ESET PROTECT console Where is this available in the console as I can't seem to find it?
  12. Hi, where is this feature available - New: Support for forced check of product auto-upgrades via ESET PROTECT console? I can't seem to find it and running the latest version.
  13. This is the same with us too, using the Mimecast Outlook plugin. Is this a known issue? It's been happening since .2051 but is fine with .2046
  14. We've got clients reporting 'The ESET LiveGrid servers cannot be reached' but when this error clears on the client, it still shows it in the ESET Protect console for a while and doesn't update on the next agent interval. Is this by design or should it clear straight away?
×
×
  • Create New...