In order to leverage the power of Kolide, you'll need to get some devices enrolled. Here are some suggestions based on a few common IT environments. For the sake of simplicity, we're going to be focusing on macOS in this article, however Windows and Linux are also supported. If there's something we don't cover here, or you have follow-up questions, click on the Intercom button below and start chatting with our team.
Deploying with the Kolide Slack app is the easiest way to get your team started. https://k2.kolide.com/1/onboarding
Here is a sample of what your users will see:
From here, they can select their launcher package and download it right from Slack!
The best way to deploy the Launcher if your team does not use Slack is by downloading and installing the package directly from the Downloads page. You can reach the Downloads page by clicking your Account avatar and navigating to Settings:
From here click on the Downloads item in the Sidebar:
Click on the download link for the OS of the device you want to enroll, the download will start automatically.
Now that you have the package downloaded, you can:
- Upload it to a local file server and share the location
- Upload it to a sync & share service (Dropbox, Google Drive, etc.) and share a link
- Upload the installer as an attachment into your organization's Slack.
- Put it on a USB drive and manually install on individual Macs
- Deploy it en masse with Apple Remote Desktop
All of the above options require some degree of manual interaction from you as the admin. That's ok for smaller fleets, but doesn't necessarily scale well.
If you manage a larger fleet, chances are you are using a device management tool, such as jamf or Munki, to automate your software installs. Each will have its own way of handling deployments, and we'll try to highlight a couple here (for the sake of simplicity, we will reference existing documentation where appropriate).
For those using jamf Pro: they have detailed documentation on how to upload and manage packages. In addition, you can find an excellent how-to video on deploying the package via policy here.
For Munki admins: because Munki is an open source project, you'll find a lot of community support resources, as well as differing opinions on how best to proceed. The official wiki can be found on Github. There is also an active Munki user and contributor community in the MacAdmins Slack.
Deploying via Fleetsmith: Fleetsmith does not currently support uploading custom packages. Because your Launcher is unique to your Kolide instance, that poses a problem. The solution - script it! Fleetsmith has the ability to deploy custom bash scripts to your macs, as described in this blog post. To deploy Kolide this way, you will need to:
- Upload a copy of your launcher.pkg to a secure but publicly available location. Note - as of this writing this does not work with Google Drive, your mileage may vary.
- In Fleetsmith, select Apps & Settings > Custom Bash Script (Run Once), select or create a profile to which to add it (I'd suggest Global if you are enrolling your entire fleet), and paste in your script (example below).
This example places the package in
/tmp so that the it will be deleted on the next restart. You can choose to download the package to a different location, however you may want to update the script to delete it upon completion.
Deploying via MDM: If you are using an MDM platform that offers custom .pkg uploads, such as jamfNOW or SimpleMDM , you will need to take an additional step before deploying. Following the steps outlined here, you will need to pass the launcher.pkg to
productbuild , which will make it ready to distribute. Additional reading is available on both the jamf and SimpleMDM websites.