@a.holley I create a script from the config profile and deploy it that way.
Here are the steps:
- Create the Configuration Profile .mobileconfig however you want, for example, in Jamf Pro, or in Apple's Profile Manager. As long as you can get a physical .mobileconfig file in the end, or access the direct xml of the profile.
- If you created it in Jamf Pro, access it in the GUI and use the Download button in the Profile details.
- Use the following command on the downloaded file. This is necessary with any downloaded from Jamf Pro, since they end up as signed Config Profiles:
security cms -D -i /path/to/profilename.mobileconfig | xmllint --format -
4. Take the output from the above command in Terminal and copy it. You will paste this into a script.
5. Create a script with the following information in it. You will need to edit some of this to correspond to whatever it is that you're deploying, like a name for the profile for example.
#!/bin/bash ## Create the .mobileconfig file in /private/tmp/
cat << EOF > /private/tmp/profile.mobileconfig
*<paste the entire xml code for the configuration profile from step 3 and 4 here, unaltered>*
EOF
## Install the .mobileconfig with the profiles command
/usr/bin/profiles -I -F /private/tmp/profile.mobileconfig
if [ $? == 0 ]; then
echo "Successfully installed. Deleting local file..."
rm -f /private/tmp/profile.mobileconfig
exit 0
else
echo "Installation of profile failed. Deleting local file..."
rm -f /private/tmp/profile.mobileconfig
exit 1
fi
So you can essentially create these scripts that install a config profile. A bit more of a pain but it has worked for us.
You can even make extension attributes based on the config profile UUID to confirm compliance.
I did not come up with this by the way, I can't remember where I found it to give credit though.
