NEW WHITEPAPER: VMware AirWatch Product Provisioning Microsoft Office 2016 for macOS Best Practices

This post was originally published on this site

The VMware AirWatch Product Provisioning Office 2016 for macOS document is now available!   This white paper provides configuration best practices for provisioning Microsoft Office 2016 zmacOS.  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.

VMware-AirWatch-Product-Provisioning

Document Overview

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

Introduction

The introduction starts by introducing VMWare AirWatch and the Product Provisioning feature and how it helps with deploying large or complex non-Appstore 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.  By using the custom attribute, you can determine any exclusions for product assignment and prevent re-install over top of devices where the app was installed out-of-band by the user.

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 the Product creation process in a step-by-step manner.   The product references all the individual application files and actions, along with a manifest that lays out the order of operations.   Product provisioning deploys these files and performs the actions on the managed device, allowing you to install non-Appstore applications on managed macOS devices.

To comment on this paper, contact VMware End-User-Computing Technical Marketing at euc_tech_content_feedback@vmware.com.

The post NEW WHITEPAPER: VMware AirWatch Product Provisioning Microsoft Office 2016 for macOS Best Practices appeared first on VMware End-User Computing Blog.

Leave a Reply

Your email address will not be published. Required fields are marked *