Deploying macOS Roaming Client via Meraki MDM
Hello!
Anyone else confused or having an issues with deploying the host installer via Meraki MDM or something similar to macOS devices?
Kind of confused with steps 4 and 5 (using https://help.dnsfilter.com/hc/en-us/articles/41062760716307-Install-macOS-Roaming-Client-v2-2-0-or-higher for reference).
My understanding is that you take the provided URL (standard agent in my case) insert it into the script (where the download URL is, within the “”) and do the same with your site key, then run the script to the target machine(s). Is that correct?
Or do you deploy the host installer to the target machine first (after the mobile configs) > dont install it > then run the script (as stated just above).
Ive done both, checked the logs, and getting failures on both ends. Successful with the mobile configs though!
Thanks in advance!
-
Thanks for posting this, James Triplett II—and great call opening a Support ticket too! 🙌
For anyone else running into similar confusion with macOS Roaming Client deployment via Meraki (or other MDMs), here’s a quick recap from our Support Team:
You don’t need to pre-download the installer to the device. Instead, you’ll want to:
- Host the DNSFilter installer file within your MDM. You'll download the installer from the Roaming Client dashboard and upload it into the MDM hosting field following your MDM's guidance.
- Use the URL your MDM provides for that hosted file in your deployment script. We just provide the DNSFilter-hosted URL for users who may not have hosting capabilities.
For example, after uploading the installer to your MDM, you might see something like:
https://cdn.kandji.io/tenants/<tenant-id>/custom-apps/<app-guid>/DNSFilter%20Agent-2.2.0-Installer.pkgThat’s the URL you’ll plug into your script’s
DOWNLOADURLfield.If you’re using Meraki, the exact hosting and path setup may vary, but the same principle applies!
0
Please sign in to leave a comment.
Comments
1 comment