Already a NinjaOne customer? Log in to view more guides and the latest updates.

Apple MDM: Troubleshooting Apps and Books Sync Issues

Issue

I added a new application (app) via Apple Business Manager (ABM), but it is not syncing to NinjaOne.

Environment

  • NinjaOne Mobile Device Management (MDM)
  • Apple iOS
  • Apple iPadOS

Cause

When a newly added app in ABM fails to appear in the Apps and Books in NinjaOne (via the linked content token), the failure generally indicates a sync failure or misconfiguration.

Resolution

The following steps explain how to efficiently isolate and diagnose your issue.

Check for Sync Errors

NinjaOne should surface a sync error or failure message when the content token fails to pull updated app data from ABM. However, not all sync failures produce actionable errors; some issues may go undetected by NinjaOne.

A sync may have failed even if NinjaOne does not display an error. If a new app does not appear, treat it as a potential silent sync failure or a per-app sync anomaly.

Troubleshooting

  1. Validate ABM app configuration.
    1. Ensure you have assigned the app to the correct location in ABM that corresponds to the content token in NinjaOne.
    2. Verify that you have licenses assigned to that location for the app in question.
    3. Confirm the app supports platforms compatible with NinjaOne MDM (iOS, iPadOS, macOS). If NinjaOne does not support an app, it will not appear in the platform.
  2. Perform the following test to determine whether the issue affects the entire content token or only the specific app:
    1. In ABM, add or remove a different app or modify license quantities for an existing app within the same content token's Location.
    2. Trigger a manual sync in NinjaOne for the content token. To learn how to perform a manual sync, refer to NinjaOne MDM: Apple Apps and Books.
      • If the unrelated app or license change syncs, this indicates the token is syncing correctly. The issue is specific to the one app.
      • If the unrelated changes also do not sync, this indicates the entire content token may be failing, even if there is no sync error.
    3. Verify that the change appears in NinjaOne.

Additional Resources

To learn more about troubleshooting NinjaOne MDM, refer to NinjaOne MDM: Resource Catalog.

FAQ

Next Steps