DriveStrike Linux Mass Deployment Guide

 

DriveStrike can be deployed by IT administrators via mass deployment mechanisms. This document details the steps required to deploy DriveStrike via these mechanisms for Linux devices. If you are looking for instructions for mass deployment on Windows please go here.

Step 1: Obtain a mass deployment token

Since mass deploying DriveStrike has the potential to impact a large number of devices, we currently require IT administrators to call the DriveStrike support line to authorize mass deployments on their accounts. This process is very simple, and can be completed in just a few minutes.

When mass deployments have been enabled on your account, your DriveStrike support agent will provide you with a mass deployment token (an alphanumeric string). It is important to safeguard this token, since anyone who has this token can register an unlimited number of machines on your DriveStrike account.

The mass deployment token will not expire, so you can use it to deploy DriveStrike to machines in the future as well. If you ever find that this token has become compromised, please contact DriveStrike support to obtain a new token and invalidate the old one.

Step 2: Configure your deployment mechanism

You will need to perform the steps listed below on each machine. You can of course execute these commands remotely via SSH or some other remote-access mechanism.

On Ubuntu-based distributions, you’ll need to first add the DriveStrike repository key to apt (this step isn’t necessary for distributions which use the yum package manager):

wget https://app.drivestrike.com/static/drivestrike.pubkey.txt

sudo apt-key add drivestrike.pubkey.txt

 

Next, add the DriveStrike repository to your package manager’s list of package sources:

# Ubuntu-based distributions

echo deb [arch=amd64] https://app.drivestrike.com/static/apt/ stretch main \

| sudo tee /etc/apt/sources.list.d/drivestrike.list

sudo apt-get update

 

# Red Hat-based distributions

# Install yum-utils, to get yum-config-manager

sudo yum install -y yum-utils

# Add the DriveStrike repository

sudo yum-config-manager –add-repo \

https://app.drivestrike.com/static/yum/drivestrike.repo

 

Now you can install DriveStrike using your package manager:

# Ubuntu-based distributions

sudo apt-get install -y drivestrike

 

# Red Hat-based distributions

sudo yum install -y drivestrike

 

Finally, register the machine using this command, providing values for the “email@example.com” and “massDeployToken” placeholders as appropriate, and then start the DriveStrike service:

# On both Ubuntu- and Red Hat-based systems

sudo drivestrike register email@example.com massDeployToken

sudo systemctl start drivestrike

 

As new versions of DriveStrike are posted, you can upgrade via the package manager as normal:

# Ubuntu-based distributions

sudo apt-get upgrade drivestrike

 

# Red Hat-based distributions

sudo yum update drivestrike

Step 3: Test your deployment

To confirm you have the proper mass deployment token, use a test machine (or VM) and install using the instructions in the sections above. Once the deployment process completes, log into the drivestrike.com website, navigate to the Dashboard page, and confirm that you see the expected device owner, with a device that shows the “Ready” state.

DriveStrike remote wipe dashboard
After you confirm the machine installed correctly, you can uninstall DriveStrike from the machine and delete the device and device owner objects from the DriveStrike website.

Next, you may wish to push the DriveStrike installer to a test machine (or VM) via your preferred application deployment mechanism, to confirm the software delivery channel.

Step 4: Deploy to production machines

When you deploy to production machines, you can always monitor the status of your deployment through the drivestrike.com Dashboard page. Machines to which DriveStrike has been deployed successfully will be visible in the Dashboard and show a status of “Ready.”