If you’re a beginning Munki administrator, you’re probably pretty familiar with adding software to these categories:
- Managed Installs: Software that has to be installed on the client machine and does not appear as an optional install to be removed.
- Managed Uninstalls: Software that must be removed, so if it’s installed will be force-removed from the client machines.
- Optional Installs: Software that users can install or uninstall themselves using Managed Software Center.
- Managed Updates: Software whose update-for software will install automatically. For example, if you have MSOffice2011 installed and then have MSOffice2011Updates set as an update package for MSOffice2011, you would want MSOffice2011 in Managed Updates.
But what if you want to keep a package in optional installs but trigger it to install for a group of users (based on a script or a nopkg, for example)?
The terminal command you want to kick off is something like
Not that functionally there is any difference in having a duplicate managed install in the SelfServeManifest, but if you want to check first that the entry isn’t in there, you can use this command (perhaps assign it to a variable) to see if the entry’s already there before you decide to add it:
Acknowledgements: Full credit goes to Arjen van Bochoven’s post on the Munki Dev mailing list for this tip.