Skip to main content

Migrate from Malwarebytes for Teams to Nebula

This article walks you through how to transition from Malwarebytes for Teams to Nebula.

Malwarebytes for Teams is a solution for small businesses to protect and manage their devices. It includes protection for Windows, Mac and Android devices. The app is installed and managed independently on each device.

Growing businesses can take advantage of Nebula to remotely and efficiently manage the protection of endpoints through a cloud-based management console. Our Nebula products protect Windows and Mac workstations, and Windows and Linux servers. For more information on our cloud-based Business products, go to Malwarebytes for Business.  

Further technical information on the Nebula features and functions is available in the Malwarebytes Nebula Administrator Guide.

Follow these steps to migrate from Malwarebytes for Teams to Nebula.

Step 1: Requirements

Verify your environment and endpoints meet the following requirements: 

Step 2: Pre-deployment 

Before deploying with Nebula, you must complete certain actions and configuration steps.

1. Log in to Nebula

Before deploying with Nebula, you must set up your account and log in. During the Nebula subscription purchase process, you define the email address for the user that is the Account Owner. This user has specific permissions and needs to login to Nebula to invite other users, or initiate the configuration and deployment processes. For more information, see First login to Malwarebytes Nebula. 

2. Review and compile Malwarebytes for Teams settings 

If you have multiple devices, check each Malwarebytes for Teams device individually to track differences and similarities in settings. This will help organize your endpoints by Groups and create Policies that define the settings for those groups in Nebula. Skip this step if individual device settings are unimportant. 

Review the information about the relevant settings below.

2.1 Allow list/Exclusions

Exclusions in For Teams and Nebula enable you to add items that you know and trust to the Allow list, to prevent them from being detected and quarantined as malicious. If you have Exclusion settings you would like to migrate from For Teams to Nebula, go to your devices and record the existing Exclusions, to add them to Nebula before deployment. 

2.2 Device Alerts and Reports

Malwarebytes for Teams offers Device Alerts and monthly reports to provide insight into your devices without having to review each one. To receive this information from Nebula, generate an Endpoints Summary report or Weekly Security Report. For more information, see Configure reports in Malwarebytes Nebula. 

2.3 Scheduled scans

If you have scans scheduled to run at specific times that enable the most efficient use of your devices, check and record the existing schedules on your devices, to set similar Scheduled scans in Nebula. 

2.4 Tamper Protection 

Tamper protection in For Teams and Nebula prevents unauthorized access and changes to the Malwarebytes application by requiring a separate password or further locking down the application. 

In Nebula, an uninstall password is generated by default and is only required when removing the application from the endpoint locally. If you had this setting enabled in Teams, see how to Configure Tamper protection in Nebula. 

2.5 Brute force protection 

A brute force attack happens when hackers try to connect to your computer using Remote Desktop Protocol (RDP) and guess your password. Brute Force Protection in For Teams and Nebula monitors RDP for these attacks.  

Note: Available in Nebula for Windows endpoints only

If this setting is enabled in Malwarebytes for Teams, see how to Configure Brute Force Protection in Malwarebytes Nebula. 

3. Configure Nebula

Once you have access to Nebula, you can invite other users to start configuration, deploy and manage the devices or endpoints, or start the configuration process yourself.  

Use the settings information you compiled from your For Teams set up, or start fresh with Nebula. For more information about Nebula settings and configuration, see the Malwarebytes Nebula Administrator Guide.   

Step 3: Deployment

To deploy the Malwarebytes endpoint agent to Windows and Mac endpoints:

Windows

  1. Uninstall Malwarebytes for Teams from your endpoints.
    Note: Click No when asked if you want to reinstall.
  2. Log in to Malwarebytes Nebula. 
  3. Deploy the Malwarebytes endpoint agent to your endpoints.

Mac

  1. Uninstall Malwarebytes for Teams from your endpoints. 
    Note: Click No when asked if you want to reinstall.
  2. Log in to Malwarebytes Nebula. 
  3. Deploy the Malwarebytes endpoint agent to your endpoints. 

Linux

  1. Log in to Malwarebytes Nebula.
  2. Deploy the Malwarebytes endpoint agent to your endpoints.

 

Related articles