djacobson

The solution is to run a query on the database via SQL Management Studio to free up the association to the older MBMC server. This requires a ticket to be opened with the support team. https://support.malwarebytes.com/community/business/pages/contact-us

MBMC can support in excess of 20k seats. It all depends on your SQL config. There are other limitations with the product that can be impactful to enterprise setups, that's detailed here - Here is a matrix to help you design good policies for your endpoints based on their OS and role.

Hi Steball, please open a ticket with the support team, you are likely having trouble with old FP logs or some other problem that will require a cleanup of the SQL and the archived client info.

Hi Tony, I apologize about that, many of us didn't know until this was added to our guide. For ARW ignores, make sure to be as direct and literal as possible, using the full path the to exe or whole folder. For the machine that has been unable to take up the exclusions, make sure they are on the latest plugin, shows in Programs and Features as Malwarebytes 3.6.1.2716.

Yes, that's right.

Hi @j_french, here are the areas. Select the items for which you want Anti-Malware to look. Tell Anti-Malware what to do with the items it finds, using on-demand scans: Or using the scheduled scans:

Hi guys, changes to the policies within MBMC will be picked up by the clients themselves once they check into the management server. The version number of the policy will iterate, and in your client view, machines which need to check-in to receive the policy change will be highlighted in yellow. Once the highlight goes away, those machine have accepted the new policy and reported back.

Hi @TraptPatriot, MBMC uses port 443 for the admin connection to SQL. Your external SQL is just pointed as fqdn(or IP)\instance, your SQL server should be able to have an alternate port than the Microsoft default if you desire.

Hi @rodbcans, the managed client on here is very old. That version also pairs the legacy Anti-Malware 1.75. What version is your MBMC right now? Malwarebytes' Managed Client (HKLM\...\{D14F4181-275B-4837-9767-3E9E0672A884}) (Version: 1.5.0.2701 - Malwarebytes Corporation)

I forgot if we had to use any wildcards on your setup Tony, but a reminder that wildcard use will render the exclusion un-usable to ARW aka Behavior Protection.

The detection has been released from the signature.

Malwarebytes is scheduled to update our cloud platform on October 18, 2018 at 8:00PM EST / 5:00PM PST. We anticipate less than 3 hours of downtime to complete this update. As a customer of this platform, we want to take a moment to familiarize you with the changes that are about to become available. With this latest update we’re proud to announce that we’ve enhanced administrators’ visibility and interaction throughout the cloud management console, providing additional insight. This makes it even easier for you to immediately respond to alerts and manage events. Malwarebytes Endpoint Protection and Response customers also benefit by seeing the exact behaviors and rule(s) which triggered a cloud sandbox detection. New Features Malwarebytes cloud console now features endpoint status icons in the Manage Endpoints page. This allows administrators to take immediate action by clicking directly on the icons. You can see when an endpoint restart is needed, if remediation is required, or if any suspicious activity is detected on that endpoint (for Malwarebytes Endpoint Protection and Response). Hovering over an icon provides additional info, and clicking on the icon presents specific actions you can take: Endpoint status icons are also displayed when viewing the details of an individually selected endpoint: This is the full list of endpoint status icons: Improvements For Malwarebytes Endpoint Protection and Response only: Updated the Suspicious Activity Details page to display an expanded set of rules triggered when making cloud sandbox detections. This provides administrators with greater context of why a cloud sandbox detection was made on a suspicious file or process: For Malwarebytes Endpoint Protection and Response only: Updated the Process Graph details pane. This allows administrators to click on Activities links and see specific file operation details, including File Rename, File Write, Set Security, Registry Set Value, Net Connect Inbound, and Net Connect Outbound activities: For Malwarebytes Endpoint Protection and Response only: Granular Endpoint Isolation is now supported for Windows Server 2008 R2, Server 2012 R2, and Server 2016 allowing businesses to remotely isolate servers for further investigation For Malwarebytes Endpoint Protection and Response only: Updated the Remove Endpoint Isolation notice to specify the endpoint name Added capability for end users to enable/disable debug logging from the tray icon using ctrl + right click, and via command line Fixed: For Malwarebytes Endpoint Protection and Response only – BSOD with SamSam ramsomware variant on Windows10x86 Fixed: Not cleaning up all temp files in c:\Windows\Temp Fixed: For Malwarebytes Endpoint Protection and Response only – Some suspicious activities viewed in Process Graph returned Error 500 and other general improvements needed Fixed: For Malwarebytes Endpoint Protection for Mac only – Error appearing in logs: ERROR WebServiceStore: remove: request.guid=... Fixed: For Malwarebytes Endpoint Protection and Response only – Yes button in the dialog box for Lock icon status indicator doesn’t work Fixed: For Malwarebytes Endpoint Protection for Mac only – Endpoint Agent does not report update_package_version on fresh Endpoint Protection install Known Issues Exclusions that have been entered with short file name paths such as “c:\progra~2\” are not being applied Modal windows are showing an unnecessary scroll bar For Malwarebytes Endpoint Protection and Response only: When a Remediation action succeeds but Rollback action fails, the Suspicious Activity status is stuck and displays “Pending Remediation” For Malwarebytes Endpoint Protection for Mac only: Scan History tab does not get information populated if Threat Scan does not detect any threats For Malwarebytes Endpoint Protection for Mac only: Timestamps in Scan History tab for macOS endpoints are in GMT, and not the web browser’s locale All Malwarebytes scans will inspect archived files regardless of the policy setting In some cases, when a reboot prompt is shown, the reboot timer may reset with a 1-minute countdown When administrators reboot endpoints from the cloud console, if the initial reboot task has not completed subsequent reboot commands are queued rather than replacing the initial reboot command (this would result in multiple reboots executing) When administrator chooses “Restart Immediately” option in the Restart Options dialog, end users are still allowed to postpone the reboot even though the “Allow user to postpone” option is grayed out. Current workaround involves selecting the “Restart in ___ minutes” radio button, unchecking the “Allow user to postpone” checkbox, then select the “Restart Immediately” radio button and click the blue Restart button Clicking on the Remediate button causes the Remediation Required indicator to lose its badge on hover and on click behavior— nothing happens on click (should give you the option to view details) and nothing happens on hover (should show "Remediation Pending"). This issue is resolved by refreshing the browser Memory and storage objects in endpoint properties are not visible until the page is refreshed Our next cloud platform update is scheduled for November 2018.

Try using an asset scan instead. If it still shows the older one, it could be that it has not yet installed it, the update is currently metered. If you'd like to hurry it along, a reinstall will have it pull the newest plugin

Please zip them into an archive and give the archive a password, 'infected' is what we usually use. Send via PM.

You will see "Malwarebytes 3.6.1.2716" in add/remove programs and under the Software tab in the cloud portal.