Endpoint Agent Setup for Windows Assistance Needed

[mjolly803]

It appears the Endpoint Agent Setup installer is capable of detecting the OS flavor (workstation vs server) on run. Is there a way to force the installer to install the workstation version of the Endpoint Agent via command line or some other method? Even though the Nebula portal has different options under Endpoint Installers in the Downloads section for Windows and Windows Server. They appear to be the same installer in running them and the hash values shown. We have a need to install the workstation version of the Endpoint Agent no matter the Windows OD flavor.

Thanks!

[Porthos]

I would highly suggest that you open a support ticket with Business Support to work with them directly.

Submit Support Ticket

It can take a few days for a response as ticket volume is high at this time.

[mjolly803]

I'm doing that as well, but I know they are slow right now so was posting here to see if users potentially had a faster answer for me. Appreciate the feedback though!

[AlexSmith]

Hi @mjolly803 and great questions!! Oddly enough, you sort of already answered it yourself, but let me confirm and expand on it.

The Malwarebytes Endpoint Agent and the Malwarebytes software component plugins are the same for Windows and Windows Server. Endpoints that are running Windows Server (and properly licensed for Server support) will have access to unique Policy settings/configurations for Windows Server. Policy settings are managed from the Malwarebytes Nebula and/or OneView consoles.

Let me know if oyu have any additional questions.

[mjolly803]

Thanks for the reply @AlexSmith.

My follow up based on your response is what is the determination of "properly licensed for Server support"? The reason I'm trying to determine all this is our environment includes quite a few virtual machines that run Windows Server as the OS, but they stay off a large majority of the time. We of course want them protected when they are on, but its hard to justify the cost of an Endpoint Protection server license for those instances. We want to license those endpoints with Endpoint Protection workstation licenses, knowing that doing so may mean some loss of functionality on those endpoints (in the sale process we were told using workstation license on Windows Server would mean loss of real-time scanning, but scheduled/manual scanning is possble). Is that possible and if so how do we make sure the endpoints we want licensed as workstation or server are configured that way?

Thanks!

[AlexSmith]

@mjolly803 Sorry for the delay in a follow up. Properly licensed for Server support would mean having a license that includes seats for Endpoint Protection/Endpoint Detection & Response for Servers.

When the Malwarebytes Endpoint Agent performs license validation and redemption on a Server OS, it will redeem against the seats for Endpoint Protection/Endpoint Detection & Response for Servers. This in turn means that Windows Server endpoint would now be able to use Server specific capabilities which are configured via the Policy settings in the Nebula/OneView management consoles.

Some of the unique settings/configurations for Windows Server include Brute Force Protection for Server Protocols and Suspicious Activity Monitoring for Servers (EDR Only).  For more details on settings and Policies, check our user guide here: https://support.malwarebytes.com/hc/en-us/articles/360039985913-Malwarebytes-Nebula-Administrator-Guide

Unfortunately, I cannot provide much additional guidance on using a non-Server license on a Windows Server endpoint as that would go against our current licensing.

Edited July 28, 2021 by AlexSmith

[mjolly803]

@AlexSmith Understood. Unfortunately that is not what we were told when asking questions ahead of purchase and that incorrect response is what influenced out decision to make the purchase. We will work back through that channel to get a resolution to this issue. Thank you for your assistance and the information.