Software Distribution for macOS application Deployment Requirements

You can deploy macOS applications with the software distribution using the supported file types, platform versions, and agents.

Supported Platform Version

macOS 10.10+

Supported File Types

PKG, DMG, MPKG

Supported Agents

• Omnissa Workspace ONE Intelligent Hub for macOS 3.0
• (Optional) Workspace ONE 1.0 native application

Considerations

• pkginfo metadata file generation – You can upload all primary macOS software file types through Resources > Apps > Internal application. A PKG file can be a Bootstrap package, or it can be managed through a full lifecycle management. To configure advanced management features for macOS software through the integrated Open-Source Munki library, you must generate a metadata file for the application before uploading the application to the Omnissa Workspace ONE UEM console. You can generate a pkginfo metadata file using the Admin Assistant Tool.
• Third-Party Integration – Apart from using the Admin Assistant tool to generate metadata or a pkginfo file, you can also integrate with AutoPkg and AutoPkgr tools that have ready-made software with configuration features. They perform periodic checks for updates to the third-party software and notify the admins.
• Migration from Munki setup to Omnissa Workspace ONE UEM – You can add the existing application with the direct link of the application on your current Munki Repository server. This method is advantageous, as there is no requirement for an actual upload of the file to Workspace ONE UEM, which uses Workspace ONE UEM File Storage space.
• CDNs and File Storage Systems – All deployments use a content delivery network (CDN) to deploy applications. This method has the advantage of sending the content to devices in the network and to remote devices. It also offers an increased download speed and reduces the bandwidth on the Workspace ONE UEM servers.