All other imaging variations are determined by Munki manifests. ![]() This allows me to have only two DeployStudio workflows for all computers: one for new, out-of-box Macs which don’t require a rebuild, and one for rebuilding Macs. I use these fields to determine manifest enrolment using Munki-Enroll. ![]() If you are using Imagr instead of DeployStudio, you could easily script the use of these fields with commands such as: sudo defaults write /Library/Preferences/ Text1 "Some text" ![]() The contents of these fields are actually written to a preference file on the host computer at /Library/Preferences/, with key names Text1, Text2, Text3, Text4. These are four text fields available in the Hostname workflow page. I have tweaked Munki-Enroll in order to leverage a feature of DeployStudio called Computer Information fields. It enables the automated creation of unique client manifests, which makes it easy to change the group manifests of a client remotely at any time using tools like manifestutil, MunkiAdmin or MunkiWebAdmin, utilising the included_manifest key in Munki manifests. ![]() Munki-Enroll is a useful tool to use when installing the Munki tools on Mac clients.
0 Comments
Leave a Reply. |