Jump to content

tbsky

Members
  • Content Count

    158
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by tbsky

  1. Hi: ERA->ESMC->Eset Protect. maybe we should change back to the simplest ERA name. it's not a good sign. please don't play stupid name-changing games like microsoft windows/office
  2. thanks a lot for the hint! although it seems strange that I need to put the msi file to some other place to make it work. I think I need sperarate 32bit/64bit versions right? what will happen when 7.3.2039.1(Japanese version) get upgrade task to 7.3.2041? I want to make sure before doing these kind of upgrade...
  3. Hi: I use Active Directory to update Eset components for clients before. but one of the customer didn't have AD, so I try to use ESMC to do the job. it easy to do for one PC. but for multiple PCs I found: 1. there seems no way to list/sort the computers by Agent version, so I can not pick up the computers that need upgrade. am i miss something? 2. I can list/sort the computers by Product version, but when I create upgrade tasks, it is language specific. I have users with many languages. do I need to create multiple tasks for each language?
  4. It had been discussed again and again. but I still want to say: with endpoint 8.0, Please give up stupid MySQL and use MariaDB. check current system requirement it is really funny: MySQL ODBC driver versions 5.3.11 and later, 8.0.0 – 8.0.15 and 8.0.18 and later are not supported.
  5. Please check with your colleagues . after so many posts to forum, I still confuse about the situation of Japanese version. and I can not find any document about it. thanks a lot for your help!!
  6. since I can not create all-in-one installer before 7.3.2039.1, I always use msi version to install Japanese OS. I can not read Japanese so I didn't care much about the result. in your wording it seems there is a 7.3.2039.1 msi version? where can I download it?
  7. I don't understand. if I install 7.3.2039.0 msi version in Japanese OS, I get the localized Japanese version. what's the necessity for a special 7.3.2039.1 all-in-one version? and why only Japanese version?
  8. Hi: today I saw 7.3.2039.1 when check ESMC installer. only Japanese language shows that version. long time ago I asked about broken Japanese all-in-one installer but never get real reply. 7.3.2039.0 Japanese all-in-one installer is still broken and can not download. but surprise! 7.3.2039.1 can be downloaded. I can not find any information about this version. it this a special Japanese only version?
  9. @Marcos will endpoint release new version soon to fix the bug? and I didn't see current bugs list in https://support.eset.com/en/kb6927-known-issues-for-version-7-eset-business-products#ESMC I have bugs in mind like ESMC Japanese product repositories, MySQL database minor version incompatibility, Endpoint upgrade settings incompatibility, schedule update.. etc. hope ESET can update the current issues base on current time line. it is wasting time to check the forum message one by one...
  10. Hi: I already report this problem in March. I just upgrade to ESMC 7.2 and try to download japanese 7.3.2036 but still nothing. hope it can be solved soon.
  11. Yes. I have heard there will be PCU for update. we are still waiting the first PCU form Eset. hope the product can catch up with other vendors.
  12. that's bad. powershell script is very slow and can not easily execute by normal user. (eg: double click the script won't get it run). and it changes too quickly (there are many versions and powershell core will replace powershell). vbscript is much better for general deployment if MS still support it.
  13. maybe your EMSC MySQL get update like mine?
  14. Hi @Marcos @MartinK where can I download Japanese version of EEA 7.2? maybe I need to install Japanese windows to test, but I hope I can get some information before that.
  15. I don't understand. the default policy of "Program component update" is "never update". do you mean we still need set custom update server for the "never update" policy?
  16. hi @MartinK thanks a lot for your confirm. indeed 7.1.2053.1 is ok. since this is the first time I need Japanese version, I don't quite understand the situation about the locale. if I install the msi package downloaded from eset web site, (eg: eea_nt64.msi), will the Japanese OS get Japanese nod32? I get English/Chinese UI correctly with the msi package. now I am not sure what will Japanese OS get with the msi package.
  17. hi @MartinK I still can not make all-in-one Japanese version. I can wait if it won't take too long to fix. will this fixed by Eset server side, ESMC component update, or next ESMC version?
  18. sorry @MichalJ. I have two questions about v4 1. can I use MirrorTool to mirror virus signature for v4 so I can update signature in local network? mirror tool support ep4 product, but I don't know if it is compatiable with v4 or how to configure v4 to use the mirror. 2. you said ESET will no longer support linux full UI. will v4 be abandoned soon ( < two years)?
  19. thanks a lot for your confirm!
  20. I got it. so these "desktop notifications" is the only xwindow gui for v7. you can not control v7 in xwindow gui. is that correct? so the desktop environment requirement is for "desktop notifications", although I don't know what it is since I never get one.
  21. I hope you are correct and I can use it in the near future! can someone from ESET confirm this?
  22. v7 has the program "egui". but document didn't mention it and I can not start it.
  23. Hi: I have asked the question before but didn't get answer. so I think I need to issue it again and wait for fix. the previous thread is at
×
×
  • Create New...