Users may install the software on-demand.Ī powerful feature of the Shared Apps directory is that app titles are automatically updated. Self-Serve: Software is presented in the Munki client, available on assigned devices.Managed: Software is automatically installed to devices without requiring any interaction from the user.With the Munki Integration, you may create two different types of Munki assignment groups: Assignment groups are created that associate software titles to devices. Software assignment for Munki distribution works similarly to distribution using MDM. An example of utilizing AutoPkg to publish software directly to SimpleMDM. munki recipe can be configured to upload to your SimpleMDM account and distribute to your fleet with just a couple of additional command line or recipe arguments. AutoPkg / Munki Toolsĭoes your business use AutoPkg or Munki command line tools, like munkiimport? The SimpleMDM Munki repo plugin allows AutoPkg and Munki to publish software directly to your SimpleMDM account. Binaries delivered via Munki do not need to be signed.
Our article How To Sign macOS PKGs for Deployment with MDM details this process. Please note that macOS requires that binaries distributed via MDM are signed. SimpleMDM processes each upload and determines whether it can be distributed via MDM, Munki, or both. Apps can be uploaded to SimpleMDM using the admin UI or via API. Perhaps you have an in-house application or custom build that you would like to distribute. The Shared Apps repository Custom App Upload SimpleMDM maintains these apps to ensure they remain up to date.
Apps from this directory, such as Google Chrome or Zoom, for instance, can be added to your catalog and distributed to devices without any additional work on your part. SimpleMDM accounts get immediate access to the Shared Apps directory: a growing collection of commonly used macOS software. There are currently three methods for adding Munki-distributed software to your SimpleMDM account. Maintenance, security reviews, and investment associated with in-house infrastructure are eliminated. Requests are served by SimpleMDM’s cloud infrastructure and content delivery network (CDN), ensuring that software downloads are quick and reliable. Communications are authenticated using per-device PKI, device attestation, and of course, MDM.
The Munki client benefits from SimpleMDM’s distributed, hardened infrastructure. No additional command line tooling nor third-party hosting services required. In this manner, an admin can view DEP PreStage, MDM device and user channel, and Munki app deployments from a single interface. Administrators are able to upload custom apps, assign them to devices, and install with a click. Munki app deployment is configured using the same interface used to deploy MDM apps. It integrates with SimpleMDM through standard built-in configuration options. SimpleMDM deploys the open-source, unmodified Munki client code. How SimpleMDM integrates with Munki Vanilla Install – No Black Box Client The self-serve private app store interface that presents to macOS users. The Munki codebase is maintained by an extensive roster of leading Mac Admins and is considered the best macOS software management solution available today. Employees may view the software library, install the applications that they need, and receive automatic updates as they become available.Īs a testament to Munki, many admins use it even when their MDM already includes a similar offering. Additionally, Munki provides a private, self-serve app store. Whereas MDM supports installing a subset of macOS package formats, Munki supports a much wider range of software, including the common. Munki is an open-source project that layers additional app capabilities onto the native Apple MDM protocol. With the SimpleMDM Munki Integration, a hosted Munki deployment is now available out-of-the-box for SimpleMDM admins. Munki traditionally requires additional cost and administrative effort to configure, maintain, and secure the Munki client software and a repository server.