Jump to content

nd1818

Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About nd1818

  • Rank
    New Member
  1. I'll check with our support team to see if they are still seeing reports of this. At this point, when issues persist, they end up removing the malwarebytes client. In our environment, we've disabled realtime scanning with MWB completely via policy, and only have it on with SCEP yet that didn't seem to do it for all machines. If I hear of some more machines with the problem (reproducibly) I'll PM you. Tough thing is that users get so frustrated that support just rips off MWB to get them back up and running, which I definitely understand. Will ask them to give a user a loaner if
  2. We've been mostly OK for the past few weeks with the exceptions in place and the protection agent in Malwarebytes disabled by policy, however in the last day we're starting to see a number of machines with high CPU utilization for SCEP and MBAM. Are we seeing a new, similiar issue? Previously it wasn't so much CPU spiking as it was Disk IOPS. Anyone else seeing a recurrence of these/related problems?
  3. Not sure that the majority of the windows world is running the combo of Microsoft security and Malwarebytes agents necessarily. Yes, this sucks, but in the end, if the vendor recommends not running two realtime threat protection agents on one machine (the vendor being Microsoft in this case), then the onus is on us ultimately to have the correct procedures and protection in place to prevent the conflicts. Lessons Learned: Make sure you have exclusions in place for the likely conflicts of security agents Maybe structure SCEP policies for phased definition updates? Have
  4. Microsoft told me explicitly today that the definition updates they made started to target Malwarebytes protection processes as malicious. This came from my TAM, not a premier support engineer. Our TAM did say that MS doesn't supported two realtime protection agents running at the same time but said they are still working with Malwarebytes as they recognized that the Malwarebytes product is better at detecting certain unwanted adware that may not be flagged by SCEP. He said he does not foresee any real change in Microsoft's stance on the multiple RTP clients though... they don't intend to
  5. Have been having the issue at my company as well. Saw a spattering of issues on Friday, flagged it as a possible issue that could spread, so we got a plan into place (before we knew SCEP was involved). The plan was if we heard more reports, we would disable the protection module in our Malwarebytes enterprise policy. We believe this did mitigate a fair number of machines from having the issue. However, some machines still presented the problem before the Malwarebytes policy could take effect. Once we found this forum thread with the SCEP exclusions, we made that change in our SCCM SCEP po
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.