Jump to content


  • Content Count

  • Joined

  • Last visited

Profile Information

  • Gender
  • Location
  1. There is no problem sice server restart case can be closed, i will update the mail security later.
  2. It is true it has not been restarted for at least 3 or 4 months or even much more. After windows updates, and a restart, the mail security seems working fine, no error or warning entries in the logs. I will report back after a couple days.
  3. no-no i have 7.0.10019.0. i just linked probably the wrong article, and also missunderstood the ESMC upgrade article. The only way to update the version is to reinstall the product. Am i correct?
  4. If I understand this article: https://support.eset.com/en/kb7010-upgrade-eset-mail-security-for-microsoft-exchange-server-from-4x-to-the-latest-version-7x I have to do a reinstall. edit: https://help.eset.com/emsl/7.0/en-US/installation_upgrade_era.html I will try upgrading via ESMC
  5. This is in production environment. If there is newer server OS released and something worng with the older one you can not always reinstall the newer OS, and hope for the error gone. But I do understand the newer version possibly comes with advantages, so I will try to update the product. Could you please link some article how to do it? I never done before.
  6. Dear support! We have on premise exchange 2013 running on Windows server 2016 standard and eset mail security version 7.0.10019.0. Today I logged in to the server, and the eset mail warned me about the Antivirus protection module, that something is not okay i dismissed the messeage. I checked the logs, and started Eset shell, used the get status command, to check the status of the modules, and all are enabled, getting the "maximum protection" messeage. To be sure, I turned off and on the module, everything looks fine. But, in the log files I still see warnings, look for the picture attach
  • Create New...