Introduction
It is possible to deploy and manage LucidLink installation on macOS via an MDM solution. In this guide we will look at the steps necessary to achieve this in Kandji. The deployment workflow is simplified compared with LucidLink Classic since LucidLink is KEXT-less.
For an end-to-end zero-touch user workflow the following requirements must be met:
- The Mac is enrolled in your instance by any method
Workflow Overview
- Create a Custom App and upload the LucidLink .pkg
- Mac installs via Self-Service or automatically via a Blueprint
Custom App Setup
- Navigate to Library > Add New > Custom App > Add & Configure
- Complete the following items:
- Custom App Name: LucidLink
- Give the Custom App an Assignment of one or many Blueprints.
- Execution Frequency: Specify if Kandji should attempt to install this package once per device, or have the package enforced. This is your decision.
- Choose Package Type: Choose Installer Package
-
Upload Installer: Attach the LucidLink .pkg here
Once this is deployed to the Mac via a Blueprint or Self Service, the LucidLink .pkg will install silently. LucidLink will automatically open after installation and does not require a system restart or any user interaction to operate.
FAQs
Q. Does LucidLink rely on a KEXT and approval?
A. No, LucidLink is KEXT-less and also does not rely on System Extensions.
Q. Is a system restart required after installation or update of LucidLink?
A. No, LucidLink can be installed and immediately used with no system restart.
References
Kandji documentation
Custom Apps: https://support.kandji.io/support/solutions/articles/72000559807-adding-custom-apps-to-your-library
Kandji KB: https://support.kandji.io/support/solutions