tbsky
-
Posts
231 -
Joined
-
Last visited
-
Days Won
3
Posts posted by tbsky
-
-
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.
-
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!!
-
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?
-
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?
-
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?
-
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...
-
18 hours ago, MartinK said:
Unfortunately this glitch was not resolved yet.
Problem is that ESMC shows versions, that are actually not available in JPN language, as last version supported in JPN probably version 7.1.2053.1 -> manual selecting of it should work.that's not acceptable and need to fix.
-
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.
-
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.
-
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.
-
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?
-
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.
-
On 3/23/2020 at 10:54 PM, Marcos said:
I see that it was fixed in Endpoint 7.0.2091. Just make sure that a custom update server is used and that program updates are disabled.
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?
-
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.
-
On 3/17/2020 at 2:18 AM, MartinK said:
Seems that this issue was already reported few days ago so I hope someone will be able to check and possibly resolve soon.
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?
-
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)?
-
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!
-
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.
-
3 hours ago, Marcos said:
As far as I know, it should be addressed in the next service release of Endpoint 7.2.
thanks a lot for your confirm!
-
22 minutes ago, Nightowl said:
It must be for the future usage , when they finish developing the simplified GUI that this product will have.
I hope you are correct and I can use it in the near future! can someone from ESET confirm this?
-
2 minutes ago, Nightowl said:
Could it be that reason? that I use MATE? , but what the GUI has to do with it , it doesn't have a GUI even , I am mistaken somehow?
v7 has the program "egui". but document didn't mention it and I can not start it.
-
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
-
47 minutes ago, Nightowl said:
I believe it was meant for it to be controlled through the ESMC but I sometimes you don't want an Agent on that device , like on my case , I am stuck with the CLI and still I can't get it to work.
I don't know why v7 need desktop environment when it is only CLI. in document v7 system requirement:
Supported desktop environments:
•GNOME
•KDE
•XFCE
-
11 minutes ago, Nightowl said:
Only by commands , as far as I know there should be a simplified GUI for the v7 desktop but probably that will also come for endpoint , I can't seem to get it running , it's telling me to update my linux and the product activation has failed but yet still I can update to the latest modules and I can't get it to start working.
Here you can find information about commands : https://help.eset.com/eesu/7/en-US/retrieve-module-information.html?index.html
I rolled back to 4.095
yes I had study the document. I start a local scan for the computer. the scan finished but I don't know where to check the scan result. the document didn't say about this. it seems strange if everything is cli. eset file security at least has web interface. I don't understand why a desktop product only has cli.
batch update Agent/Product
in ESET PROTECT On-prem (Remote Management)
Posted
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?