Jump to content

BryanWright

Members
  • Posts

    13
  • Joined

  • Last visited

Everything posted by BryanWright

  1. I wonder if the underlying issue isn't a windows issue with the presence of two real-time scanning engines? Since Microsoft says this is an unsupported configuration. Maybe it doesn't matter what those two real-time engines are, just that there are two of them. If that's the case and we can't truly solve this, even with exclusions, then I'll have to make a choice between SCEP and MBAM.....
  2. Another quick update. We have been migrating computers to a new SCCM server this past week. The new server did not have the exclusions in place, and the freezing problems started backup with computers that were migrated to the new servers. They weren't the complete freezes from before, but more random periodic freezes that lasted a few minutes then went away for a while but eventually returned. So there are still some issues with the current security definitions or versions of both programs. I've now added the exclusions to the new SCCM server and forced all the clients to check-in for the updated policy, so hopefully this resolves this issue for now and I can get back to my more important year-end projects.
  3. We seem to periodically be having issues with a few stubborn machines, even with the exclusions in place, and it sounds like this could be the issue, but it's difficult to pin down, because if that were the case you would think it would affect everyone with the same configuration and it doesn't. It seems to just randomly choose who to affect. We're a small department, managing over 600 users, and of course have too many other projects that I haven't been able to give this my full attention, especially since it's just an occasional computer or user now. I'll try to get the screen shots requested above and more details regarding versions, etc. when I have some time. Until then I'm hoping someone else solves this permanently.
  4. This is interesting as we were still having problems on computers that had the definition update. I wonder if there was more to it, and once you had the problem getting the updated definition was not sufficient to solve the issue. I still haven't had time to test the scheduled scanning issue. For now, scheduled scans are disabled in malwarebytes, and we have quit having reports of problems (with the exclusions in place).
  5. As an update, I haven't had time to troubleshoot the scheduled scan still causing the computers to freeze, but I had one remote user who was having freezing issues and discovered a few things on investigation. 1. He had a stand-alone version of Malwarebytes installed, probably an older version, but I didn't note the version. What I did notice was that the program files directory did not have the ' in the path name for the Malwarebytes directory. So it wasn't honoring the exclusions set. 2. I completely uninstalled Malwarebytes, but the computer continued to have issues with random freezing. I had to remove and reinstall system center endpoint protection to completely fix the issue with freezing. As he was a remote user I did not reinstall Malwarebytes, we'll do that after I get to the bottom of the issue with scheduled scans causing the computer to freeze.
  6. I hadn't thought about that. I need to see what processes are starting up with the scheduled scans and make sure they are excluded in MSE. Now some more research to go do.
  7. Right. I have the exclusions entered for it. It's just the scheduled scans in Malwarebytes that are still causing issues. As soon as the scan kicks off the computer freezes. The rest of the time it works fine.
  8. For us, we are using the Malwarebytes enterprise console and Microsoft System Center Endpoint protection. Neither is running as a stand alone product. Perhaps that is the difference. We are also running Malwarebytes Anti-Exploit, which you can't really add exclusions to in the same way, but I don't think anti-exploit is the issue.
  9. For us, with real-time protection on in both we are not having issues (with the exclusions for each in place in the opposite product. However we still have an issue when the scheduled sans go off in Malwarebytes that slows things down/freezes the computers. We've disabled the scheduled scans for now until we find a solution.
  10. I'm fairly certain I have all the exceptions entered with the correct short form now. we didn't figure it out until reading the prior posts, but our lockups were occurring at the 12:00 malwarebytes scheduled scans too. I pushed the updated policy out, but with the holiday and so many leaving early I think it only got to about 50 percent of the computers. everyone should get the policy Monday morning.
  11. Our problem is we have 400+ machines. managed through system center, which won't allow us to paste in the whole list at once and doesn't allow 's in the process name. I've updated the short names with the correct ~numbers, hoping this works so I don't have to manually update 400 computers.
  12. Is anyone else still having issues with this? We entered the exclusions in system center, both processes and files, and have the most recent definitions from Microsoft. We thought we had solved everything yesterday afternoon, however today some computers are back to freezing again, and disabling Malwarebytes solves the issue.
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.