Jump to content

knwillis

Members
  • Posts

    7
  • Joined

  • Last visited

Reputation

0 Neutral
  1. Still working with Kaseya support. So far, no resolve.
  2. I've opened a support request with Kaseya directing them to this forum thread. I'll let you know what I find out. Thanks
  3. I just updated the Kaseya agent on my computer to the newest version and ran a quick scan but got the same results from MBAM.
  4. Thanks Sam. The files I posted in the first post actually have two different machines. One computer is running the Kaseya agent with the Kaseya anti-virus (re-branded AVG) and one machine runs the Kaseya agent but not their anti-virus (using MSE instead). The Kaseya agent does not manage any virus scans without that re-branded AVG installed.
  5. Hi Sam, some of the systems I'm running MBAM on do not have Kaseya's endpoint solution. I have some with MSE and some home users with Norton/Symantec. Still getting the same results. Any other ideas?
  6. You are correct on Kaseya! I'll give this a shot and see if it helps us. Thanks for the quick reply!
  7. I've been finding the same group of files all over my company. We have clients all over the state and nearly every machine we scan with MBAM comes up with these results. The files are non-existent on the computers. I've attached the initial quick scan logs for two computers along with the /developer quick scan logs for the same machines. mbam logs.zip
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.