Our current deployment process for Non-DEP, non-T2 Macs is imaging-based through DeployStudio. The imaging ends with the installation of the Munki Agent, which installs the Meraki agent and all the other apps. However, the SM profile .mobileconfig needs to get on there in an automated way, and I can't find one that works.   I can doubleclick on it, while logged in as an admin and install it manually, but who has time for that? Munkiimport will not import the .mobileconfig as downloaded from the Dashboard "Add Devices" page. MunkiAdmin will not import it either. I tried wrapping in a package with Profile-to-PKG.py (Thanks, Tim Sutton!). It makes a PKG file, but the installation fails. Works fine with other .mobileconfig files...   I know something is weird and unholy about this mobileconfig when I can't even install it from the command line in its pure form.   profiles -I -F /Users/myuser/Downloads/meraki_sm_mdm.mobileconfig -f -v (The operation couldn’t be completed. (InternalError error 1.))   What is it about this .mobileconfig file? Is it haunted? Is it from another dimension of space and time? Endpoint management is all about automating your devices... so why do I have to do a manual process to implement it. Am I crazy? (Yes, but that's beside the point) I contacted Meraki support, and they sent me here. The wisdom is in the group... ... View more