Jump to content

PhillyPhotog

Members
  • Content Count

    22
  • Joined

  • Last visited

Community Reputation

0 Neutral

About PhillyPhotog

  • Rank
    New Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @vs2015sv, see the link in my previous post. You likely need to manually define the location of a windows install file (specifically the sxs). You can find this by grabbing any Genuine Windows install CD or ISO.
  2. Not sure what sparked the new conversation here, but I wrote up a brief synopsis on how to overcome this here: http://weisswesley.com/deploying-malwarebytes-on-windows-8-8-1-10-using-group-policy-software-deployment-or-other-3rd-party-deployment-tools/
  3. Thanks for the response @AdvancedSetup. I should have been a bit more detailed in my post. This is what I am seeing Client Group A (~2% clients) Database Version 2016.11.17.15 Anti Malware Version 1.80.2.1012 Managed Client Version 1.7.0.3208 Client Group B (~96% clients) Database Version 2016.11.17.15 Anti Malware Version 1.80.1.1011 Managed Client Version 1.6.1.2897 Client Group C (~2% clients) Database Version 2016.11.17.15 Anti Malware Version 1.75.0.1300 Managed Client Version 1.4.1.2329 Is there an integrated upgrade
  4. Not sure what the implications are, 98% of my clients are running the most recent Anti-Malware Version and relatively recent Database Versions, but I have a notable number of clients (which have recent anti-malware and database versions) which are running older version of the Managed Client. It has been over 2-3 months since we upgraded the Management Console to the latest release (1.7.0.3208) My questions: Does the installed version of the management client have any impact on the speed of updates or effectiveness of the scanning engine? (any impact to the safety of my clients)
  5. Submitted. What is the upper limit for embedded? At what point does MB recommend that a deployment team consider utilizing SQL for database rather than embedded (# of clients, record length, etc.)
  6. Embeded, sorry for delay, did not see the reply. Error went away for a bit, but just popped again.
  7. Performing an audit of the installs on our network of MBAM, and noticing a variation between services that are installed / not installed, running / not running. Searching the forums did not shine any light on the different services that Malwarebytes Enterprise relies on, what they do, if they should always be running, if they should always be installed, etc. The services that I have discovered are: MBAMService, MBAMScheduler, and MEEClientService
  8. More information on this. I disabled the cleanup settings for Obselete logs / clients. This allowed the management service to stay alive and collect data from clients. I have been running manual cleanups for the past day, and the log keeps getting a bit smaller (as reported by console, but not realized in app_data folder in MBMC install path), but still fails eventually and kills the service.
  9. Correction, Database now shows as .54 GB in MBMC, but when looking @ app_Data folder in Malwarebytes Management Server folder, scdb shows as .978 GB and SCDB_Log shows as 2.1 GB
  10. Interesting note, began a database cleanup and the service just crashed on me. Server had just been rebooted about 45 minutes prior... Database corrupt? How can I confirm / rebuild? I have been able to repeat this and get the same result. Database size is currently .9 GB. Too large?
  11. My management console is failing after about 24 hours of uptime. Specifically, I am getting an error with ID 7034 from source Service Control Manager Eventlog Provider, with the detial I am running Management Console version 1.7.0.3208 I am not sure where to begin troubleshooting this one. Search of forums came up blank for me. Any guidance would be appreciated.
  12. Ron, Thanks for the reply. I did submit a ticket (00015829) via the site form, but the technician assigned to the ticket did not satisfactorily address the question posed. The first response just told me to enable 3.5 manually. When I restated a need to deploy via GPO, I received a reply saying that GPO pushes are possible (they aren't, without the manual enabling of 3.5) and that console deployment requires 3.5. Unsure if I was missing something, I replied back indicating that I was not sure I was following, and attempted to restate what I though was communicated, hoping that there
  13. Does anyone from MalwareBytes have any feedback regarding improving Windows 8, 8.1, and 10 compatibility so that this tool can be more consistently implemented in updated environments?
  14. All of our clients appear to be 2 hours behind in updates throughout the day on a consistent basis. Of the 600 managed, the reporting interface shows <10 as on the most current release at any time. When manual updates are triggered on clients (from client desktop), client shows that it is on an older than most currently available definition, but reports that it is up to date (and does not download the most current definition. Are there any guides to troubleshooting Update Lag / Update Issues
  15. For some reason a bunch of my posts were taken out of their respective topics and mushed into one kind of related topic, so I am reposting, with the specific questions that need to be addressed. Currently, any attempt to deploy to stock installs of Windows 8, Windows 8.1, and Windows 10 fail, whether the Malwarebytes management console is used, or the MSI package created using the console is deployed via other means (I have tried PDQ Deploy and Group Policy Software Installation). The root cause of this issue is a reliance on .NET 3.5, which is not activated by default on Windows 8+, and
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.