Mar 25, 2021 Windows application size is capped at 8 GB per app. Convert the Win32 app content. Use the Microsoft Win32 Content Prep Tool to pre-process Windows classic (Win32) apps. The tool converts application installation files into the.intunewin format. The tool also detects some of the attributes that Intune requires to determine the application.
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.
Note
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.
macOS LOB apps have a maximum size limit of 2 GB per app.
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.
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.
Important
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.
Download the Intune App Wrapping Tool for Mac.
Note
The Intune App Wrapping Tool for Mac must be run on a macOS machine.
Mark the downloaded tool as an executable:
IntuneAppUtil
is located.chmod +x IntuneAppUtil
Use the IntuneAppUtil
command within the Intune App Wrapping Tool for Mac to wrap .pkg LOB app file from a .intunemac file.
Sample commands to use for the Microsoft Intune App Wrapping Tool for macOS:
Important
Ensure that the argument <source_file>
does not contain spaces before running the IntuneAppUtil
commands.
IntuneAppUtil -h
This command will show usage information for the tool.
IntuneAppUtil -c <source_file> -o <output_directory_path> [-v]
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>
.
IntuneAppUtil -r <filename.intunemac> [-v]
This command will extract the detected parameters and version for the created .intunemac file.
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.
Review the values and settings you entered for the app.
When you are done, click Create to add the app to Intune.
The Overview blade for the line-of-business app is displayed.
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.
Note
If the .pkg file contains multiple apps or app installers, then Microsoft Intune will only report that the app is successfully installed when all installed apps are detected on the device.
Note
For the Intune service to successfully deploy a new .pkg file to the device you must increment the package version
and CFBundleVersion
string in the packageinfo file in your .pkg package.
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.
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.
Learn more about the context of your app in Intune. For more information, see Overview of device and app lifecycles
In the first blog about the Microsoft Intune App-layer protection, one of the supported features is that you are able to wrap your own applications with the Microsoft Intune App Wrapping Tool for iOS so that you are able to manage those applications with the Mobile Application Management policies. In this second blog in the series, we will have a look at the Microsoft Intune App Wrapping Tool for iOS.
With this blog I want to show two scenarios. One with an application with no policies active and one with the same application that is wrapped with the Microsoft Intune App Wrapping Tool with the mobile application policies active. To be able to do this I have created a very basic application with two “pages” and on each page, there is a text field where I can type text and copy and paste it within the application and beyond.
Meet Notepad 🙂
Page 2 of Notepad |
Again it is a very basic and uggly app, but it does its work 🙂 (Okay I will try to make it more fancy 😉 )
That being said, when looking at the Microsoft Intune App Wrapping Tool for iOS, you need to be sure that the following prerequisites are in place:
Unmanaged Application
So when deploying the standard application via Microsoft Intune, you are able to install it and copy and paste the “Super secret text” between the pages in the Notepad application and for instance the email application within the iOS device.
Create a managed application
So the default created application can be deployed without any problem. What we need to do next is to wrap the Notepad application with the Microsoft Intune App Wrapping Tool to allow management via Microsoft Intune.
You can download the Microsoft Intune App Wrapping Tool for iOS supporting the right language here. Next you need to extract the DMG file to a folder where you are able to access the IntuneMAMPackager tool, TechNet describes to start the command line tool like this ./IntuneMAMPackager.app/Contents/MacOS/IntuneMAMPackager but I also extracted the content from the file to be able to access the IntuneMAMPackager file directly.
The IntuneMAMPackager tool has the following parameters that you may need to add to be able to wrap your application.
Parameter | Description |
-i | The path and file name of the source application. (mandatory) |
-o | The path in which to save the wrapped application. (mandatory) |
-p | The path of your provisioning profile for iOS applications. (mandatory) |
-c | The SHA1 hash of the signing certificate (Optional). |
-a | The Client ID of the input app (in GUID format) if the app uses Azure Active Directory Libraries (Optional). |
-t | The path to a test mobile application management policy file for testing outside of Intune (Optional). |
-r | Redirect URI of the input app if the app uses Azure Active Directory Libraries (Optional). |
-v | Verbose messages while wrapping the application. |
For my Notepad application I need to start the following command line at the console of the Mac OS X device;
./IntuneMAMPackager –i ./Notepad-v1.ipa –p XC_Ad_Hoc_.mobileprovisioning –o ./Notepad- wrapped.ipa –c 679cd10b63499c3f89c6edfb07d2e2b80dfb0d
Application wrapped by the Microsoft Intune App Wrapping Tool
That you cannot wrap every IPA file is true since the wrapping tool cannot wrap the following apps;
Trying to wrap an app that is not signed by Apple
In the next blog we will add the application to Microsoft Intune, deploy it and have a look how the Mobile Application Management Policies can be applied to the managed application.
Till next time.