When you deploy a
software inventory package to a device, Device Manager maintains the list of
apps. You can work from those lists to configure Applications Access Policies,
also known as application blacklists and whitelists, to manage users' access to
applications on their devices.
You can also use the
Applications Access Policies in the following ways:
Access Policies Types
You can create the
following types of Applications Access Policies:
(blacklist). A list of apps that users cannot install on their
devices. If even one app on device matches an app in the Forbidden list in
Device Manager, the device is considered to be in violation of the policy.
(whitelist). A list of apps that you suggest to users. Users can
have one or more of the apps from the list installed and still be in compliance
with the policy. However, if users install an app that is not listed in the
policy, the user's device is in violation of the policy.
(whitelist). A list of apps that must be installed on the device to
be in compliance with the policy. Users must install all of the apps on the
list. If users do not install any of the apps in the list, the device is in
violation of the policy.
You have the option
in Device Manager of using the App bundle ID and App package name when you
define iOS and Android apps in your policies. Device Manager can identify apps
more reliably, however, when you use these values.
In iOS, an App
bundle ID is traditionally a reverse-domain-name style string used when a
developer creates a new app. For example, for Angry Birds (www.rovio.com/), the
App bundle ID on iOS is 'com.rovio.angrybirds'. On Android, an App package
naming convention is similar to iOS, in which the developer identifies the app
with a reverse-domain-name style string. The last part of the name is the name
of the App package, often with the file extension appended to the end. For
example, for Angry Birds, the App package name on Android is