LogoLogo
  • Introducing dope.swg
    • Changing the Rules...
    • Quick Start Guide
      • Create a dope.swg Account
      • Get Started with the dope.endpoint
      • Import User and Group Data
      • Create a dope.swg Web Policy
    • Mitre ATT&CK and Nist CSF
  • dope.console
    • Analytics
      • Overview dashboard
      • Policy View
      • Productivity
      • Shadow IT
      • Detail View
    • dope.swg Policy
      • Editing the Base Policy
      • Adding Policy Exceptions
      • Assigning a Block Page
      • Creating Custom Categories
      • URL Bypass List
      • Application Bypass List
      • Default Bypass List
      • Cloud Application Control (CAC)
        • Microsoft O365
        • Google
        • Box
        • Salesforce
        • Dropbox
        • Slack
        • WebEx
      • Custom Policy
      • Policy Assignment
      • Policy Inheritance and Customization
    • CASB Neural
      • Microsoft 365 - Authentication
      • Google - Authentication
      • CASB DLP
        • DLP Files Table
    • Endpoint Manager View
      • Searching the View
      • Filtering and Sorting the Endpoint View
      • Endpoint Count
      • Running Diagnostics
      • Disable Endpoint
    • Settings
      • General
      • Block Pages
      • Endpoints
      • Users
        • Importing from Google
        • Why not SAML & SCIM?
      • Audit Log
      • SIEM Integration
        • Category & Verdict Mappings
      • API Client Credentials
      • Billing Details
    • Notifications
      • SSL Errors
  • dope.endpoint
    • Trusted Process Names
    • Generate Diagnostics
    • Disable Endpoint
    • Installing using MDM on Mac
      • Using JAMF
      • Using Kandji
      • Using Intune
    • Installing using Intune on Win
    • Mac Installer
      • Installation Process - Silent
      • Uninstall
      • Endpoint Authentication
    • Windows Installer
      • Installation Process - Silent
      • Uninstall
      • Endpoint Authentication
    • dope.endpoint UI
      • Windows UI
      • macOS UI
    • Automatic Updates
  • Release Notes
  • DOPE.APIs
    • Public API Specification
Powered by GitBook
On this page
  • 1. Upload the MobileConfig File
  • 2. Deploy profile to devices
  • 3. Upload the application pkg zip
  1. dope.endpoint
  2. Installing using MDM on Mac

Using Kandji

PreviousUsing JAMFNextUsing Intune

Last updated 1 month ago

Kandji allows you to do a managed device deployment with a Kandji blueprint. Kandji (or any MDM) eliminates manual steps on Mac to trust the Certificate and accept permissions for our system extension.

There are two primary components:

  1. MDM Profile: this is the config profile that contains the certificate, extension, VPN, and privacy permission to ensure the user will never see a pop-up. Otherwise, there will be manual interaction for accepting/authorizing the installation (due to Apple security policies)

  2. : this is where you upload the full zip to Kandji to deploy to your devices - same steps as any managed deployment (upload the install zip as-is). Once distributed, Kandji will run the installer

1. Upload the MobileConfig File

You can retrieve the MDM profile's XML and directly upload it to Kandji. This will contain all requisite permissions at once, including:

  1. Root Certificate - for trusting the on-device SSL inspection

  2. Network Extension Permission - for re-routing traffic to the on-device proxy

  3. VPN Permission - for re-routing traffic to the on-device proxy

  4. Privacy Preferences Permission - for anti-tampering

You will need to add the XML to a .mobileconfig file, and upload it to Kandji as show below.

2. Deploy profile to devices

Add the custom profile to the blueprints you are going to install the endpoint on. We always recommend to deploy the profile prior to installing the software to ensure there are no user pop-ups.

3. Upload the application pkg zip

Add a new custom app into your library with the Mac package downloaded from your dope.console:

You can add the Blueprints that the application will be deployed to here, and select either:

  • Install once per device: This option will install the software only

After the library item has been setup, you will be able to deploy this to all of your devices quickly. You may opt to do a small test deployment, but we have seen admins deploy thousands of healthy installs in minutes.

Audit & Enforce: This will use a to ensure the software remains installed (best practice, although the software is built to prevent removal)

script
Custom App Deployment
here
Add a custom profile using Kandji library items
After uploading the mobileconfig file
You can directly upload the zip here
Upload the zip, extract to /tmp or your preferred directory, and add in the installer command