macOS 11.2 Intune Issue: App Installs & Shell Script Execution Failing
Organizations leveraging Microsoft Intune for comprehensive Mobile Device Management (MDM) on their Apple macOS endpoints often rely on its robust capabilities for application deployment and script execution. Intune provides a centralized platform to manage, configure, and secure macOS devices, ensuring compliance and enhancing user productivity across the enterprise. However, administrators occasionally encounter specific challenges, particularly when integrating with different macOS versions. This article details a known issue affecting macOS Big Sur 11.2.x devices, manifesting as critical failures in app installation and shell script execution through Intune. Understanding the symptoms, underlying cause, and the definitive solution is paramount for maintaining a healthy and productive macOS fleet.
Symptoms of Deployment Failure¶
Administrators managing macOS devices running Big Sur 11.2.x might observe a distinct set of operational issues that significantly impede device functionality and management capabilities. These symptoms collectively point towards a core problem with how Intune interacts with the macOS MDM framework on this specific operating system version. Recognizing these signs early is crucial for timely intervention and resolution.
App Installation Stagnation¶
A primary symptom encountered is the inability of applications to download and install correctly on affected devices. Whether these are Line-of-Business (LOB) applications, store apps, or custom packages deployed via Intune, the deployment process fails to complete successfully. From the administrator’s perspective within the Microsoft Intune admin center, the installation status for these applications will often display as “Install Pending” indefinitely. This state persists regardless of device reboots, policy syncs, or network connectivity checks, creating a bottleneck for new software deployments and updates.
This persistent “Install Pending” status is particularly problematic as it offers little insight into the actual failure point from the console view. End-users are left without critical applications, impacting their ability to perform daily tasks, while IT departments struggle to roll out necessary software or security patches. The lack of progress means devices might remain non-compliant or unprovisioned, leading to potential security vulnerabilities or operational inefficiencies within the organization.
Shell Script Execution Impairment¶
Beyond application deployment, the ability to execute shell scripts on macOS devices is a cornerstone of advanced Intune management. These scripts are vital for a multitude of tasks, including applying intricate configurations, automating post-enrollment setups, managing device security settings, or deploying specific agent software. However, on macOS 11.2.x, administrators will find that shell scripts fail to run as expected.
The root cause of this script execution failure is typically linked to the Microsoft Intune management agent itself, which cannot be installed successfully or operate correctly on these devices. This agent is fundamental for processing and executing the custom shell scripts pushed from Intune. Without a properly functioning agent, the scripts remain unprocessed, leading to a breakdown in automation, configuration management, and the overall desired state of the macOS endpoints. This issue severely limits an administrator’s ability to perform granular customizations and automated remediations across the fleet.
Detailed Log Analysis¶
When investigating these deployment and script execution failures, reviewing the device console logs provides invaluable diagnostic information. On affected macOS 11.2.x devices, entries similar to the following example will be frequently logged, offering a deeper insight into the underlying problem. These logs are critical for confirming the specific nature of the issue.
<Time> localhost mdmclient[2611]: [com.apple.ManagedClient:ManagedApps] StartInstall using UUID: <ID> for MDM 'Microsoft.Profiles.MDM'
<Time> localhost mdmclient[2611]: [com.apple.ManagedClient:ManagedApps] Installing with MDM options: {
ManagementFlags = 0;
ManifestURL = "https://euprodimedatapri.blob.core.windows.net/macsidecaragent-<ID>/sidecar_2103.013.plist";
RequestType = InstallApplication;
}
<Time> localhost mdmclient[2611]: [com.apple.ManagedClient:InstallApplication] InstallApplication (UUID:<ID>) (iOS: no) manifest: no
<Time> localhost mdmclient[2611]: [com.apple.ManagedClient:AppStore] Calling AppStore -submitManifestRequest. ID: <ID> Platform: <macos> Manifest: no URL: YES Certs: no Pinning: no
<Time> localhost mdmclient[2611]: [com.apple.ManagedClient:MDMDaemon] [ERROR] submitManifestRequest completed. ID: <ID> Error: Error Domain=ASDErrorDomain Code=506 "Install request is a duplicate" UserInfo={NSLocalizedDescription=Install request is a duplicate}
<Time> localhost mdmclient[2611]: [com.apple.ManagedClient:MDMDaemon] [ERROR] Assertion Failed. File: /AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/MCXTools/MCXTools-1430/ConfigProfiles/mdmclient/AppStoreUtil.mm Line: 578
<Time> localhost mdmclient[2611]: [com.apple.ManagedClient:MDMDaemon] Logging Manifest request failure. InstallUUID: <ID> Error: Error Domain=ASDErrorDomain Code=506 "Install request is a duplicate" UserInfo={NSLocalizedDescription=Install request is a duplicate}
<Time> localhost mdmclient[2611]: [com.apple.ManagedClient:ManagedApps] Processing install phase 97 for <ID> ==> {
"__Error__" = {
code = 506;
domain = ASDErrorDomain;
userInfo = {
NSLocalizedDescription = "Install request is a duplicate";
};
};
"__Success__" = 0;
}
This log snippet provides critical clues regarding the failure. The presence of mdmclient indicates the device’s MDM client is attempting to process an Intune-initiated action. The key error messages, Error Domain=ASDErrorDomain Code=506 "Install request is a duplicate" and [ERROR] Assertion Failed, are particularly telling. ASDErrorDomain often relates to the App Store Daemon, suggesting a problem within macOS’s internal application management services. The “Install request is a duplicate” error implies that macOS might be mistakenly identifying new installation attempts as redundant, even when no previous successful installation has occurred. The “Assertion Failed” line points to a code-level error within Apple’s own Managed Client tools, indicating a bug in the macOS operating system itself rather than an Intune-specific misconfiguration.
Here’s a breakdown of the critical log components:
| Log Component | Description | Significance |
|---|---|---|
mdmclient |
The process responsible for handling Mobile Device Management (MDM) commands and policies on the macOS device. | Indicates MDM commands are being received and processed by the device. |
[com.apple.ManagedClient:ManagedApps] |
A specific logging domain within the MDM client related to application management and installation. | Pinpoints the issue to app deployment. |
ManifestURL |
The URL where Intune hosts the manifest file for the application being deployed. | Shows Intune is correctly providing deployment instructions. |
RequestType = InstallApplication |
Confirms the MDM command is specifically for installing an application. | Verifies the intended action. |
Error Domain=ASDErrorDomain |
Error domain associated with the App Store Daemon (ASD), which handles app installations. | Directs the focus to macOS’s application management services. |
Code=506 |
Specific error code indicating an issue within the ASDErrorDomain. |
Points to a known error pattern within Apple’s system. |
"Install request is a duplicate" |
The user-friendly description of the error, suggesting that the system believes an identical installation is already in progress or has completed. | Crucial for understanding the logical flaw in macOS’s app handling. |
[ERROR] Assertion Failed. |
A programming assertion failure, typically indicating an unexpected condition or a bug in the software’s internal logic. | Strong evidence of a defect within the macOS operating system’s MDM components. |
File: .../AppStoreUtil.mm Line: 578 |
Specific file path and line number within Apple’s source code where the assertion failed. | Confirms the error originates deep within the OS framework, not merely a configuration issue. |
This detailed log analysis empowers IT professionals to quickly confirm if their devices are exhibiting the specific macOS 11.2.x Intune issue.
Root Cause of the Anomaly¶
The underlying cause of these pervasive deployment and script execution failures on macOS Big Sur 11.2.x is identified as a known issue within the macOS operating system itself. Operating system updates often introduce new features, security enhancements, and bug fixes, but occasionally, they can also inadvertently introduce new regressions or incompatibilities with existing frameworks, such as the MDM services. In the case of macOS 11.2.x, it appears a specific defect was present within the operating system’s internal mechanisms responsible for handling application installation requests and potentially the associated MDM agent communication.
This defect caused the mdmclient to misinterpret new installation attempts as duplicates, leading to the ASDErrorDomain Code=506 error. Furthermore, it directly interfered with the successful installation and operation of the Microsoft Intune management agent, which is essential for advanced management tasks like shell script execution. Such “known issues” are not uncommon in the lifecycle of an operating system. They typically arise from complex interactions between different system components or unforeseen side effects of changes made during development. The fact that an “Assertion Failed” error is logged further underscores that this was an internal OS bug, not an Intune configuration problem or a network issue.
Definitive Solution¶
Fortunately, the solution to this specific macOS 11.2.x Intune issue is straightforward and effective: upgrading the affected devices to a newer version of macOS. Apple regularly releases updates that address known bugs, improve stability, and enhance security. In this instance, macOS 11.3 and subsequent versions contain the necessary fixes to resolve the application deployment and shell script execution problems.
Upgrade Path and Considerations¶
To remediate the issue, administrators should plan and execute an upgrade of all macOS 11.2.x devices to macOS 11.3 or a later version (e.g., macOS 11.6.x for Big Sur, or even migrating to macOS Monterey, Ventura, or Sonoma if compatible and desired). This process can often be managed through Intune itself, using a “major OS update” policy or by pushing the update as an application. Before initiating a widespread upgrade, it is always recommended to:
- Test the upgrade process on a small group of pilot devices to identify any unforeseen issues with your specific device models or configurations.
- Ensure device compatibility with the target macOS version.
- Back up critical data on devices, especially if a significant OS jump is being made.
- Communicate clearly with end-users regarding potential downtime or necessary steps.
Once the devices are successfully upgraded to macOS 11.3 or a newer version, the underlying OS bug is resolved. This will allow Intune to properly manage application installations, eliminating the “Install Pending” status, and enable the Microsoft Intune management agent to install and function correctly, thereby facilitating the successful execution of shell scripts. Regular OS updates are not just about fixing specific bugs; they are a critical component of maintaining a secure, stable, and feature-rich computing environment.
Proactive Device Management with Intune¶
Beyond resolving this specific issue, adopting a proactive approach to macOS device management with Intune can prevent similar disruptions in the future.
- Phased Rollouts: Implement phased rollouts for new macOS versions and major Intune configuration changes. This involves deploying updates to small, controlled groups before wider release, allowing for early detection and mitigation of issues.
- Monitoring and Reporting: Utilize Intune’s reporting capabilities to monitor application installation statuses, script execution results, and device compliance. Set up alerts for critical failures to respond swiftly.
- Regular Audits: Periodically audit device logs and Intune diagnostic information to identify recurring patterns or emerging issues before they impact a large number of users. The macOS Console app and
log streamcommand-line utility are invaluable for this. - Stay Informed: Keep abreast of Microsoft Intune updates, Apple macOS releases, and relevant documentation from both vendors. Subscribing to official blogs and forums can provide early warnings about known issues.
By following these best practices, organizations can build a more resilient and efficient macOS management ecosystem within their Intune environment.
Conclusion¶
The challenges faced by administrators with macOS 11.2.x devices regarding Intune app deployments and shell script executions underscore the intricate relationship between operating system versions and MDM solutions. While frustrating, the “Install request is a duplicate” and “Assertion Failed” errors clearly pointed to an inherent bug within macOS Big Sur 11.2.x. Fortunately, Apple’s prompt resolution in macOS 11.3 and later versions provides a clear and effective path to remediation. Prioritizing OS updates is not just about gaining new features, but fundamentally about ensuring the stability, security, and manageability of your device fleet. By upgrading affected devices and adopting a proactive, well-informed management strategy, organizations can maintain a robust and reliable Intune-managed macOS environment.
Have you encountered similar issues with macOS and Intune? How do you manage your OS update cycles for critical business devices? Share your experiences and insights in the comments below, or suggest other troubleshooting tips that have helped you!
Post a Comment