Jump to content

therealjoshuad

Members
  • Posts

    7
  • Joined

  • Last visited

Reputation

0 Neutral

Profile Information

  • Location
    Louisiana
  1. We use the MSI as part of our task sequence in SCCM and it works beautifully. To OP: Create a Package with the Client Setup MSI in the source location, and create a program with the following install command: msiexec /i "clientSetup.msi" /qn and add it in the state restore phase when you install all of your other applications. The MSI can be generated in the MalwareBytes Management console by going to the Policy Tab. Select a policy to generate the msi from, and at the bottom of the Console, click the Installation Package button. Fill in the save directory, and what group to put the client that uses the package in, and then select the Create a MSI file option. Feel free to ping me if you're having trouble creating the package @therealjoshuad
  2. I strongly agree with #2, #4, and #5. As for number 2, a workaround is to create a text file with the single hostname or ip address, or a small group of hostnames, one on each line, and then you can select that to scan, and it will only scan the single, or small group that you want.
  3. I've had a similar issue. It could be due to a few things. The short of it, is to uninstall the client from the local computer, and push it out via the Management Console again. In my case, it was that the "Managed Client Version" was older than the "Client Version". The managed client version is the component that talks to the MEE server. So while the client (The user application), can be up to date, the Managed Client Version can be out of date. As of now, it looks like the current version is 1.3.1.1962, you can verify that particular computer's managed client version in the console, by enabling the "Managed Client Version" column in the console client view. You can add and remove columns in the Client view by right clicking one of the columns, and click customize columns.
  4. Thank you, I assume it wouldn't be that difficult to have it added in, as it's an MSI installer wrapped with the .dat file with the server address in it. I tried installing it with just the MSI, but it doesn't seem to accept the way I was passing the parameters for silent and to point to the .dat file.
  5. Anyone get the Management Console for MEE with a silent installer? I have the exe for the console, but I'd like to deploy the management console to our techs with System Center Config Manager silently.
  6. Microsoft Active Directory integration, capable of querying AD to import admin users, computers, groups, and organizational units" (How can I only scan the built in "Computers" in AD (It's technically not an OU and doesn't show up in the tree in MEE) Expedited deployment of Malwarebytes managed clients based on membership in Active Directory groups (Couldn't find this feature) Set a Domain Query Account to synchronize Active Directory changes (Could not find this feature) Automatic configuration of managed client polling intervals based on the number of clients (I did not see this in the documentation) Policy option added which allows managed clients to download signatures directly from the internet (Will the version still be able to be tracked and updated if needed via the management console?)
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.