Skip to content

Commit 57e4dbf

Browse files
author
Angela Fleischmann
authored
Merge pull request #6555 from Erikre/erikre-rel2201-1171356
Erikre-rel2201-1171356
2 parents 4a4ada3 + 15d4780 commit 57e4dbf

7 files changed

Lines changed: 255 additions & 39 deletions

File tree

memdocs/intune/apps/apps-add.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ keywords:
66
author: Erikre
77
ms.author: erikre
88
manager: dougeby
9-
ms.date: 11/22/2021
9+
ms.date: 01/18/2022
1010
ms.topic: overview
1111
ms.service: microsoft-intune
1212
ms.subservice: apps
@@ -67,6 +67,7 @@ The following table lists the specific app types and how you can add them in the
6767
| Android Enterprise system apps | Store app | Select **Android Enterprise system app** as the **app type**, and then enter the app name, publisher, and package file. |
6868
| Windows app (Win32) | LOB app | Select **Windows app (Win32)** as the **app type**, select the **App package file**, and then select an installation file with the extension **.intunewin**. |
6969
| macOS LOB apps | LOB app | Select **Line-of-business** as the **app type**, select the **App package file**, and then select an installation file with the extension **.intunemac**. |
70+
| macOS apps (DMG) | LOB app (non-store app) | Select **macOS app (DMG)** as the app type, select the **App package** file, and then select an installation file with the extension *.dmg*. |
7071

7172
<sup>1</sup> For more information about Android Enterprise and Android work profiles, see [Understanding licensed apps](apps-add.md#understanding-licensed-apps) below.
7273

Lines changed: 72 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,72 @@
1+
---
2+
# required metadata
3+
4+
title: Understanding Microsoft Intune management agent for macOS
5+
titleSuffix:
6+
description: Learn about the Microsoft Intune management agent for macOS.
7+
keywords:
8+
author: Erikre
9+
ms.author: erikre
10+
manager: dougeby
11+
ms.date: 01/18/2022
12+
ms.topic: how-to
13+
ms.service: microsoft-intune
14+
ms.subservice: apps
15+
ms.localizationpriority: medium
16+
ms.technology:
17+
ms.assetid:
18+
19+
# optional metadata
20+
21+
#ROBOTS:
22+
#audience:
23+
24+
ms.reviewer: arnab
25+
ms.suite: ems
26+
search.appverid: MET150
27+
#ms.tgt_pltfrm:
28+
ms.custom: intune-azure
29+
ms.collection:
30+
- M365-identity-device-management
31+
- macOS
32+
- highpri
33+
---
34+
35+
# Microsoft Intune management agent for macOS
36+
37+
### Why is the agent required?
38+
The Microsoft Intune management agent is necessary to be installed on managed macOS devices in order to enable advanced device management capabilities that are not supported by the native macOS operating system.
39+
40+
### How is the agent installed?
41+
The agent is automatically and silently installed on Intune-managed macOS devices that you assign at least one shell script to in Microsoft Endpoint Manager Admin Center. The agent is installed at `/Library/Intune/Microsoft Intune Agent.app` when applicable and doesn't appear in **Finder** > **Applications** on macOS devices. The agent appears as `IntuneMdmAgent` in **Activity Monitor** when running on macOS devices.
42+
43+
### What does the agent do?
44+
- The agent silently authenticates with Intune services before checking in to receive assigned shell scripts for the macOS device.
45+
- The agent receives assigned shell scripts and runs the scripts based on the configured schedule, retry attempts, notification settings, and other settings set by the admin.
46+
- The agent checks for new or updated scripts with Intune services usually every 8 hours. This check-in process is independent of the MDM check-in.
47+
48+
### How can I manually initiate an agent check-in from a Mac?
49+
On a managed Mac that has the agent installed, open **Company Portal**, select the local device, click on **Check settings**. This initiates an MDM check-in as well as an agent check-in.
50+
51+
Alternatively, open **Terminal**, run the `sudo killall IntuneMdmAgent` command to terminate the `IntuneMdmAgent` process. The `IntuneMdmAgent` process will restart immediately, which will initiate a check-in with Intune.
52+
53+
> [!NOTE]
54+
> The **Sync** action for devices in Microsoft Endpoint Manager Admin Console initiates an MDM check-in and does not force an agent check-in.
55+
56+
### When is the agent removed?
57+
There are several conditions that can cause the agent to be removed from the device such as:
58+
- Shell scripts are no longer assigned to the device.
59+
- The macOS device is no longer managed.
60+
- The agent is in an irrecoverable state for more than 24 hours (device-awake time).
61+
62+
### Why are scripts running even though the Mac is no longer managed?
63+
When a Mac with assigned scripts is no longer managed, the agent is not removed immediately. The agent detects that the Mac is not managed at the next agent check-in (usually every 8 hours) and cancels scheduled script-runs. So, any locally stored scripts scheduled to run more frequently than the next scheduled agent check-in will run. When the agent is unable to check-in, it retries checking in for up to 24 hours (device-awake time) and then removes itself from the Mac.
64+
65+
### How to turn off usage data sent to Microsoft for shell scripts?
66+
To turn off usage data sent to Microsoft from the Intune management agent, open Company Portal and select **Menu** > **Preferences** > *uncheck 'allow Microsoft to collect usage data'*. This will turn off usage data sent for both the agent and Company Portal.
67+
68+
## Next steps
69+
70+
- The app you have created is displayed in the apps list. You can now assign it to the groups you choose. For help, see [How to assign apps to groups](apps-deploy.md).
71+
- Learn more about the ways in which you can monitor the properties and assignment of your app. For more information, see [How to monitor app information and assignments](apps-monitor.md).
72+
- Learn more about the context of your app in Intune. For more information, see [Overview of device and app lifecycles](../fundamentals/device-lifecycle.md)
Lines changed: 169 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,169 @@
1+
---
2+
# required metadata
3+
4+
title: Add a macOS DMG app to Microsoft Intune
5+
titleSuffix:
6+
description: Add a macOS DMG app to Microsoft Intune.
7+
keywords:
8+
author: Erikre
9+
ms.author: erikre
10+
manager: dougeby
11+
ms.date: 01/18/2022
12+
ms.topic: how-to
13+
ms.service: microsoft-intune
14+
ms.subservice: apps
15+
ms.localizationpriority: medium
16+
ms.technology:
17+
ms.assetid:
18+
19+
# optional metadata
20+
21+
#ROBOTS:
22+
#audience:
23+
24+
ms.reviewer: arnab
25+
ms.suite: ems
26+
search.appverid: MET150
27+
#ms.tgt_pltfrm:
28+
ms.custom: intune-azure
29+
ms.collection:
30+
- M365-identity-device-management
31+
- macOS
32+
- highpri
33+
---
34+
35+
# Add a macOS DMG app to Microsoft Intune
36+
37+
> [!NOTE]
38+
> The feature is in public preview.
39+
40+
Use the information in this article to help you add a macOS DMG app to Microsoft Intune. A DMG app is a disk image file that contains one or more applications within it. Many common applications for macOS are available in DMG format. For more information about how to create a disk image file, see [Apple’s website](https://support.apple.com/guide/disk-utility/create-a-disk-image-dskutl11888/mac).
41+
42+
> [!NOTE]
43+
> The DMG file must contain one or more files with .app extensions. DMG files containing other types of installer files will not be installed.
44+
45+
## Prerequisites
46+
47+
The following prerequisites must be met before a macOS DMG app is installed on macOS devices.
48+
- Devices are managed by Intune.
49+
- DMG app is smaller than 2GB in size.
50+
- The [Microsoft Intune management agent for macOS](../apps/lob-apps-macos-agent.md) is installed.
51+
52+
## Important considerations for deploying DMG apps
53+
54+
A single DMG should only contain a single application file or multiple application files that are dependent on one another. The containing application files can be listed under the **Included apps** section in the **Detection rules** tab in order starting with the parent app to be used in reports.
55+
56+
It is not recommended that multiple apps that are not dependent on each other are installed using the same DMG file. If multiple independent apps are deployed using the same DMG app, failure to install one app will cause other apps to be re-installed. In this case, monitoring reports consider the DMG installation a failure as well.
57+
58+
## Select the app type
59+
1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
60+
2. Select **Apps** > **All apps** > **Add**.
61+
3. In the **Select app type** pane, under the **Other** app types, select **macOS app (DMG)**.
62+
4. Click **Select**. The **Add app** steps are displayed.
63+
64+
## Step 1 – App information
65+
66+
Select the app package file:
67+
1. In the **Add app** pane, click **Select app package file**.
68+
2. In the **App package file** pane, select the browse button. Then, select a macOS DMG file with the extension *.dmg*. The app details will be displayed.
69+
3. When you're finished, select **OK** on the **App package file** pane to add the app.
70+
71+
### Set app information
72+
73+
1. In the **App information** page, add the details for your app. Depending on the app that you chose, some of the values in this pane might be automatically filled in.
74+
75+
- **Name**: Enter the name of the app as it appears in the policy name and company portal. Make sure all app names that you use are unique. If the same app name exists twice, only one of the apps appears in the company portal.
76+
- **Description**: Enter the description of the app. The description appears in the company portal.
77+
- **Publisher**: Enter the name of the publisher of the app.
78+
- **Category**: Select one or more of the built-in app categories, or select a category that you created. Categories make it easier for users to find the app when they browse through the company portal.
79+
- **Information URL**: Optionally, enter the URL of a website that contains information about this app. The URL appears in the company portal.
80+
- **Privacy URL**: Optionally, enter the URL of a website that contains privacy information for this app. The URL appears in the company portal.
81+
- **Developer**: Optionally, enter the name of the app developer.
82+
- **Owner**: Optionally, enter a name for the owner of this app. An example is HR department.
83+
- **Notes**: Enter any notes that you want to associate with this app.
84+
- **Logo**: Upload an icon that is associated with the app. This icon is displayed with the app when users browse through the company portal.
85+
2. Click Next to display the Scope tags page.
86+
87+
## Step 2 – Requirements
88+
89+
You can choose the minimum operating system required to install this app.
90+
91+
**Minimum Operating System**: From the list, choose the minimum operating system version on which the app can be installed. If you assign the app to a device with an earlier operating system, it will not be installed.
92+
93+
## Step 3 – Detection rules
94+
95+
You can use detection rules to choose how an app installation is detected on a managed macOS device.
96+
97+
**Ignore app version**: Select **Yes** to install the app if the app is not already installed on the device. This will only look for the presence of the app bundle ID. For apps that have an auto-update mechanism, select **Yes**. Select **No** to install the app when it is not already installed on the device, or if the deploying app's version number does not match the version that's already installed on the device.
98+
99+
**Included apps**: Provide the apps that are contained in the uploaded file. Included app bundle IDs and build numbers are used for detecting and monitoring app installation status of the uploaded file. Included apps list should only contain the application(s) installed by the uploaded file in **Applications** folder on Macs. Any other type of file that is not an application or an application that is not installed to **Applications** folder should be excluded from the **Included apps** list. If **Included apps** list contains files that are not applications or if all the listed apps are not installed, app installation status does not report success.
100+
101+
> [!NOTE]
102+
> - The first app on the Included apps list is used for identifying the app when multiple apps are present in the DMG file.
103+
> - Mac Terminal can be used to lookup and confirm the included app details of an installed app.
104+
> For example, to look up the bundle ID and build number of Company Portal, run the following:
105+
>
106+
> ```defaults read /Applications/Company\ Portal.app/Contents/Info CFBundleIdentifier```
107+
>
108+
> Then, run the following:
109+
>
110+
> ```defaults read /Applications/Company\ Portal.app/Contents/Info CFBundleVersion```
111+
>
112+
> - Alternatively, the `CFBundleIdentifier` and `CFBundleVersion` can be found under the ```<app_name>.app/Contents/Info.plist``` file of a mounted DMG file on a Mac.
113+
114+
## Step 4 – Select scope tags (optional)
115+
116+
You can use scope tags to determine who can see client app information in Intune. For full details about scope tags, see [Use role-based access control and scope tags for distributed IT](../fundamentals/scope-tags.md).
117+
1. Click Select scope tags to optionally add scope tags for the app.
118+
2. Click Next to display the Assignments page.
119+
120+
## Step 5 - Assignments
121+
122+
1. Select the **Required group assignments** for the app. For more information, see [Add groups to organize users and devices](../fundamentals/groups-add.md) and [Assign apps to groups with Microsoft Intune](../apps/apps-deploy.md).
123+
2. Click **Next** to display the **Review + create** page.
124+
125+
## Step 6 – Review + create
126+
127+
1. Review the values and settings you entered for the app.
128+
2. When you are done, click **Create** to add the app to Intune.
129+
The **Overview** pane for the macOS DMG app is displayed.
130+
131+
The app you have created appears in the apps list where you can assign it to the groups you choose. For help, see [How to assign apps to groups](../apps/apps-deploy.md).
132+
133+
> [!NOTE]
134+
> If the *.dmg* file contains multiple apps, then Microsoft Intune will only report that the app is successfully installed when all installed apps are detected on the device.
135+
136+
## Next steps
137+
138+
- The app you have created is displayed in the apps list. You can now assign it to the groups you choose. For help, see [How to assign apps to groups](apps-deploy.md).
139+
- Learn more about the ways in which you can monitor the properties and assignment of your app. For more information, see [How to monitor app information and assignments](apps-monitor.md).
140+
- Learn more about the context of your app in Intune. For more information, see [Overview of device and app lifecycles](../fundamentals/device-lifecycle.md)
141+
142+
## Known issues
143+
144+
- **"Uninstall" and "Available for enrolled devices" assignment types are not available**: only "Required" assignment type is currently supported.
145+
- **"Collect logs" action is unavailable during preview**: log collection feature on macOS apps (DMG) is unavailable during preview.
146+
- **Errors might not show details during preview**: some errors you encounter may only show "Failed" status with an error code and not provide additional details.
147+
- **App upgrade fails to install**: Updating an app that has the same bundle ID as an existing app in Applications folder fails to install.
148+
- **DMG apps report once after deployment**: Assigned DMG apps report back on initial deployment only. These apps will not report back again during preview.
149+
- **Some DMG apps may display a warning to end-users on launch**: Apps downloaded from the internet and deployed using Intune may show a warning to end-users when launched. End-users can click "Open" on the dialog to continue opening the app.
150+
151+
![DMG apps may display a warning to end-users on launch](./media/lob-apps-macos-dmg/lob-apps-macos-dmg-01.png)
152+
153+
- **Some app icons may not display immediately after installation**: some app icons may take some time after installation to start displaying on the installed device.
154+
- **Monitoring reports only show error code**: failed app installations only show an error code in "device status" monitoring reports. To show error details, refresh the browser window or refer to the table in the Troubleshooting section.
155+
156+
157+
## Troubleshooting
158+
159+
macOS app installation may not be successful due to any of the following reasons provided in the table below. To resolve these errors, follow the remediation steps. If the app remains assigned, failed installations are retried at the next agent check-in.
160+
161+
| Error code | Error message | Remediation steps |
162+
|------------|---------------|-------------------|
163+
| 0x87D30137 | The device doesn't meet the minimum OS requirement set by the admin. | Update macOS to the minimum OS version required by the admin. |
164+
| 0x87D3013E | The DMG file doesn't contain any supported app. It must contain at least one .app file. | Ensure that the uploaded file contains one or more .app files. |
165+
| 0x87D30139 | The DMG file couldn't be mounted for installation. Check the DMG file if the error persists. | Try manually mounting the DMG file to verify that the volume loads successfully. |
166+
| 0x87D3013B | The app couldn't be installed to the Applications directory. Sync the device to retry installing the app. | Ensure that the device can install apps locally to the Applications directory. |
167+
| 0x87D3012F, 0x87D30130, 0x87D30133, 0x87D30134, 0x87D30136,| The app couldn't be installed due to an internal error. Contact Intune support if the error persists. | Something went wrong while installing the app using Intune. Try installing the app manually or try creating a new macOS app profile containing the app. Contact Intune support if the error persists. |
168+
| 0x87D30131, 0x87D30132 | The app couldn't be downloaded. Sync the device to retry installing the app. | Something went wrong while downloading the app. This may happen if the network is poor or the app size is large. |
169+
| 0x87D30135 | The app couldn't be installed due to a device error. Sync the device to retry installing the app. | This could be due to insufficient disk space or the app could not be written to the folder. Ensure that the device can install apps to the Applications folder. |

0 commit comments

Comments
 (0)