Home error codes intune macos troubleshooting

Troubleshooting Intune: Fix Error 0x87D13BA2 When Deploying macOS LOB Apps

Updated: • 0 • min read
Table of Contents

This document provides a detailed troubleshooting guide to resolve the error message 0x87D13BA2 encountered during the deployment of macOS Line-of-Business (LOB) applications using Microsoft Intune. This error specifically indicates an issue with the bundle identifiers within the application package, preventing Intune from accurately reporting the installation status, even when the application might be successfully installed on the target macOS device. Understanding the nuances of this error and applying the outlined solution is crucial for maintaining efficient and reliable macOS application deployments within your organization’s Intune environment.

Symptoms

The primary symptom of error 0x87D13BA2 manifests within the Microsoft Intune admin center. When a macOS LOB application deployment encounters this issue, the Device install status for the affected application will display a “Failed” status. Drilling down into the status details reveals the specific error message: “One or more apps contain invalid bundleIDs. (0x87D13BA2)”.

Error 0x87D13BA2 When Deploying macOS LOB Apps

This error presentation in the Intune admin center can be misleading, as users may report that the application is functioning correctly on their macOS devices despite the “Failed” status reported in Intune. This discrepancy arises because the error is not necessarily indicative of a failed installation, but rather a failure in Intune’s ability to correctly track and report the installation status of all components within the application package.

Consider the example of deploying Microsoft Teams as a macOS LOB application. Even if Teams installs and operates without issue on a user’s Mac, Intune might still report error 0x87D13BA2. This situation can create confusion for IT administrators and hinder accurate device and application management. It’s essential to differentiate between a genuine application installation failure and this reporting error to effectively troubleshoot and maintain a healthy application deployment ecosystem.

Further investigation might reveal that the application is listed in the macOS system’s application directory and functions as expected. However, Intune’s inability to reconcile the bundle identifiers prevents it from confirming successful installation, leading to the persistent error status within the management console. This can impact compliance reporting and other Intune-driven automation that relies on accurate application installation status.

Cause

The root cause of error 0x87D13BA2 lies in the structure of certain macOS application packages and how Intune processes them. This issue typically arises when deploying applications packaged with multiple components or sub-applications bundled together within a single .pkg or .dmg file. Common examples include applications like Microsoft Office suites, creative software suites, or communication platforms like Microsoft Teams, which may consist of multiple individual applications working in concert.

Intune’s application deployment mechanism for macOS LOB apps relies on identifying and tracking individual applications within a package using their bundle identifiers (bundleIDs). A bundle identifier is a unique string that identifies each application within the macOS ecosystem. When an application package contains multiple applications, Intune expects to receive installation status reports for each of these individual applications.

The error 0x87D13BA2 occurs when not all applications within the package correctly report their installation status back to Intune. This can happen for several reasons:

  • Package Structure: The application package might be structured in a way that Intune’s default detection methods cannot identify and track all individual applications and their bundle identifiers.
  • Reporting Mechanisms: Some applications within the package might not be configured to report their installation status back to the MDM (Mobile Device Management) agent, which is responsible for communicating with Intune. This could be due to the application’s design or configuration.
  • Intune Limitations: In certain complex application packages, Intune’s current capabilities might not be sufficient to accurately parse and track the installation status of every component, especially if the applications are deeply nested or use unconventional packaging methods.

Essentially, Intune detects discrepancies between the bundle identifiers it expects to see based on the application package metadata and the actual bundle identifiers reported by the device. When Intune cannot reconcile these discrepancies, it flags the deployment with error 0x87D13BA2, indicating that it suspects invalid bundleIDs or an inability to track all components.

This issue is more prevalent with complex application suites rather than single, self-contained applications. Understanding that the error is often related to reporting inconsistencies rather than a true installation failure is key to applying the correct solution and avoiding unnecessary re-deployments or troubleshooting efforts focused on the wrong areas.

Solution

To resolve error 0x87D13BA2 and enable accurate reporting of the macOS LOB app installation status in Intune, you need to align Intune’s application definition with the actual applications installed on the macOS device. This involves identifying the valid bundle identifiers of the installed applications and updating the Intune application configuration to reflect only those bundle identifiers that are actively reporting their status. The following steps outline the process:

  1. Identify Installed Applications and Bundle Identifiers:

    The first step is to determine the bundle identifiers of the applications that are actually installed on a macOS device after deploying the LOB app through Intune. You can achieve this by using the macOS command-line tool mdmclient.

    • Open Terminal: Access the Terminal application on a macOS device where the application in question has been deployed via Intune.

    • Execute the Command: Run the following command in Terminal. This command queries the MDM client for a list of installed applications and redirects the output to a text file named InstalledApps.txt in your current user directory. The sudo command is necessary as it requires administrator privileges to execute mdmclient.

      sudo /usr/libexec/mdmclient QueryInstalledApps > InstalledApps.txt

    • Authenticate: You will be prompted to enter the administrator password for the macOS device to authorize the sudo command.

    • Locate the Output File: After the command completes, find the InstalledApps.txt file in your user’s home directory.

  2. Examine the InstalledApps.txt File:

    Open the InstalledApps.txt file using a text editor. This file contains a structured list of applications installed on the device, along with their associated bundle identifiers and other relevant information.

    InstalledApps.txt Example

    • Identify Relevant Bundle Identifiers: Carefully review the contents of the file and locate the entries related to the application you are troubleshooting in Intune. Look for bundle identifiers that correspond to the main application or its components. Often, application names are included in the output, making it easier to identify the relevant sections.

    • Note Down Bundle Identifiers: Make a list of the bundle identifiers that appear to be associated with the deployed application as listed in the InstalledApps.txt file.

  3. Access Intune Application Properties:

    Navigate to the Microsoft Intune admin center (https://endpoint.microsoft.com/) and locate the macOS LOB application that is reporting error 0x87D13BA2.

    • Select the Application: Click on the application name to open its overview page.

    • Navigate to Properties: In the application overview, select Properties from the left-hand menu.

    • Edit App Information: Within the Properties pane, find the App information section and click Edit.

  4. Compare and Remove Invalid Bundle Identifiers:

    The Edit application pane for App information will display a section listing the “Included apps”. This section contains the bundle identifiers that were initially configured for the application in Intune.

    Intune App Information - Included Apps

    • Compare Lists: Carefully compare the list of bundle identifiers in Intune’s “Included apps” section with the list of bundle identifiers you extracted from the InstalledApps.txt file in Step 2.

    • Remove Discrepancies: Identify any bundle identifiers listed in Intune that do not appear in the InstalledApps.txt file. These are likely the “invalid” or non-reporting bundle identifiers causing the error. Remove these bundle identifiers from the “Included apps” list in Intune by clicking the delete icon (usually a trash can or an “X”) next to each entry.

    • Retain Valid Bundle Identifiers: Ensure that only the bundle identifiers that you confirmed are present and reported in the InstalledApps.txt file remain in the “Included apps” list in Intune.

  5. Save and Sync:

    After removing the extraneous bundle identifiers, finalize the changes in Intune.

    • Review Changes: Carefully review the updated “Included apps” list to ensure accuracy.

    • Save Changes: Click Review + save and then Save to apply the changes to the Intune application configuration.

    • Initiate Device Sync: On the macOS device used for troubleshooting, manually initiate a sync with Intune. This can typically be done through the Company Portal application or via macOS system settings related to MDM profiles. This sync forces the device to report its latest application installation status to Intune based on the updated application configuration.

    After the device sync completes, monitor the Device install status of the application in the Intune admin center. The error 0x87D13BA2 should be resolved, and the application status should now accurately reflect the installation state on the device, ideally showing “Installed” if the application is indeed successfully installed.

By meticulously following these steps, you can effectively troubleshoot and resolve error 0x87D13BA2, ensuring accurate application deployment status reporting for macOS LOB applications in Microsoft Intune. This leads to improved device management, compliance accuracy, and a clearer understanding of your organization’s macOS application landscape.

Have you encountered error 0x87D13BA2 when deploying macOS LOB apps in Intune? What challenges did you face, and did this solution help you resolve the issue? Share your experiences and questions in the comments below!

Post a Comment