App Management updates in AirWatch 8.3

App Management updates in AirWatch 8.3

Assume management of user-installed apps - iOS 9+

Prior to AirWatch 8.2, administrators could only assume management of iOS applications if those applications were installed by AirWatch.  In AirWatch 8.3 (and later 8.2 feature packs), administrators can assume management of applications for iOS 9+ devices even if the application was installed manually by the user.  This is supported for public, purchased, and internal iOS applications by adding them to the AirWatch Console and selecting the Make App MDM Managed if User Installed checkbox in the Deployment tab of the app settings.


If these settings are pushed to a device, users of non-supervised devices will be prompted to allow AirWatch to manage the specific applications.  There is built-in retry logic if the application is a required application, similar to normal application installs, that will continue to prompt users to allow management of the specific applications if they were user-installed.  Supervised devices will automatically assume management with no user-prompt.  No application data will be affected or deleted when an application is converted from unmanaged to managed.

However, the privacy settings must be properly configured in order for administrators to be able to distinguish user-installed apps that have been converted to managed.  If the privacy settings are configured to Collect Application Data, then the status of a user-installed application will display as managed once the process is complete.  However, if the privacy settings are set to Do Not Collect Application Data or Collect Application Data but Do Not Display, then the application status will stay as Already Installed in the AirWatch Console.

Android for Work updates

Google is now allowing app developers to leverage the Android for Work SDK to create Android for Work apps that are targeted for older devices that don't fully support Android for Work.  Essentially, these Android for Work apps are targeted for devices that are running < OS 5.0.  However, these applications will follow the standard Android for Work workflow and can also be added the same way as standard public applications.  There is currently no way to automatically distinguish between a public app not using the Android for Work SDK and the version that does use the SDK except for the name of the application itself.  When attempting to add such an application to your deployment, keep in mind that, typically, these applications will add the suffix "for Work" at the end of their name.

AirWatch will identify and differentiate between normal applications that have been imported through Android for Work, these new Android for Work applications, and standard public applications.  Additionally, the same EMM token that is used for Android for Work integration can be leveraged for these Android for Work apps as well.


Have more questions? Submit a request


Article is closed for comments.