Release Notes
Abstract
IBM MaaS360 for macOS enhanced the MaaS360 packager that allows administrators to distribute enterprise applications through the PKG URL from external storage, reducing reliance on MaaS360 storage workflow. Also, the uninstall process is redesigned to prevent accidental or malicious device unenrollment by retaining MDM profiles and enabling automatic agent reinstallation. These improvements collectively enhance scalability, security, and operational efficiency for enterprise macOS device management.
Content
MaaS360 Packager
Previously, the MaaS360 Packager required administrators to upload generated
.pkg files directly to MaaS360, where they were stored in the platform’s managed storage. Given the large size of many macOS applications, this approach consumed significant storage space as apps were added or updated. Additionally, it did not support the distribution of enterprise apps hosted in external storage.With this release, MaaS360 Packager introduces a new, more flexible workflow. Administrators can now specify a custom PKG URL pointing to their own storage location. Once configured, the application is treated like any other enterprise app within MaaS360. During distribution, the user’s Mac downloads the app directly from the specified URL, completely bypassing MaaS360’s managed storage.
Note: For this feature to work successfully, the device where the app is being installed must have read access to the specified download URL. The Mac must be able to directly access and retrieve the package from the URL provided. If the device cannot reach the URL or does not have permission to download the file, the installation will fail at the MaaS360 App Catalog.
MaaS360 uninstall workflow
Previously, the agent and all MaaS360 MDM profiles were deleted from the device when the IBM MaaS360 mac software was uninstalled.
With this release, there is an improvised version of macOS device management for MaaS360 that avoids the removal of the MDM profile during agent uninstallation on managed devices. The agent no longer starts a new registration once it is reinstalled. To maintain device management continuity, it instead fetches the current enrollment information. Also, monitoring to determine whether the agent is installed on the device is now part of MaaS360. Every 24 hours, the system automatically starts the reinstallation process by using MDM if the agent cannot be located.
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSYSXX","label":"IBM MaaS360"},"ARM Category":[{"code":"a8m3p000000hCHXAA2","label":"DEVICES"},{"code":"a8m3p000000hCH9AAM","label":"PLATFORM"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":""}]
Was this topic helpful?
Document Information
Modified date:
04 July 2025
UID
ibm17235721