Understanding Managed Apps in Jamf School
When an app is managed by Jamf School, you have more control over distribution and removal of the app, as well as the backup of app data and options for updating the app. The following table provides more detail:
|
|
Unmanaged apps |
Managed apps |
|
Distribution Methods |
|
|
|
Make available in Jamf Teacher |
|
|
|
Make available in Jamf School Student |
|
|
|
Prompt users to install |
|
|
|
Removal Options |
|
|
|
Remove from Jamf Teacher |
|
|
|
Remove from Jamf School Student |
|
|
|
Remove from mobile devices |
|
|
|
Remove when MDM profile is removed |
|
|
|
Prevent users from removing the app |
|
|
|
Backup of App Data |
|
|
|
Prevent backup of app data |
|
|
|
App Update Options |
|
|
|
Schedule automatic app updates |
|
|
|
Force an app update |
|
|
|
App Validation Options (in-house apps only) |
|
|
|
Schedule automatic app validation |
|
|
|
Force app validation |
|
|
Managed App Requirements
There are two factors that determine whether an app can be managed by Jamf School:
-
Whether users have to pay for the app
The app must be free or purchased in volume. For more information on volume purchasing, see the following Apple documentation: -
The mobile devices to which you distribute the app
Mobile devices must have iOS 5 or later, or tvOS 10.2 or later and an MDM profile that supports managed apps.
Mobile devices that have iOS 5 or later when they are enrolled with Jamf School automatically obtain an MDM profile that supports managed apps.
If you try to make an app managed but these requirements are not met, the app behaves as unmanaged.