Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


tbsky last won the day on February 5 2019

tbsky had the most liked content!

Profile Information

  • Location
  1. just give it a try and the answer is no. you can not uninstall v6 with v7 msi files. so what's is the correct command to remove v6 without v6 msi files?
  2. Hi: I need to uninstall endpoint v6 then install v7 to get rid of the v6 policy inheritance . I wonder what's the best command line to use in script. after searching the forum, I found the command is MSIEXEC /uninstall X:\ESET\eea_nt64_enu.msi /qb REBOOT="ReallySuppress" PASSWORD="password" I don't have v6 msi now. can I use v7 msi file to remove v6? is there better command to use without using the msi file? thanks a lot for help!
  3. I don't know if you have heard about the virus of my case. one of our business partner was infected by some kind of malware. all the outlook email content and contacts are stolen. someone use the email content and contact address to attach the virus. they only send to specific email address in the contact, so the general email RBL won't block the infected mail server ip address soon. and they change the virus file every day. very annoying.
  4. indeed ESET have very few false positives. that's what I love most. you can prevent new malware by good human behavior, but you can not prevent the damage from false positive. in fact I had zero false positive since I use delayed update. I am very satisfied with the setting. In my current case I don't think regular update will help. since both livegrid and virustotal won't detect it. only Macfee and sometime Microsoft can detect the virus at the beginning. Microsoft is know to have high FP, I don't know about Macfee. but it detect the virus every time from virustotal engine. you said "it won't help in case of malicious documents". do you mean livegrid didn't detect document, only local virus signature will do the work? PS: as usual, virus from yesterday is detected by nod32 now. but today we still get new viruses, and they will be detected tomorrow. I don't know when will this stopped...
  5. Hi: I use delayed update for maximum stability. but start from last week we are attacked by some kind of phishing mails. it includes a word doc virus about invoice, and that doc file changed every day. nod32 normally detect it after one day. livegrid doesn't detect it. upload the file to "virustotal" for scan, their nod32 engine also can not detect it (but will detect it tomorrow). I wonder if the "delayed update" can co-work with livegrid?
  6. maybe set both 6.x and 7.x password would help, I haven't try. but I will upgrade all client to 7.x, so the policy would be strange at that time. and if someone remove the strange 6.x policy one day, the same behavior may come back. your information is valuable: "it might not work as expected in case settings were changed before upgrade to 7". so to prevent all these strange policy problem, I think I should uninstall all the 6.x before upgrade. I need to study how to do it. but may I ask again last time: is there any method to reset default policy for endpoint 7.2 without uninstall ?
  7. unfortunately our local ESET support can only answer general questions. when I already RTFM , I can only ask for support in the forum.
  8. according to Endpoint 7.2 document, there should be a different way for policy. although I don't know what it is yet. still waitng for someone answering the forum question.
  9. howto do that? I didn't set password 6.x style policy. I only set password 7.x style policy. and client shows about now password settings get improvement every time. in fact, I want to reset all settings to 7.2 default without uninstall. is that possible?
  10. 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?
  11. 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.
  12. 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" ?
  13. 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!!
  14. 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.
  15. 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.
  • Create New...