djacobson

Brad, can you PM me the URL you are trying and screenshot how you have them set in your list?

The MBEP business version's protection software is based on the consumer MB3 technology, but highly modified to be controlled by your cloud portal.

MBAMservice is all your protection items, the scan engine, the realtime for malicious file, web, ransomware and exploit. If it is removed, MBCloudEA will have nothing to control.

Malwarebytes Endpoint Agent, MBEndpointAgent, "C:\Program Files\Malwarebytes Endpoint Agent\MBCloudEA.exe", is your communication service to your cloud portal. Malwarebytes Service, MBAMService, "C:\Program Files\Malwarebytes\Anti-Malware\mbamservice.exe", is your protection software. They are both vital. "C:\ProgramData\Malwarebytes\MBAMService\config\UpdateControllerConfig.json" is the correct place to get your database package version and date, but also your controller and program versions.

Emails already used for cloud accounts cannot be used again. They become tied to the original account.

@WORKS2016 we backup the changes to our cloud storage, it does not rely on any 3rd party tools to rollback.

@Heinrich May I see the msi log? Just in case, there are some things to be aware of; the file must copied to the machine and ran from a local drive, running it from a network location will not work. Anti-Malware and Anti-Exploit are part of the Malwarebytes Managed Client entry shown in Programs and Features, though later on Anti-Exploit can and will auto-update (if allowed in policy), and create a separate entry for itself in Programs and Features. Anti-Malware will not create an entry for itself and will remain under Malwarebytes Managed Client.

Moving thread to correct section. Dcollins was thinking this was the EP product at first, like Kalrand initially thought. The tactics they provided are true for the cloud based solution and its installers. With the server based on-premises solution, that uses MBMC, Malwarebytes Management Console, it can create an offline EXE and MSI for manual or 3rd party deployment, however the EXE one is not able to use any switches.

Hi @Heinrich, please use the MSI, the EXE installation package does not support any switches. Use something like this: MSIEXEC /a C:\[path to]\[setupfile].msi /qn Or if you want to log the install, use something like this: MSIEXEC /a C:\[path to]\[setupfile].msi /qn /lv %userprofile%\desktop\mbamInstallLog.txt

Malwarebytes cloud platform update - September 13, 2018 Malwarebytes is scheduled to update our cloud platform on September 13, 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. New Features None Improvements For Malwarebytes Endpoint Protection and Response only - Added granular Endpoint Isolation options, enabling administrators to specify one or more isolation methods to be applied to the selected endpoint. By default, all three isolation types will be selected: Added Malwarebytes AdwCleaner for use and download from the “Add Endpoints” page within the cloud console. Please note this is an unmanaged solution: Added capability to use shift key + mouse click to select ranges of items for tables that allow batch actions. Updated Malwarebytes tray icon so that end users who are permitted by policy to initiate scans can bring their minimized scan progress window back into focus by simply double-clicking on the Malwarebytes tray icon. Changed the Malwarebytes Self-Protection Module so it’s enabled bydefault for all new customer accounts. This setting controls whether Malwarebytes creates a safe zone to prevent malicious manipulation of the program and its components. Enabling this setting introduces a one- time delay as the Self-Protection Module is enabled. While not a negative, the delay may be considered undesirable by some end users. We strongly recommend existing customers enable this setting in their security policies. Added a loading spinner animation while paginating through large sets of data. Removed Anti-Exploit shield from Chrome due to Google’s new policyagainst code injection into Chrome. Extended the timeout toggle for “Remote Assistance” to 4 hours. Updated Syslog Communication feature so that the designated endpoint cannot be uninstalled using the Deployment & Discovery tool unless it’s first unselected within the Syslog Communication setting. This prevents administrators from inadvertently losing syslog messages. Before removing an endpoint, Malwarebytes cloud administrators will need to first disable Syslog Communication in the console or promote a different endpoint Fixed: Malwarebytes Single Sign-On settings page styling and page scroll. Fixed: Read Only users can log into the Deployment & Discovery tool. Fixed: Could not edit a user’s email address if the user account has not been verified. Fixed: After Endpoint Agent upgrades, some .zip files under ...\windows\temp are not deleted. Fixed: Filter options on the Endpoints and Detections pages are sometimes cut off abruptly. Fixed: For Malwarebytes Endpoint Protection and Response only - Several bugs were impacting administrator’s experience interacting with the Process Graph feature. Fixed: For Malwarebytes Endpoint Protection and Response only – Reset the network adapter on the endpoint to enforce network isolation. Fixed: For Mac endpoints, the “Check for Protection Update” action does not update the “Last Refreshed” attribute on first run. Fixed: Endpoints could not be moved to a different group when selected using the “Select All” checkbox. Fixed: Windows Server 2008 scans can crash when scanning .lmk files. Fixed: User Verified account notifications are not getting emailed to administrators. Fixed: Within the Endpoint Properties page under the Detections tab, the Action Taken and Category dropdowns are cut off. Fixed: For Malwarebytes Endpoint Protection for Mac only - Scans are occurring every hour, regardless of what the scheduled scan interval is set to. 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. For Malwarebytes Endpoint Protection for Mac only - Endpoint Agent does not report update_package_version on fresh Endpoint Protection install.

@SivajiGanesh were you able to get past the SQL issue?

Hi @j_french, are you selecting remove threats found in your scan option for on-demand and scheduled scans in addition to the scanner options of what to look for? You may also be facing something that is only live in that particular user's profile and not from the system account that would normally run the scans you send from MBMC. Browser items commonly do this.

MBMC does not have the ability to show when releases are done, it is unfortunately a manual process for this. You can compare version numbers between your console in the bottom corner and the version listed on the MBMC installer you've downloaded, or you can use the release history page here to compare - https://www.malwarebytes.com/support/releasehistory/business/#mbmc2 The package number on the zip changes whenever something within it changes, most commonly Anti-Exploit's build version, which updates very often since it is a signature-less program.

Which product version is installed on their machine? The Control Panel \ Programs and Features areas hold list the version numbers. I suspect the build in use is incorrect for the license type.

To chime in on what exile360 said, finding out which realtime engine is responsible for the behavior you are seeing helps narrow down the troubleshooting process. We don't want you to have this portion of the realtime disabled indefinitely.