Airwatch catalog allows the admin to deploy applications from enterprise applications, Saas applications, and app store remotely and centrally to all endpoint devices. The endpoint users can access applications from the application catalog with a one-touch single sign-on.

Introduction

Earlier, following up with users to download a particular app and constantly reminding them of the same was a hectic task. The users were required to create multiple IDs and passwords and were required to remember them. Upgrading applications and devices was a hectic task, done individually for every user.

Airwatch catalog allows mass deployment of enterprise apps, Saas apps, or apps from the app store to an individual or group endpoint user devices. Patchwork can be deployed for all devices, allowing mass up-gradation of all enrolled devices in one go. Users can simply access all applications with Single-touch sign-on without the need to connect to VPN. The apps can be internal, public(free), public(paid), web, purchased VPP or purchased custom apps. The deployment features vary for different devices and platforms. The endpoint devices can be personal or corporate-owned. A secure workplace is created for all employees, thus boosting productivity and creativity among them.

What is Airwatch Catalog

The admin can deploy an app catalog so endpoint device users can access enterprise applications managed in the Workspace ONE UEM console. Two app catalogs are offered Workspace ONE UEM: Workspace ONE and the AirWatch catalog. The features in the Apps Settings of the Workspace ONE UEM console are supported in both catalogs. Integrate resources from environments that use Workspace ONE UEM and workspace ONE UEM in the Workspace ONE catalog. Access the features previously released for the AirWatch catalog even if deployment does not use Workspace ONE UEM. Navigate to Workspace ONE UEM console. Go to Groups & Settings. Click All Settings and select Apps. Click on Workspace ONE to highlight the Workspace ONE catalog. The AirWatch catalog is supported under the Workspace ONE title options. The options under the AirWatch catalog are not necessary for the Workspace ONE catalog and apply specifically to it. Workspace ONE and the AirWatch catalog, brief descriptions of the options available for both, and those options that apply specifically to the AirWatch catalog are described below:

Common catalog settings

• Application Categories: Identify Group applications used with custom application categories
• Paid Public Applications: In situations not feasible to use Apple’s Volume Purchase Program (VPP), deploy paid public iOS applications.
• App restrictions: Restrict installations of only assigned applications approved by the organization to restrict iOS devices older than iOS 9
• External App Repository: To host internal applications on the enterprise network with an external application repository, enable an external app repository, and manage the applications with Workspace ONE UEM.
• Application Removal Protection: To control the deployment of applications removal commands for important internal applications, configure threshold values.

AirWatch Catalog Specific Settings

• AirWatch catalog under the standalone catalog: The standalone catalog has limited features and is configured for non-MDM functionality environments.
• AirWatch Catalog under Feature Applications: In the AirWatch catalog, view featured applications in a prominent place.
• AirWatch Catalog under General: General settings for the AirWatch catalog can be configured.

From AirWatch Catalog to Workspace ONE Transition Behavior

Many AirWatch catalog features in previous releases change, as Workspace ONE UEM is migrated to the Workspace ONE catalog. The option for an added Web Clips profile shown in the AirWatch catalog was editable. The Show in App, catalog / Container feature is not editable in some Workspace ONE UEM versions. The catalog displays all Web Clips in the Workspace ONE catalog, no matter what configured settings are applied for Show in App catalog / Container. Saving the Web Clips is reflected in the AirWatch catalog if the AirWatch catalog is used.

VMware AirWatch Catalog to Workspace ONE Catalog Migration

The Workspace ONE app catalog is the repository of all the resources that the admin can deploy to the users when AirWatch and Workspace ONE UEM are integrated. Enterprise applications managed in the Workspace ONE catalog can be accessed by end-users based on the settings established by the admin for the application. Migrate customers from the legacy VMware AirWatch catalog to Workspace ONE catalog with the AirWatch administrator.

Before the migration following steps needs to be followed:

• Configure the integration between Workspace ONE UEM and AirWatch by logging into the Workspace ONE UEM.
• The AirWatch Application for Enterprise Key-Value Pairs needs to be configured.
• The Mobile Single Sign-in Authentication for Android devices and AirWatch-Managed iOS devices needs to be configured.

Add Workspace ONE as a public application from an App store by manually pushing Workspace ONE as a managed application.

In the Groups & Settings menu, disable the AirWatch catalog.

Creating an AirWatch Mobile Application Catalog Item

The admin can use the New catalog item wizard when the App Portal is connected to an AirWatch instance to create a mobile application catalog item Google Android or Apple iOS apps. All iOS and Android mobile apps can be associated with an App Portal catalog item and made available in App Portal, both internal and public store, by configuring on the connected AirWatch instance.

To accommodate different operating systems and devices, the admin can add multiple mobile application versions. Workspace One UEM does not offer a standalone catalog for the Windows Desktop and macOS devices to the same catalog item. The following versions of the same mobile app could be contained in a single catalog item named XYZ Application:

• XYZ Application / iOS iPhone Version
• XYZ Application / iOS iPad Version
• XYZ Application / Android Version

The version appropriate to the user’s registered device will be delivered when the end-user requests the XYZ mobile application.

Note: A mobile application can be linked to its corresponding desktop version so that end-users requesting anyone will be shown the option to opt for others as well. Users are not shown any mobile applications displayed on the Browse Catalog tab if a user does not have a registered mobile device. Also, if a user has only Android mobile devices registered, iOS-only mobile applications are not shown on the Browse Catalog tab for that user, and vice versa.

For creating an AirWatch mobile application catalog item:

1. App Portal must be connected to an AirWatch instance before proceeding further.
2. Navigate to Catalog Management, click on New Catalog Item Wizard. Under the New Catalog Item Wizard, The Catalog Item Type panel opens.
3. Click on AirWatch Mobile Application Catalog Item and select Next. The panel for AirWatch Mobile Application Catalog Item Type opens.
4. From the list of available platforms, select the platform of the mobile application the admin wants to add to this catalog item: iOS Application, Android Application, or both.
5. Select Next. If the admin selected the iOS application, the iOS Applications panel would open, listing all iOS applications on the AirWatch instance.
6. The iOS application that the admin wants to add is selected. Click on next if the admin selected Android Application on the AirWatch Mobile Application Catalog Item Type panel, the panel for Android applications.
7. The iOS mobile application that the admin wants to associate with this new catalog item is selected.
8. Navigate to Supported Devices, click on iPhone or iPad to view the devices that this mobile application supports.
9. Selecting the Next button opens the Catalog Item Title and Category panel.
10. A title has to be entered to identify this catalog item in the App Portal storefront under the Title section. By default, the name of the package or application the admin has selected is listed in this field.
11. A category has to be selected to specify this catalog item’s location in the App Portal catalog under the category field. The admin is required to select at least one category but may select more than one if required.
12. The text that the admin wants to display under the catalog item, Title, is entered In the Brief Description field in the App Portal storefront (when viewed in list view).
13. A generic icon is associated with this catalog item by default. A custom icon can be associated with this catalog item by navigating to Change to open the Image Selection dialog box and select a .jpg, .png or .gif, icon file.
14. Single words that an end-user might use have to be entered, in the Search Keywords text box, when searching for this catalog item.
15. A longer description of this catalog item is entered in the Full Description text area, and the items on the toolbar are used to format it.

Under the Title, Brief Description, and Full Description fields, the text entered will be displayed as follows:

Title: When viewing this catalog item on the Browse Catalog tab, the text entered in the Title field along with the catalog item icon will be shown.

Brief Description: The brief description will also be visible when viewing catalog items in list view.

Full description: When a catalog item is viewed in its detail view, the text entered in the Full Description field will be displayed, either the list or card view, opened by clicking on the catalog item name.

1. Select Next after finishing editing the fields on the Catalog Item Title and Category panel. The panel Ready to Create opens.
2. To immediately open this catalog item’s Catalog Item Properties dialog box, after this catalog item is created, where the admin can specify advanced settings, select the Load advanced display after creating the catalog item option.
3. Click Create to create this new catalog item after reviewing the summary information. The catalog item will now be listed under the Browse Catalog tab in the category the admin selected.

Basic and advanced settings on the Catalog Item Properties dialog box can be edited after creating a catalog item.

Installing your Application from the Airwatch Catalog

Installation of applications from the AirWatch catalog on devices works in specific ways. For instance. Push notifications are used to install some applications on a device while other applications install silently. Installation is dependent on the platform type of the device, whether the device uses a standard standalone catalog or the AirWatch catalog, and the type of application. The device behaviors must be reviewed, and devices display the application prompts and messages when users install applications.

Platform Specific Device Modes

Brief explanations for Android devices and Apple iOS modes are reviewed.

• Apple iOS:

Supervised: Extra management features created by Apple iOS specifically for devices in supervised mode benefit them. Enhance Workspace ONE UEM management capabilities with these iOS management features.

Non-supervised: Workspace ONE UEM can manage and secure these devices but does not support the specific Apple iOS management features offered by supervised mode.

• Android:

Enterprise: The silent installation, uninstallation, and silent activity are supported if the device manufacturer supplies a compatible API. Enterprise Android devices are supported by Workspace ONE UEM when Workspace ONE UEM is supplied with the necessary APIs to perform silent processes. Internal applications only can be silently installed and uninstalled.

Standard: Silent activity is not supported. However, Workspace ONE UEM can secure these devices and can manage these devices.

Device Behavior of Installed Applications from the AirWatch Catalog

When the admin pushes an application from the Workspace ONE UEM console to a device that has an AirWatch catalog, the following general device and application behavior is observed by end-users:

1. Apple iOS Supervised:

• Internal: The app is installed silently. The user is taken from the App Catalog to the app home screen by the device.
• Public, free: The app installs silently in the background while the App Catalog stays open.
• Public, Paid: The users are directed to the app store to get the app by the App Catalog.
• Purchased, VPP: The app installs silently in the background while the App Catalog stays open.
• Web: The app installs silently in the background while the App Catalog stays open.

2. Apple iOS Unsupervised device:

• Internal: A notification is received about the app by the device.
• Public, free: A notification is received about the app by the device.
• The public paid: The users are directed to the app store to get the app by the App Catalog.
• Purchased, VPP: The device receives a notification about the app.
• Web: The app installs silently in the background while the App Catalog stays open.

3. Android(Legacy):

• Internal: The app is installed silently. The user does not leave the App Catalog while the app installs in the background.
• Public(Free): The user is directed to the app store to get the app by the App Catalog.
• Public(Paid): The user is directed to the app store to get the app by the App Catalog.
• Purchased, VPP: Not applicable.
• Web: In the bookmark profile in the Console, Enable Add to Homescreen option. The device displays message that Shortcut Web Clips created, and the device does not leave the App Catalog when the user installs the app. In the bookmark profile in the Console, Disable Add to Homescreen option. The bookmark to the native browser is installed silently.

4. Android Standard Device:

• Internal: Attempts are made by the app to install. The device takes the user to the Managed Apps section of the Workspace ONE Intelligent Hub.
• Public(Free): The user is directed to the app store to get the app by the App Catalog.
• Public(Paid): The user is directed to the app store to get the app by the App Catalog.
• Purchased, VPP: Not applicable.
• Web: In the bookmark profile in the Console, Enable Add to Homescreen option. The device displays message that Shortcut Web Clips created, and the device does not leave the App Catalog when the user installs the app. In the bookmark profile in the Console, Disable Add to Homescreen option. The bookmark to the native browser is installed silently.

5. Android:

• Internal: Not applicable as internal apps are treated as public apps by Workspace ONE UEM.
• Public, free: The app is installed silently, and while the app installs in the background, the device does not leave the App Catalog.
• Public, paid: Not applicable.
• Purchased, VPP: Not applicable.
• Web: Not applicable.

6. Windows desktop devices:

• Internal: The app is installed silently, and while the app installs in the background, the device does not leave the App Catalog.
• Public (Free): The user is directed to the app store to get the app by the App Catalog.
• Public(Paid): The user is directed to the app store to get the app by the App Catalog.
• Purchased, VPP: Not applicable.
• Web: The app is installed silently, and while the app installs in the background, the device does not leave the App Catalog.

7. macOS:

• Internal: The app is installed silently, and while the app installs in the background, the device does not leave the App Catalog.
• Public (Free): Not Applicable.
• Public (Paid): Not Applicable
• Purchased, VPP: While the app installs silently in the background, the App Catalog stays open.
• Web: The app is installed silently, and while the app installs in the background, the device does not leave the App Catalog.

Installed Applications Device Behavior from the Standalone Catalog

The general device and application behavior end users see when the admin pushes an application from the Workspace ONE UEM console to a standalone catalog device is described in the following section. A standalone catalog for the Windows Desktop and macOS devices is not offered by Workspace One UEM. The platform-specific device mode does not apply as applications in a standalone catalog are unmanaged.

1. Apple iOS Device:

• Internal: A notification about the app is received by the device.
• Public, free: The user is directed to the app store to get the app by the app catalog.
• Public, paid: The user is directed to the app store to get the app by the app catalog.
• Purchased, VPP – Redemption Codes: The user is directed to the app store to get the app by the app catalog.
• Web: To install the web clip profile for the app, a device prompt is shown to redirect the users.

2. Android Devices:

• Internal: The app is downloaded in the Download folder on the device. To install the app, users must go to the Download folder.
• Public, free: The user is directed to the app store to get the app by the app catalog.
• Public, paid: The user is directed to the app store to get the app by the app catalog.
• Purchased, VPP – Redemption Codes: Not applicable.
• Web: The Console does not add the bookmark to the native browse, and the app opens in the native browser.

Application Messages in the App Catalog

The end-users general messages when the admin pushes applications from the Workspace ONE UEM console to a device with the App Catalog are described in the following section. Workspace ONE UEM displays the price and size of the available application from the app store(if applicable), and these values are displayed in the form of a message.

1. Apple iOS Supervised Device:

• Internal: The download begins automatically. The user is taken out of this catalog to the home screen on the device.
• Public, free: The app appears on the user’s device after being downloaded automatically.
• Public, paid: The user is redirected to the app store to download the app.
• Purchased, Custom Apps: The user is redirected to the app store to download the app.
• Purchased, VPP: The app appears on the user’s device after being downloaded automatically.
• Web: The app appears on the user’s device after being downloaded automatically.

2. Apple iOS Unsupervised Device:

• Internal: A push notification to continue installation is received on the user device.
• Public, free: A push notification to continue with installation is received on the user device.
• Public. Paid: The user is redirected to the app store to download the app.
• Purchased, Custom Apps: The user is redirected to the app store to download the app.
• Purchased, VPP: A push notification to continue with installation is received on the user device.
• Web: The app appears on the user’s device after being downloaded automatically.

3. Android Enterprise Device:

• Internal: The app appears on the user’s device after being downloaded automatically.
• Public, free: The user is redirected to the app store to download the app.
• Public. Paid: The user is redirected to the app store to download the app.
• Purchased, Custom Apps: Not applicable.
• Purchased, VPP: Not applicable.
• Web: In the bookmark profile in the console, enable Add to Homescreen option. The app appears on the user’s device after being downloaded automatically. A bookmark in the user’s native browser appears for the web app.

4. Android Standard Device:

• Internal: To continue with the installation, under the Workspace ONE Intelligent Hub, tap the notification that appears in the Managed Apps section.
• Public, free: The user is redirected to the app store to download the app.
• Public. Paid: The user is redirected to the app store to download the app.
• Purchased, Custom Apps: Not applicable.
• Purchased, VPP: Not applicable.
• Web: In the bookmark profile in the console, enable Add to Homescreen option. The app appears on the user’s device after being downloaded automatically. A bookmark in the user’s native browser appears for the web app.

5. Android For Work:

• Internal: Workspace ONE UEM treats internal apps as public apps, so Not applicable.
• Public, free: The app appears on the user’s device after being downloaded automatically.
• Public. Paid: Not applicable.
• Purchased, Custom Apps: Not applicable.
• Purchased, VPP: Not applicable.
• Web: Not applicable

6. Windows Desktop Device:

• Internal: The app appears on the user’s device after being downloaded automatically.
• Public, free: The user is redirected to the app store to download the app.
• Public, paid: The user is redirected to the app store to download the app.
• Purchased, Custom Apps: Not applicable.
• Purchased, VPP: Not applicable.
• Web: The app appears on the user’s device after being downloaded automatically.

7. Mac OS:

• Internal: The app appears on the user’s device after being downloaded automatically.
• Public, free: Not applicable.
• Public, paid: Not applicable.
• Purchased, Custom Apps: Not applicable.
• Purchased, VPP: The app appears on the user’s device after being downloaded automatically.
• Web: The app appears on the user’s device after being downloaded automatically.

Application Messages in the Standalone Catalog

When the admin pushes applications from the Workspace ONE UEM console to an unmanaged device with the standalone catalog, Workspace One UEM does not offer a standalone catalog for the Windows Desktop and macOS devices catalog. When this happens, the following general messages are displayed to end-users as described in this section. Workspace ONE UEM displays the price and size of the application are available from the app store. These values are displayed in the form of messages. The Workspace ONE UEM does not offer a standalone catalog for Windows desktop and macOS devices.

1. Apple iOS Supervised Devices:

• Internal: With the installation, a push notification is received.
• Public, free: Users are redirected to the app store.
• Public, paid: Users are redirected to the app store to download the app.
• Purchased, Custom Apps: Users are redirected to the app store to download the app.
• Purchased, VPP: Users are redirected to the app store to download the app.
• Web: Tap on the profile installation prompt to install the application that appears when the user continues.

2. Apple iOS Unsupervised Devices

• Internal: A push notification is received to continue with the installation.
• Public, free: Users are redirected to the app store
• Public, paid: To download the app, users are redirected to the app store
• Purchased, Custom Apps: Users are redirected to the app store to download the app.
• Purchased, VPP: Users are redirected to the app store to download the app.in the form of
• Web: Tap on the profile installation prompt to install the application that appears when the user continues.

3. Android Enterprise Devices:

• Internal: The file is downloaded and available to install in the downloads folder on the user device.
• Public, free: Users are redirected to the app store
• Public, paid: To download the app, users are redirected to the app store
• Purchased, Custom Apps: Not Applicable
• Purchased, VPP: Not available.
• Web: In the user’s native browser, the user is taken to the web app.

4. Android Standard Device:

• Internal: The file is downloaded and available to install in the downloads folder on the user device.
• Public, free: Users are redirected to the app store
• Public, paid: To download the app, users are redirected to the app store
• Purchased, Custom Apps: Not Applicable
• Purchased, VPP: Not available.
• Web: In the user’s native browser, the user is taken to the web app.