tbsky

Hi: I try to upgrade several endpoint 6.5 to 7.2. the old policies are left in upgrade installation, which I need to reset it. but there is one strange setting: password protection. I have setup new 7.x style password policy. but every time endpoint start-up, it will show information about "password setup changed". it seems never forget 6.x style password inside. if I uninstall 6.5 and install 7.2 then everything will be fine. but that's seems stupid. is there method resetting everything to 7.2 default when upgrade?

any update for this? I don't see difference between 6.x and 7.1 "not apply" policy. I wish to understand what I missed.

will this be fixed next version? or we need to fix it at configuration or mirrortool ? maybe the mirror from mirrortool didn't give enough files so client want to contact "repository.eset.com" ?

I download ESMC 7.1 appliance and take a look. indeed it is using mysql 5.6 and tomcat 7. however it seems a tricky setup, if I do "yum reinstall tomcat" then system become broken even I put back ESET modified web.xml and server.xml . with tomcat 9 I don't need to modify any configuration file, it works by default. maybe that's why document said ESMC 7.1 need at least tomcat 9. thanks again for your information!!

thanks a lot!! the document warns behavior change between 6.x and 7.x about "not apply" flag. but I don't understand what is it. so wait and learn from your confirm.

Hi: I tried to use all-in-one installer made by ESMC to upgrade endpoint 6.4 client. the all-in-one installer include a minimal policy with only password set. I assume the minimal policy will brings endpoint client to its default. it is true for new computers. but for some old computers, after upgrade with all-in-one installer, I found the "potentially unwanted" and "potentially unsafe" are enabled. so it seems some old policy brings to new after upgrade. if I uninstall endpoint and reinstall again, then everything is normal. so I wonder I still need force many default policy like ERA 6.x? I found the sentence below at document, but I don't understand what it means. I was thinking client will use default if not apply: Important ESET security products version 7: Not apply flag turns individual policy settings to the default state on client computers.

that's strange. official tomcat 7 can not work when I upgrade to ESMC 7.1. I will download 7.1 Appliance and take a look.

what I mean best is most reliable and verified. thanks for your clarification. but I have tested tomcat 7 and it is not working. document also said ESMC 7.1 need tomcat 9. do ESMC 7.1 Appliance actually use tomcat 7? document said SQLServer for Linux is not supported. if it is supported maybe I will give it a try. although I always prefer MariaDB. MariaDB is linux standard these days(I understand ESET may never want to support it).

may I ask which mysql version is best? I now stay in 5.7. in ERA 6.x time, ESET support 5.5,5.6,5.7, but 5.7 has problems. now ESET support 5.6,5.7,8.0. I assume 8.0 will have problems but I am not sure.

Hi: I just upgrade from 6.5 to 7.1. and I want to make sure I use the same component with Eset. linux: 64bit is a must now. that's fine since rhel7 already abandon 32bit. rhel7 or clone is best since Eset virtual appliance use it? tomcat: tomcat7 is not working anymore. that's unfortunate. ESMC 7.1 need at least tomcat9, and since there is no tomcat 10, tomcat9 is the only choice. BTW, ESMC 7.1 installation document is full of tomcat7 example, I think it need to be modified for tomcat9. mysql: ERA 6.x has problems with mysql 5.7, so at that time mysql 5.6 is the best choice. now mysql 5.5 is not working anymore, I assume mysql 5.7 is the best choice now? or mysql 8.0 is better?

we use mirrortool to mirror update and point client update to mirror(of course the mirrortool is updated version for 7.x). it was working file for endpoint 6.x. in fact it is working fine for 7.2 unless you click "check update" manually. if you didn't click, the scheduler update is working fine at background and shows no warnings. it seems if you click "check update" when there is no new update at mirror, the client will try to connect internet and show failed message.

Hi: just upgrade to endpoint 7.2. I have some offline clients. when I click "update" at client GUI the client try to connect "repository.eset.com". and it shows failed after that. I assume this is a bug since offline client can not connect to internet.

I know that. I mean why windows version make this work so complicated? why not like Mac/Linux version, just set primary server and secondary server in policy? it's very stupid to set dual profile and schedule to roam.

Hi: I just upgrade ERA 6.5 to ESMC 7.1 to mange endpoint 7.2. there are many problems. but I can't understand why I still see dual profile method to update for windows. Linux/Mac can define primary/secondary update policy. why windows still need dual profile and schedule to finish such easy job?

that's a great news. we are waiting for it. thanks a lot!

Previously ESMC 7.1 / Endpoint 7.2 was planned for 19H2. but since there are no beta out yet, I assume the plan was canceled/delayed?

Hi: I think mariaDB is multi-platform compatibility also. few people like Oracle/MySQL, but it is better than nothing. at least we can install ESMC at linux

Description: reconsider MariaDB support Detail: RHEL8 is coming. ESMC should try to support MariaDB, and not lock itself to some old mysql 5.6 version. it is hard to install old mysql.

I didn't install 6.6 yet. but since 6.6.2072.2 with latest update is equal to 6.6.2072.4, why the administration panel show warning about outdated version? it should not show this kind of warning..

hi: today I saw new version of endpoint 6.5 released. but I am confused since there is already version 6.6. is this normal or just an exception? I am still at 6.4 and wait for 6.6 to become mature.

hi: you are correct. the computer time of the PC is wrong, and it haven't update virus signature for 2 days. after fix the time issue and update virus signature, windows 7 won't complain anymore.

hi: we are running eset endpoint 6.4.2014.2 and we are satisfied with the version. we have tried eset endpoint 6.6 but it can not use offline mirror so we can not use it. today I notice the windows 7 message center warning about endpoint 6.4.2014.2 announce itself expired and need to update. I am shocked about the message. how can I use the old good version before eset fix offline mirror? I really don't want to try 6.5 since I know I will upgrade to 6.6 eventually.

hi: thanks for the quick reply. before the arriving of ransomware, the biggest problem we face is not virus, but the false alarm by anti-virus software. so we are happy when we have options for delayed update. now the biggest problem is ransomware, but I am not sure the benefit/trouble caused by LiveGrid. maybe we should try it on some computers.

Hi: I always use delayed update mode since endpoint V5. and I am very satisfied with the result. there is no critical false alarm for several years. I never enable Live grid. I wonder if the logic of Live grid is conflict with delayed update mode, since Live grid is the newest detection method?

sorry I didn't see the timeline post. is there any url to check?