The main feature of the Product Provisioning system is creating an ordered installation of profiles, applications, and files/actions into one product to be pushed to devices based on the conditions you create.

Product Provisioning Basics

Once products are created and activated, they are pushed to the device based on the conditions set. Conditions are an optional tool that determines when a product is downloaded and when it is installed. Content and Application provisioning by products can be pushed to devices through optional relay servers.

Products are pushed to devices that are chosen by smart group assignments. These groups control which devices get which product based on how the group is created. For more information on smart groups, see Smart Groups. You can also use Assignment Rules to further target your products to devices.

In addition, you can ensure the product you provision from the console or from an API call is the exact same product that gets received by the device. This product verification is built into the provisioning process; if the product status is Compliant, then the product on the device matches the product provisioned. If file validation discovers a mismatch, the console pushes the content to the device again to ensure compliance between the product and the device. In this way, the product ensures that your devices remain up-to-date.

Important:

You must upload the content of the product before a product can be created.

Profiles for Product Provisioning

The product provisioning system allows you to create profiles for your rugged devices. The profiles created for rugged devices are installed or uninstalled as part of a product. Profiles created under Products ( Devices > Staging & Provisioning > Components > Profiles) are different than those created through the non-products process ( Devices > Profiles). For more information, see Profiles for Product Provisioning.

Files/Actions

You can install, configure, and upgrade devices by assigning files/actions to a product. The files/actions component also contains ways to manage the file system of a device. For more information, see Files/Actions for Products.

Applications

Product provisioning allows you to upload applications to the console for distribution as part of a product. Through product provisioning, you can upgrade and downgrade applications and remove them remotely. For more information, see Application Provisioning.

Product Conditions

A condition determines when the product or OS upgrade package should be downloaded and installed. Conditions are checked when a product is pushed to a device. For more information, see Product Conditions.

Create a Product

After creating the content you want to push to devices, create a product that controls when the content is pushed and the order of installation of the product. For more information, see Create a Product.

Product Persistence

Product Provisioning allows you to enable profiles, files/actions, and applications to remain on a device following an enterprise reset. Content marked to persist following an enterprise reset reinstalls following the device restart after the AirWatch Agent installs. Product Persistence only applies to specific Windows Rugged and Android devices. For more information, see Product Persistence.