Use a generic installer
The endpoint agent installer in the Nebula console contains an account token, which links an endpoint to a specific account. If you manage multiple Nebula accounts, you may prefer to use a generic installer.
A generic installer is the latest installer binary without an account token embedded. Using a command line script, the account token can be applied during or after installation. If an account token is not supplied, the endpoint will not register to a Nebula console and the machine will be unprotected.
Generic Nebula public installers
Download a generic endpoint installer from the public download link: https://ark.mwbsys.com/epa.mac.installer/release
Locating account token
To locate the account token for your Nebula account:
- Log in to Nebula.
- On the left navigation menu, go to Download Center > Advanced tools.
- Click Specify group assignment.
- Locate the command line for the macOS installer.
- The account token appears in the macOS pkg file name
Setup.MBEndpointAgent__xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx___.pkg
Assign account token during installation
Run the command line script to apply a specific account token to the installer:
xattr -w ACCOUNTTOKEN xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx MBBRNebulaAgent.pkg;sudo -E /usr/sbin/installer -pkg MBBRNebulaAgent.pkg -target /
CAUTION - A valid account token must be supplied, or endpoint registration fails.
Assign account token after installation
If the generic endpoint agent installer was executed without an account token, run the command line script to set the account token:
SUDO '/Library/Application Support/Malwarebytes/Malwarebytes Endpoint Agent/EndpointAgentDaemon.app/Contents/MacOS/EndpointAgentDaemon' AccountToken=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx
SUDO launchctl stop com.malwarebytes.agent.daemon
SUDO launchctl start 'com.malwarebytes.agent.daemon