Jump to content

tbsky

Members
  • Content Count

    161
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by tbsky

  1. On 3/19/2021 at 3:57 PM, MichalJ said:

    Hello, ESET Endpoint Antivirus 7/8 for Linux do have a local user interface, however it is intended to be "managed", meaning controlled via the console, so interface gives access only to a limited set of information, as listed here: https://help.eset.com/eeau/8/en-US/?gui.html. Now, with ESET PROTECT Cloud being available, we do not see a valid reason to provide a full blown UI for the end users.  

    Hi:

    it may work  in an ideal environment which all the PCs are management centralized. but sometimes it is not the situation.

    some of our customers sell specialized linux pc controllers to manage bigger machines. they have been asked to install anti-virus software before shipping to prove the system is safe. normally the machines work in a closed network. but they still require anti-virus software for the second/third defense although the virus-database may not update frequently.  ESET is our friend for the situation. hope the V4 virus-db can still be maintained after 2021-August.

     

     

  2. 20 hours ago, MartinK said:

    If I recall correctly, there are some issues with newer connectors on Linux - so it is possible that those version do actually work on Windows platforms.
    Problem with linux variants is way how ODBC connectors are built, which conflicts with EP application itself.

    Oh. never thought about windows. I always use linux to host ERA since v6. in fact it is one of the reason I encourage our customers to migrate to ESET endpoint. it is a good thing that ESET can take care about linux environment.

    BTW, it is not so good that ESET abandoned desktop gui linux version since V4. many of our customers need it. we need to find a replacement for it now.

  3. Hi:

       I was using mysql-connector-odbc 8.0.18 with ESMC/Protect at one server over 1 year. I didn't encounter strange things like previous ESMC versions. maybe I am lucky or maybe newer versions of ESMC/Protect fix something.

     could you re-test newer version of mysql-connector-odbc? I think we should not stay at mysql-connector-odbc 8.0.17 forever as document said.

  4. 20 minutes ago, Marcos said:

    1, You can send an ESMC component upgrade task to all machines. Those with an up-to-date agent will not download it and install it again.

    2, When creating a sw install task, do not use the repository but choose "Install by direct package url" and point it to the msi installer that would be shared for users. The msi is multi-lingual so it should install the same language version as the already installed one. I'd recommend trying it on 2-3 clients with different lang. versions first.

    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...

  5. 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?

  6. On 9/28/2020 at 10:48 PM, Marcos said:

    I don't think that v7.3.2039.0 was released in Japan. I can check it with colleagues but I assume that v7.3.2039.1 was the first official release of the Japanese version.

    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!!

  7. 31 minutes ago, Marcos said:

    I don't think that v7.3.2039.0 was released in Japan. I can check it with colleagues but I assume that v7.3.2039.1 was the first official release of the Japanese version.

    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?

  8. 6 hours ago, Marcos said:

    The Japanese partner releases their localized versions of ESET's products with a delay. Changes in the last version numbers indicate changes in localization or modules.

    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?

  9. 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?

     

     

  10. @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...

     

  11. 12 hours ago, TheSkymanDC said:

    Marcos - in the past we've been told that a minor upgrade as 2032 to 2036 would not require new install.  Is this still true.

    And I'm with Roger on this - having to reboot after a minor upgrade is really unexpected and somewhat painful.

     

    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. On 3/3/2020 at 1:23 AM, Ian 1 said:

    Powershell script for Deployment

    Could deployment scripts eg. ESMCAgentInstaller.bat be provided as Powershell scripts .ps1

    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. 6 hours ago, dpa said:

    Hi

    Last week our ESMC software depository went from having whatever packages we required to completely empty. 

    I have spoken directly to a member of support, however no progress has been made. 

    I have taken steps to adjust the source of the repository and i am able to connect to hxxp://repository.eset.com/v1/info.meta

    I have followed the following article - https://support.eset.com/en/kb6749-eset-security-management-center-repository-is-not-working-7x

    What are the reasons why this will just suddenly occur? 

    We have been offline for far too long and need the situation rectified ASAP particularly with so many of clients users working remotely on devices that require connection to the ESMC

    Thanks, DPA

     

     

     

    maybe your EMSC  MySQL get update like mine?

     

  14. On 4/1/2020 at 11:14 PM, MartinK said:

    I have not verified, but in case you download EEA 7.2 from global webpage (i.e. not Japan page), installer will most probably contain Japan locale, i.e. it will install with Japan locale on Japan systems. It might happen that once there will be EEA 7.2 for Japan, it will be actually new build with additional fixes.

    Maybe @Marcos can also help to confirm, how is it with support of Japan locale in global releases.

    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. On 3/28/2020 at 4:32 AM, MartinK said:

    Problem is unfortunately in ESMC itself, but actually issue is that ESMC is offering to create Japaneses installer with version, that is not available in such locale (not yet released). Workaround in this case would be to select manually version that is available in Japanese locale, which is for example 7.1.2053.1 (currently latest with this locale).

    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.

  16. On 3/19/2020 at 3:57 PM, MichalJ said:

    Hello @tbsky, yes, that is correct. Endpoint Antivirus for Linux was developed for the managed (controlled from ESMC) environments, and for the power Linux users. From our POW, there is no practical need by a standard LInux user might want any level of local management of AV product installed on his Endpoint. As of now, we are not planning to bring back the full blown UI. 

    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)?

  17. 19 minutes ago, MichalJ said:

    Hello @tbsky, yes, that is correct. Endpoint Antivirus for Linux was developed for the managed (controlled from ESMC) environments, and for the power Linux users. From our POW, there is no practical need by a standard LInux user might want any level of local management of AV product installed on his Endpoint. As of now, we are not planning to bring back the full blown UI. 

    thanks a lot for your confirm!

  18. 6 hours ago, MartinK said:

    I have not verified but my best guess would be that desktop notifications do work only in this specific desktop environments.

    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.

×
×
  • Create New...