Skip to content

Commit 1b724e4

Browse files
authored
removing references to intunemac
removing references to intunemac
1 parent a263970 commit 1b724e4

1 file changed

Lines changed: 3 additions & 41 deletions

File tree

memdocs/intune/apps/lob-apps-macos.md

Lines changed: 3 additions & 41 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ ms.collection:
3636

3737
[!INCLUDE [azure_portal](../includes/azure_portal.md)]
3838

39-
Use the information in this article to help you add macOS line-of-business apps to Microsoft Intune. You must download an external tool to pre-process your *.pkg* files before you can upload your line-of-business file to Microsoft Intune. The pre-processing of your *.pkg* files must take place on a macOS device.
39+
Use the information in this article to help you add macOS line-of-business apps to Microsoft Intune.
4040

4141
> [!NOTE]
4242
> Starting with the release of macOS Catalina 10.15, prior to adding your apps to Intune, check to make sure your macOS LOB apps are notarized. If the developers of your LOB apps did not notarize their apps, the apps will fail to run on your users' macOS devices. For more information about how to check if an app is notarized, visit [Notarize your macOS apps to prepare for macOS Catalina](https://techcommunity.microsoft.com/t5/Intune-Customer-Success/Support-Tip-Notarizing-your-macOS-apps-to-prepare-for-macOS/ba-p/808579).
@@ -45,42 +45,6 @@ Use the information in this article to help you add macOS line-of-business apps
4545
>
4646
> While users of macOS devices can remove some of the built-in macOS apps like Stocks, and Maps, you cannot use Intune to redeploy those apps. If end users delete these apps, they must go to the app store, and manually re install them.
4747
48-
## Before your start
49-
50-
> [!NOTE]
51-
> Using the Intune App Wrapping Tool for Mac is not required when uploading *.pkg* files.
52-
53-
You must download an external tool, mark the downloaded tool as an executable, and pre-process your *.pkg* files with the tool before you can upload your line-of-business file to Microsoft Intune. The pre-processing of your *.pkg* files must take place on a macOS device. Use the Intune App Wrapping Tool for Mac to enable Mac apps to be managed by Microsoft Intune.
54-
55-
> [!IMPORTANT]
56-
> The *.pkg* file must be signed using "Developer ID Installer" certificate, obtained from an Apple Developer account. Only *.pkg* files may be used to upload macOS LOB apps to Microsoft Intune. However, conversion of other formats, such as *.dmg* to *.pkg* is supported. For more information about converting non-pkg application types, see [How to deploy DMG or APP-format apps to Intune-managed Macs](https://techcommunity.microsoft.com/t5/intune-customer-success/how-to-deploy-dmg-or-app-format-apps-to-intune-managed-macs/ba-p/1503416).
57-
58-
1. Download the [Intune App Wrapping Tool for Mac](https://github.com/msintuneappsdk/intune-app-wrapping-tool-mac).
59-
60-
> [!NOTE]
61-
> The **Intune App Wrapping Tool for Mac** must be run on a macOS machine.
62-
63-
2. Mark the downloaded tool as an executable:
64-
- Start the terminal app.
65-
- Change the directory to the location where `IntuneAppUtil` is located.
66-
- Run the following command to make the tool executable:<br>
67-
`chmod +x IntuneAppUtil`
68-
69-
3. Use the `IntuneAppUtil` command within the **Intune App Wrapping Tool for Mac** to wrap *.pkg* LOB app file from a *.intunemac* file.<br>
70-
71-
Sample commands to use for the Microsoft Intune App Wrapping Tool for macOS:
72-
> [!IMPORTANT]
73-
> Ensure that the argument `<source_file>` does not contain spaces before running the `IntuneAppUtil` commands.
74-
75-
- `IntuneAppUtil -h`<br>
76-
This command will show usage information for the tool.
77-
78-
- `IntuneAppUtil -c <source_file> -o <output_directory_path> [-v]`<br>
79-
This command will wrap the *.pkg* LOB app file provided in `<source_file>` to a *.intunemac* file of the same name and place it in the folder pointed to by `<output_directory_path>`.
80-
81-
- `IntuneAppUtil -r <filename.intunemac> [-v]`<br>
82-
This command will extract the detected parameters and version for the created *.intunemac* file.
83-
8448
## Select the app type
8549

8650
1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
@@ -91,12 +55,12 @@ You must download an external tool, mark the downloaded tool as an executable, a
9155
## Step 1 - App information
9256

9357
> [!NOTE]
94-
> The **minimum operating system** for uploading a *.pkg* file is macOS 10.14. Upload a *.intunemac* file to select an older minimum operating system.
58+
> The **minimum operating system** for uploading a *.pkg* file is macOS 10.14.
9559
9660
### Select the app package file
9761

9862
1. In the **Add app** pane, click **Select app package file**.
99-
2. In the **App package file** pane, select the browse button. Then, select an macOS installation file with the extension *.intunemac* or *.pkg*.
63+
2. In the **App package file** pane, select the browse button. Then, select an macOS installation file with the extension *.pkg*.
10064
The app details will be displayed.
10165
3. When you're finished, select **OK** on the **App package file** pane to add the app.
10266

@@ -152,8 +116,6 @@ The app you have created appears in the apps list where you can assign it to the
152116

153117
[!INCLUDE [shared-proc-lob-updateapp](../includes/shared-proc-lob-updateapp.md)]
154118

155-
To update a line-of-business app deployed as a *.intunemac* file, you must increment the package `version` and `CFBundleVersion` string in the *packageinfo* file in your *.pkg* file.
156-
157119
To update a line-of-business app deployed as a *.pkg* file, you must increment the `CFBundleShortVersionString` of the *.pkg* file.
158120

159121
Intune will update the app when this schedule elapses, provided that any previous version of the app is still present on the device.

0 commit comments

Comments
 (0)