Be the first to hear the latest EUC news. Enter your email to join.

[Whitepaper] Product Provisioning Microsoft Office 2016 for macOS Best Practices

Robert Terakedis

Author: Robert Terakedis

Robert is a solutions architect for VMware End-User Computing (EUC).

Share This Post On

The VMware AirWatch Product Provisioning Office 2016 for macOS document is now available!   This whitepaper provides configuration best practices for provisioning Microsoft Office 2016 for macOS.  VMware AirWatch product features that can help you. Using easy-to-follow steps and screenshots, it walks you through leveraging custom settings XML, custom attributes, files, actions, and products.   Concepts demonstrated in this white paper can be extended to deploy additional non-AppStore applications from other 3rd party software vendors.


Product Provisioning Office 2016 for macOS Overview

Each section contains screenshots and descriptions to help you understand the features and how to leverage them:


The guide kicks off with an introduction of VMWare AirWatch and the Product Provisioning feature. Then it explains the value of product provisioning, promoting it as a solution for large or complex deployments of non-store applications.  It also lays out the use-case parameters for which the document illustrates a solution.

Skip Splash Screens with Custom Settings XML

The next section describes how to skip the first-run splash screens by delivering custom settings XML to macOS devices.  This section demonstrates how to use custom XML to modify configurable parameters supported by an application.

Custom Settings XML Payload for macOS

Custom Settings XML Payload for macOS

Report Devices Running Microsoft Office 2016

In the following section, learn how to create a custom attributes profile payload to control delivery of Office 2016 for macOS.  Use custom attributes to exclude devices with the application already downloaded from product assignment.

Configure Files and Actions for the Product Application Suite

To provision Microsoft Office 2016 to macOS devices, the Office installers must become a product within VMware AirWatch. Files and actions serve as the product’s building blocks. For Product Provisioning, files refer to a literal file, and actions refer to a behavior associated with a specific file.  This section walks you step-by-step through a repeatable process that could be used for other, similar non-Appstore applications.

Files Actions for VMware AirWatch Products

Files and Actions are the building blocks for AirWatch Product Provisioning

Create the Microsoft Office 2016 for Mac Product

The final section of the guide covers product creation process in a step-by-step manner.   Product provisioning deploys files and performs actions on managed devices. This allows you to install non-store applications on managed macOS devices.

To comment on this paper, contact VMware End-User-Computing Technical Marketing at

468 ad