Jump to content

mtieu

Members
  • Posts

    3
  • Joined

  • Last visited

Reputation

0 Neutral
  1. Trend Micro OfficeScan 10.6.1062 MEE 1.70.0.1200 What exclusions specifically would you set up? for the program directories of each other? what if they try to access and scan the same file at the same time. Those types of conflicts are what he says can crash their machines.
  2. Are there any conflicts at the kernel level or anywhere else when running MalwareBytes Enterprise Edition alongside an AV scanner such as Trend Micro OfficeScan? We have a security researcher that said it will conflict, so his suggestion is for us to run TrendMicro OfficeScan as the primary AV scanner, and turn off realtime scanning in MalwareBytes EE and only use it as a remediation tool. He said running both in real time scanning will be a conflict and is not recommended. Can anyone give me some definitive data to show to management? I have found that using both of them at the same time both scanning has been very beneficial to our environment and has stopped alot of things that TrendMicro could not find or stop. I haven't seen any crashes or the sort yet, but that is the concern. He said Kernel conflicts specifically. Anyone have any thoughts or evidence to prove otherwise? He said they are both essentially Antivirus software, not AV and AM (Antimalware). Thanks! -Mike
  3. There was no quick way to repair hundreds of computers on the Enterprise level. Computers had to be put in safe mode but that was not possible because of physical locations of these computers. Me and my team were up to very early this morning fixing these computers. You should have dedicated support for your business and Enterprise customers who pay alot of money for this product and get the same email help that anyone else gets. Im not saying that we have to be treated any differently, but when you have hundreds or even thousands of computers to deal with instead of just one, it would have been very helpful if I had an engineer working with our team to get this resolved. This is one of the fatal mistakes, along with not testing that update to begin with. The problem is though, is that there is no reason that core system files in windows/system32 should ever be flagged as a trojan downloader. If this is the competency level of your developers and engineers working on your definitions, I strongly suggest you step your game up. Sounds like the work of a scorned employee or someone already on their way out with a chip on their shoulder, because if it isn't, I am highly dissapointed in your product and procedures. We licensed 2100 computers and I believe we are going to scrap this product. I think its a great product, honestly I do, but management is not so convinced and we are looking into other options and products. I recommended this product for our environment and championed the deployment, and whatever the process may be, it has failed us. No excuses. I thought MEE was enterprise ready, but I was sorely mistaken. You dont have the testing and quality control of what it takes to be in the Enterprise game just yet. Close, but not there yet. I feel that I should have waited until your product was throughly tested and developed into a 2.0 or something. I was afraid I was going to be handed my walking papers today because of your "great" product. Good thing I got it all repaired, but I believe the damage is already done. This may be the death knell from corporations wanting to buy into MalwareBytes Enterprise Edition. I have the pro version at home and I love it, but when thousands of computers are affected at a large company, it leaves a really bad taste in everyones mouths, from management down. Sadly, I am not the only Administrator that feels this way, because its all over the place now and cannot be trusted Enterprise level. I really liked this product and I even praised it in our meeting we had yesterday morning. This situation made me eat my words and made me look really bad honestly. I don't know how to fix this and i would really like to get a refund on this purchase, but in the end, its going to take some heavy convincing to get this redeployed out in our environment from a management stand point. Many man hours and manpower was wasted because of your 8 minute untested update.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.