-
Notifications
You must be signed in to change notification settings - Fork 339
App Store Apps
An overview of deploying Mac App Store applications using Munki.
This is technical advice, not legal advice. Make sure you are complying with vendor agreements and have purchased the appropriate number of licenses for the software you wish to deploy.
Basic steps:
- Purchase one or more licenses for an application from the App Store under an institutional AppleID.
- Download the application (using the institutional AppleID) on a Mac with the Munki admin tools installed.
- Import the application into your Munki repo using
munkiimport /Applications/Foo.app
, where "/Applications/Foo.app" is the path to the downloaded/purchased application. - Deploy the application using Munki the same way as any other application.
When there are updates for the application, repeat steps 2-4 above.
This technique will work for applications that do not do App Store receipt validation. For applications that do App Store receipt validation, you'll need to use something other than Munki to distribute these applications.
Related links:
https://support.apple.com/kb/HT5061
https://support.apple.com/kb/ht4781
https://support.apple.com/kb/HT4831
VPP and Managed Distribution:
https://www.apple.com/business/vpp/
https://www.apple.com/education/it/vpp/
Q: How do I know if an application does App Store receipt validation?
A: I don't know how to tell in advance. You'll know when you try to deploy it and it asks for authorization and refuses to run on deployed machines!
- Getting Started
- Overview
- Discussion Group
- Demonstration Setup
- Glossary
- Frequently Asked Questions
- Contributing to Munki
- Release Notes
- Introduction
- Managed Software Center in Munki 5.2
- Manual Apple Updates
- force_install_after_date for Apple Updates
- Additional update encouragement
- Aggressive update notifications
- AggressiveUpdateNotificationDays preference
- Additional Munki 5 changes
- Configuration profile notes
- Major macOS upgrade notes
- Upgrading to Munki 5
- Introduction
- Munki Links
- Product Icons
- Screenshots In Product Descriptions
- Client Customization
- Custom Help Content
- Featured Items
- Update Notifications:
- Introduction
- iconimporter
- makepkginfo
- munkiimport
- managedsoftwareupdate
- makecatalogs
- manifestutil
- repoclean
- Preferences
- Default Repo Detection
- Default Manifest Resolution
- Managed Preferences Support In Munki
- Apple Software Updates With Munki
- Pkginfo Files
- Supported Pkginfo Keys
- Pre And Postinstall Scripts
- Munki And AutoRemove
- Blocking Applications
- ChoiceChangesXML
- CopyFromDMG
- nopkg items
- How Munki Decides What Needs To Be Installed
- Default Installs
- Removal of Unused Software
- Upgrading macOS:
- Apple Updates:
- Securing the Munki repo
- Preflight And Postflight Scripts
- Report Broken Client
- MSC Logging
- Munki With Git
- Bootstrapping With Munki
- License Seat Tracking
- LaunchD Jobs and Changing When Munki Runs
- Web Request Middleware
- Repo Plugins
- Downgrading Software
- Downgrading Munki tools
- Authorized Restarts
- Allowing Untrusted Packages
- About Munki's Embedded Python
- Customizing Python for Munki
- Configuration Profile Emulation
- PPPC Privacy permissions
- AutoPkg
- Repackaging
- Creating Disk Images
- Stupid Munki Tricks
- Troubleshooting
- Professional Support
- Known Issues and Workarounds
- Building Munki packages
- Munki packages and restarts
- Signing Munki
- Removing Munki
- More Links And Tools
- Munki Configuration Script
- Who's Using Munki
- Munki 3 Information
- Munki 4 Information
- macOS Monterey Info
- Pkginfo For Apple Software Updates
- Managing Configuration Profiles
- Microsoft Office
- Adobe Products
- Upgrading macOS: