Deploying Third-Party macOS Applications: VMware Workspace ONE Operational Tutorial

VMware Workspace ONE UEM 9.3

Overview

Introduction

VMware provides this operational tutorial to help you with your VMware Workspace ONE®environment. In this tutorial, you enable macOS software management, deploy a macOS application as an internal application, create a custom attributes profile, and create and assign a product to a device.

Audience

This operational tutorial is intended for IT professionals and Workspace ONE administrators of existing production environments. Familiarity with networking and storage in a virtual environment is assumed, including Active Directory, identity management, and directory services. Knowledge of additional technologies such as VMware Identity Manager™ and VMware Workspace ONE® UEM, is also helpful.

Deploying Third-Party macOS Applications as Internal Applications

Introduction

This exercise helps you to deploy third-party macOS applications as internal apps.

Workspace ONE UEM supports a few different methods for delivering software to managed macOS devices. In this section, learn about the software delivery methods that are available, and when each method is appropriate to use.

The following software delivery methods are available for macOS:

  • Apple Business Manager or Apple School Manager — Delivers macOS App Store applications to devices as volume-licensed, purchased applications
  • Software Distribution — Delivers third-party, non-store applications as internal apps in Workspace ONE UEM 9.3 and later. We cover the procedure to deliver third-party macOS applications as internal apps in this exercise. 
  • Product Provisioning — Deploys non-store applications and scripts as products in Workspace ONE UEM (or AirWatch) 9.2 and earlier. We recommend that you use either Apple Business Manager or Software Distribution to deliver software. However, if you encounter issues with software distribution, you can follow the legacy method, which is covered in Deploying Third-Party macOS Applications as Products (Legacy)

The type of software being delivered determines the appropriate delivery method. The following table lists different types of software, and their recommended delivery method.  

  macOS App Store Applications Non-Store Applications
Delivery Method Apple Business Manager Software Distribution
Examples
  • xCode 
  • Slack 
  • Microsoft Remote Desktop
  • Apple's iWork suite
  • TextWrangler
  • F5 Access (VPN)
  • iBooks Author
  • Microsoft OneDrive
  • Microsoft OneNote
  • Quickbooks
  • VMware Tunnel
  • Adobe Creative Suite
  • Microsoft Office 2016 for macOS
  • BlueJeans
  • Camtasia
  • Audacity 
  • Shell scripts, Python scripts

Prerequisites

Before you can perform the procedures in this tutorial, you must satisfy the following requirements. 

  • Apple device running macOS version 10.12.6 (Sierra) or later
  • VMware Workspace ONE UEM Agent for macOS version 3.0 or later
  • Workspace ONE UEM version 9.3 or later

For more information, see the VMware Identity Manager Documentation and VMware Workspace ONE UEM Documentation.

Logging In to the Workspace ONE UEM Console

To perform most of the steps in this exercise, you must first log in to the Workspace ONE UEM Console.

1. Launch Chrome Browser

Launch Chrome Browser

On your desktop, double-click the Google Chrome icon.

3. Authenticate In to the Workspace ONE UEM Console

  1. Enter your Username, for example, administrator.
  2. Click Next. After you click Next, the Password text box is displayed.
  1. Enter your Password, for example, VMware1!
  2. Click Login.

Note: If you see a Captcha, be aware that it is case sensitive.

Enabling macOS Software Management

In this section, you configure file storage and macOS software management settings.

1. Access All Settings

Log in to the Workspace ONE UEM Console as an administrator and view the Global Organization Group:

  1. Select Groups & Settings.
  2. Select All Settings.

2. Enable File Storage

  1. Ensure you are at the Global Organization Group unless your particular setup requires configuring at child Organization Groups.  
  2. Expand Installation.
  3. Select File Path.
  4. Scroll through the file paths pane and select Enabled for File Storage Enabled.
  5. Enter the path of a file share accessible from your Device Services and Console servers.
  6. Select Disabled for File Storage Caching Enabled unless you have planned and sized your Device Services server accordingly.
  7. Select Enabled for File Storage Impersonation Enabled.
  8. Enter the username credentials to impersonate to access the file storage path.
  9. Enter the password for the impersonation user.
  10. Confirm the password for the impersonation user.
  11. Click Test Connection and ensure you see Connection Succeeded.
  12. Click Save.

3. Enable Software Management

In the Settings screen, perform the following steps.

  1. Expand Devices & Users.
  2. Expand Apple.
  3. Expand Apple macOS.
  4. Select Software Management.
  5. Select Override.
  6. Select Enabled for Enable Software Management.
  7. Click Save.
  8. Ensure settings are Saved Successfully.

 

Configuring the Application Catalog

Configure the application catalog for macOS.

1. Open Safari Web Browser

On your macOS device, click the Safari icon on the dock.

2. View Settings

View All Settings

In the Workspace ONE UEM Console:

  1. Select Apps & Books.
  2. Select All Apps & Books Settings.

3. Access Catalog Settings

Enable the Application Catalog
  1. Select Apps.
  2. Expand Workspace ONE.
  3. Expand AirWatch Catalog.
  4. Select General.

4. Enable the Application Catalog

Enable the Application Catalog
  1. Select the Publishing tab.
  2. Select Override.
  3. Enter the Catalog title as App Catalog.

5. Enable macOS Platform

  1. Scroll down until you see the platform macOS.
  2. Select Enabled for macOS.
  3. Click Save.
  4. Scroll to the top and click X to exit the pop-up window.

Preparing macOS Applications for Deployment

In this section, you download the VMware AirWatch Admin Assistant tool and use it to prepare another third-party application for deployment.

1. Open New Browser Tab

On your macOS device, open a new Safari tab.

2. Download Skitch

  1. In Safari, navigate to https://evernote.com/products/skitch.
  2. Click Download for Mac.
  3. Do not download the app from the Mac App Store to complete this exercise.

The zip file for Skitch will download to the Downloads folder.

3. Download VMware AirWatch Admin Assistant Tool

In the same tab as you downloaded Skitch, paste the link to the VMware AirWatch Admin Assistant tool and press Enter: https://awagent.com/AdminAssistant/VMwareAirWatchAdminAssistant.dmg

The DMG file will download to the Downloads folder.

4. Begin VMware AirWatch Admin Assistant Tool Installation

On the dock, perform the following steps:

  1. Click the Downloads folder (next to the Trash).
  2. Click VMwareAirWatchAdminAssistant.dmg.

5. Launch Installer Package

Double-click the VMware AirWatch Admin Assistant.pkg file.

6. Continue Installer

Click Continue.

7. Review and Continue Installer

  1. Review the License Agreement and click Continue.
  2. Click Agree if you agree to the license agreement.

8. Install Admin Assistant Tool

Click Install.

9. Enter Admin Credentials

If prompted for administrative credentials, enter the credentials required to install.

  1. Enter the Administrator as the Admin User Name on the macOS device.
  2. Enter the VMware1! as the password for the admin user.
  3. Click Install Software.

10. Close the Installer

  1. Click Close when the installer completes.
  2. Click Move to Trash to clean up the installer.

11. Prepare VMware Admin Assistant Tool

  1. Click the Launchpad on the Dock.
  2. Click VMware AirWatch Admin Assistant.

12. Drag and Drop Skitch

  1. Click the Downloads folder on the Dock.
  2. Click and HOLD Skitch.
  3. Drag-and-drop Skitch onto the VMware AirWatch Admin Assistant in the box.

The VMware Admin Assistant Tool begins parsing the file to extract information necessary to deploy the software.

13. Monitor Process and Reveal Files

  1. Monitor the progress of the parsing. When it is complete, the wheel changes to a green checkmark.
  2. In the pop-up window, click Reveal in Finder.

14. Review Generated Files

In the Finder window:

  1. Change to Column view.
  2. Note the Path of the Output for the Skitch files:  ~/Documents/VMware AirWatch Admin Assistant/Skitch-2.8.1
  3. Note the output from the Assistant tool as described here:
Skitch-2.8.1.dmg -- The Application has been packaged into a DMG file.   (Note: MPKG and PKG files will not be modified)
Skitch-2.8.1.plist -- A metadata file (referenced as the pkginfo.plist in munki documentation) which contains information used by the munki framework to determine how to install/uninstall the software
Skitch.png -- An icon image extracted from the app used for user-friendly display in the console and Workspace ONE app for macOS

Important: All output for the Admin Assistant tool follows the convention ~/Documents/VMware AirWatch Admin Assistant/{AppName-Version}.  At the time this exercise was created, Skitch was at version 2.8.1.

Deploying a Third-Party macOS Application

In this exercise, deploy Skitch, a third-party macOS application, as an internal application in Workspace ONE UEM.

1. Return to Workspace ONE UEM Console

In Safari, select the tab labeled Devices > Dashboard.

2. View Native Internal Apps

  1. Select Apps & Books.
  2. Expand Applications.
  3. Select Native.
  4. Select Internal.
  5. Select Add Application.

3. Upload the Application File

Click Upload.

4. Choose File

Click Choose File.

5. Select Application File

  1. Choose the Documents folder.
  2. Select VMware AirWatch Admin Assistant.
  3. Select Skitch-{version} (for example, Skitch-2.8.1).
  4. Select Skitch-{version}.dmg.
  5. Click Choose.

6. Save Local File

Click Save.

7. Continue Adding Application

Click Continue.

8. Upload Metadata File

  1. Note the link to directly download the VMware AirWatch Assistant (in case you forgot to generate the metadata file and are working from a computer where the VMware AirWatch Assistant is not installed).
  2. Click Upload.

9. Choose File

Click Choose File.

10. Navigate to Plist File

  1. Choose the Documents folder.
  2. Select VMware AirWatch Admin Assistant.
  3. Select Skitch-{version} (for example, Skitch-2.8.1).

11. Select Plist File

  1. Select Skitch-{version}.plist.
  2. Click Choose.

12. Save Plist File

Click Save.

13. Continue Adding Application

  1. Note the Application File is shown.
  2. Note the Plist File is shown.
  3. Click Continue.

14. Add Image File

  1. Select the Images tab.
  2. Select Click or Drag Files Here.

15. Navigate to Image File

  1. Choose the Documents folder.
  2. Select VMware AirWatch Admin Assistant.
  3. Select Skitch-{version} (for example, Skitch-2.8.1).

16. Select Image File

  1. Select {App Name}.png (for example, Skitch.png).
  2. Click Choose.

17. Review Scripts Tab

  1. Select the Scripts tab.
  2. The Pre-Install Script runs before the Workspace ONE UEM Agent runs the dmg/pkg/mpkg file that installs the application and can be used to set-up prerequisite items before the installer runs. The pre-install script must have an exit code of zero (0) for the install to proceed.
  3. The Post-Install Script runs after the Workspace ONE UEM Agent executes the dmg/pkg/mpkg file. This can be useful for applying configurations after the software completes the installation.
  4. The Pre-Uninstall Script runs before the Workspace ONE UEM Agent initiates the uninstall. The pre-uninstall script must have an exit code of zero (0) for the uninstall to proceed.
  5. The Uninstall Method defines how the Workspace ONE UEM Agent uninstalls software. Typically, Remove Copied Items is used for a DMG installer, and Remove Packages is used for a PKG installer.  
  6. The Post-Uninstall Script provides a method to validate an uninstall was completed and potentially handle any cleanup for the uninstall.
  7. The Install Check script assists the Workspace ONE UEM Agent with determining whether an install needs to happen. This script can be useful for desired state purposes and ensuring that a software install remains intact on a user's machine. If the script has an exit code of zero (0), the agent assumes an Install is needed.
  8. The Uninstall Check Script validates whether an uninstall has occurred. If the script has an exit code of zero (0), the agent determines an uninstall is (or is still) required.

Note: Use the pre and post install scripts to avoid repackaging installers. By including scripts, you can automate tasks that would normally require user input before/after an install.

For more information, see Pre And Postinstall Scripts on the Munki wiki.

Important: Scripts must include the shebang (#!) statement on the first line. Examples include the following:

#!/bin/bash
#!/bin/sh
#!/usr/bin/python

18. Review Deployment Tab

  1. Select the Deployment tab.
  2. Note the different Restart actions.
  3. Note the section to include conditions which can further constrain the deployment.

For more information, see Conditions on the munki wiki.

19. Save and Assign Application

  1. Select Terms of Use.
  2. Review the ability to add terms of use to a software title.  
  3. Click Save & Assign.

20. Open Assignment Settings

Click Add Assignment.

21. Configure Assignment Settings

  1. Select the assignment group associated with your organization group (formatted like your email address).
  2. Select Auto for App Delivery Method.
  3. Select Enabled for Remove on Unenroll.
  4. Click Add.

22. Save and Publish the Application

  1. Ensure your recently added Assignment shows in the list of Assignments.
  2. Click Save & Publish.

23. Publish the Application

Click Publish.

24. Review Published Application Information

Review the newly published application.

Validating Application Install

With the macOS device enrolled, the published application should begin downloading and installing immediately. This exercise helps you to manually validate the application is installing and/or installed.

1. Check the Agent Status

  1. Click the Workspace ONE shield in the menubar.
  2. As the agent processes application installs, you will see a note about Handling Application Updates. Depending on the speed of your connection, the agent may finish processing the install before you have a chance to see the status on the menubar applet.

Note: In a Workspace ONE UEM environment integrated with VMware Identity Manager, the end-user will see more verbose installation feedback from within the macOS native Workspace ONE application. Feedback using this method is outside the scope of this exercise.

2. Launch Terminal

  1. Click the LaunchPad on the Dock.
  2. Enter terminal to filter the LaunchPad apps.
  3. Click Terminal.

3. Review ManagedSoftwareUpdate Log

  1. Tail the ManagedSoftwareUpdate.log file by running the following command. Note: The -F parameter means the tail command continually monitors the file for updates (displaying progress as the software installation continues).
tail -n 20 -F /Library/Application\ Support/AirWatch/Data/Munki/Managed\ Installs/Logs/ManagedSoftwareUpdate.log 
  1. Search for a line in the results stating Skitch version [version] (or newer) is already installed. This indicates the software has been installed.

Note: The agent initiates a Managed Software Update within the munki framework multiple times. Depending on where the agent is within the process of the install, the tail command may output lines similar to the following:

[Date/Time]    Need to install Skitch
[Date/Time]    Downloading Skitch-2.8.1.dmg from Skitch-2.8.1.dmg
[Date/Time]     The following items will be installed or upgraded:
[Date/Time]         + Skitch-2.8.1
[Date/Time]      Processing installs
[Date/Time]      Installing Skitch (1 of 1)
[Date/Time]     Mounting disk image Skitch-2.8.1.dmg
[Date/Time]     The software was successfully installed.

4. Check for App in the Launchpad

  1. Click the Launchpad icon on the Dock.
  2. Check if the Skitch application is present.

5. View the Application Status in the Workspace ONE UEM Application Catalog

  1. Click the Application Catalog weblink on the Dock.
  2. Note the Installation Status for Skitch.

Key Takeaways

  • macOS applications can be deployed using the Munki framework (Internal Application) or a detailed manifest of scripts and packages (Product Provisioning, not covered in this exercise).
  • Detailed status on installation progress is delivered to the end-user using the Workspace ONE native application for macOS (not covered in this exercise)
  • Workspace ONE UEM provides an application catalog to allow user and device specific self-service requests for application installation.

Deploying Third-Party macOS Applications as Products (Legacy)

Introduction

This exercise helps you to use the legacy method of product provisioning to deploy third-party macOS applications.

Workspace ONE UEM supports a few different methods for delivering software to managed macOS devices. In this section, learn about the software delivery methods that are available, and when each method is appropriate to use.

The following software delivery methods are available  for macOS:

  • Apple Business Manager or Apple School Manager — Delivers macOS App Store applications to devices as volume-licensed, purchased applications
  • Software Distribution — Delivers third-party, non-store applications as internal apps in Workspace ONE UEM 9.3 and later. This method is covered in Deploy Third-Party macOS Applications as Internal Applications.
  • Product Provisioning — Deploys non-store applications and scripts as products in Workspace ONE UEM (or AirWatch) 9.2 and earlier. We recommend that you use either Apple Business Manager or Software Distribution to deliver software. However, if you encounter issues with software distribution, you can follow the legacy method, which is covered in this exercise.

The type of software being delivered determines the appropriate delivery method. The following table lists different types of software, and their recommended delivery method.  

  macOS App Store Applications Non-Store Applications
Delivery Method Apple Business Manager Software Distribution
Examples
  • xCode 
  • Slack 
  • Microsoft Remote Desktop
  • Apple's iWork suite
  • TextWrangler
  • F5 Access (VPN)
  • iBooks Author
  • Microsoft OneDrive
  • Microsoft OneNote
  • Quickbooks
  • VMware Tunnel
  • Adobe Creative Suite
  • Microsoft Office 2016 for macOS
  • BlueJeans
  • Camtasia
  • Audacity 
  • Shell scripts, Python scripts

Prerequisites

Before you can perform the procedures in this tutorial, you must satisfy the following requirements. 

  • Apple device running macOS version 10.12.6 (Sierra) or later
  • VMware Workspace ONE UEM Agent for macOS version 3.0 or later
  • Workspace ONE UEM version 9.3 or later

For more information, see the VMware Identity Manager Documentation and VMware Workspace ONE UEM Documentation.

Creating a Custom Attribute Profile

Custom Attributes are a built-in function of the VMware Workspace ONE UEM agent for macOS. An administrator can deliver a shell script in a profile payload, and the echo result of that script is returned to the console as custom information about that device. In the context of product provisioning, one or more custom attributes can be used to further constrain product deployment to devices within an assignment group.  

This section demonstrates how to create a custom attribute profile.

1. Create Custom Attribute Profile

Add a macOS Device Profile

In the Workspace ONE UEM console:

  1. Select Devices.
  2. Select Profiles & Resources.
  3. Select Profiles.
  4. Select Add.
  5. Select Add Profile.

2. Select Profile Platform

Select Profile Platform

Select the macOS icon.

3. Select the Profile Context

Select the Profile Context

Select the Device Profile icon.

4. Configure General Profile Settings

Configure General Profile Settings
  1. Click General if it is not already selected.
  2. Enter BBEdit Version for the Name.
  3. Select Auto for the Assignment Type.
  4. Click in the Assigned Groups field. This will pop-up the list of created Assignment Groups. Enter All Devices and select the All Devices (your@email.shown.here) Smart Group.
    Note: You may need to scroll down to find the Assigned Groups field.

NOTE: You do not need to click Save or Save & Publish at this point. This interface allows you to move around to different payload configuration screens before saving.

5. Configure Custom Attributes Payload

Configure Custom Attributes Payload
  1. Scroll down on the list of Payload Types on the left side.
  2. Click Custom Attributes.
  3. Click Configure.

6. Enter Local Host Name Custom Attribute Command

Enter Local Host Name Custom Attribute Command
  1. Enter BBEdit-Version as the Attribute Name.
  2. Enter the following command.  Be sure to use the correct slash, two hyphens, and proper capitalization.
    if [ -x "/Applications/BBEdit.app" ]; then /usr/bin/defaults read /Applications/BBEdit.app/Contents/Info.plist CFBundleShortVersionString ; else echo "0.0"; fi
  3. Select 1 Hour as the Reporting.
  4. Click Save & Publish.

7. Publish to Device Assignment

Publish to Device Assignment

Click Publish.

Locating Custom Attributes

After Workspace ONE UEM delivers a custom attributes profile/payload to a device, the agent reports the initial value of the custom attribute back to Workspace ONE UEM and begin the Schedule or Event monitoring. Custom attribute values that have been reported back to the console can be viewed in the device details.

1. Select Your Enrolled Device

  1. Select Devices.
  2. Select List View.
  3. Select your enrolled macOS device to access the Device Details view.

2. Access Custom Attributes

Access Custom Attributes
  1. Click More.
  2. Click Custom Attributes.

3. Review Custom Attributes

Review Custom Attributes
  1. Note that the Source of the Attributes is Device Sourced, meaning it was gathered at the device and sent to Workspace ONE UEM.
  2. Note the list of Attributes.  
  3. Note the value of each Attribute. These values were generated by the output of your command/script in the Custom Attributes payload.

The value is currently 0.0 because BBEdit is not installed on the device.

Downloading BBEdit Installer

Next, download the BBEdit installer file.

1. Open Safari Browser

If not already open, click the Safari icon in the Dock.

2. Browse to BareBones Software Website

Navigate to https://www.barebones.com/products/bbedit/download.html.

3. Download BBEdit 12 Evaluation for macOS

Click Download.

Creating Files/Actions

A product can comprise one or more Files/Actions. Files/Actions are the building blocks of a product, containing a set of files and a manifest of actions to take against those files. A Files/Actions set can also contain a corresponding uninstall manifest which directs the Workspace ONE UEM agent as to how a product should be removed during an Enterprise Wipe. This exercise demonstrates how to create a basic set of files/actions in order to install and uninstall BBEdit.

1. Browse to Files/Actions

In the Workspace ONE UEM Console, perform the following:

  1. Select Devices.
  2. Expand Staging & Provisioning.
  3. Expand Components.
  4. Select Files/Actions.
  5. Click Add Files/Actions.

2. Choose the macOS Platform

Select Apple macOS.

3. Name the Files/Actions Item

  1. Enter BBEdit Install as the Name.
  2. Select the Files tab.

4. Add Files to Files/Actions

Select Add Files.

4.1. Choose Files to Upload

Select Choose Files.

4.2. Select File from Finder

  1. Click the Downloads folder.
  2. Select the BBEdit_<version>.dmg file.
  3. Select Choose.

Note: The BBEdit Installer will be located in your default Downloads folder. Common folders to check are the Desktop and Downloads folders.

4.3. Save the File to Files/Actions

Click Save.

5. Enter Download Path

  1. Enter /tmp as the download path.
  2. Click Save.

Note: In this example, we use /tmp as the download path as it is automatically cleaned up by macOS. If you want Product Downloads to persist on the file system, you must choose a different download path.

6. Copy File Path

  1. Click and drag to highlight the Path field.
  2. Right-click (or Control-click) the highlighted path and select Copy.
  3. Select the Manifest tab.

7. Add Action to Install Manifest

Click Add Action under Install Manifest.

7.1. Configure Add Manifest Action

The Install Manifest comprises the sequence of actions that must be performed to install the files you have included in the Files/Actions. This could involve copying or moving files, installing dmg/pkgs, and running scripts.

  1. Select Install as the action.
  2. Paste the File Path you copied previously: /tmp/BBEdit_<version>.dmg
  3. Select Save.

8. Add Action to Uninstall Manifest

Click Add Action under Uninstall Manifest.

8.1. Add Action to Uninstall Manifest

The Uninstall Manifest comprises the sequence of actions that must be performed in order to remove or revert the files and actions you have taken as part of an install. The Uninstall Manifest also instructs the agent how to remove the product during an Enterprise Wipe.

  1. Select Uninstall as the action.
  2. Enter the name of the App as it appears in the list of Applications when installed: BBEdit
  3. Select Save.

9. Save File/Actions

Select Save.

Creating a Product from Files/Actions

This exercise helps you to create a product from Files/Actions.

1. Add Product

In the Workspace ONE UEM Console:

  1. Select Devices.
  2. Expand Staging & Provisioning.
  3. Select Product List View.
  4. Select Add Product.

2. Choose Product Platform

Select Apple macOS.

3. Complete General Information

  1. Enter Install BBEdit for the Product Name.
  2. Click in the Assigned Groups field and select All Devices (your@email.shown.here).
  3. Click Add Rules.

4. Add Dependency Rules

  1. Click Add Rule.
  2. Select BBEdit-Version @ AirWatchAgent for the Attribute/Application.
  3. Select <> for the Operator.
  4. Select Enter Manually for the Value.
  5. Enter 12.1.5  (or the most current version of BBEdit).
  6. Note that the Rule Logic field is built out automatically based on your selections and inputs.
  7. Select Save.

5. Add Manifest to Product

  1. Select the Manifest tab.
  2. Select Add.

6. Choose Manifest Item

  1. Select Install Files/Actions in the action(s) menu.
  2. Select BBEdit Install as the Files/Actions item.
  3. Select Save.

7. Set Product Type and Activate

  1. Select the Deployment tab.
  2. Select Required as the product type.
  3. Select Activate.

8. Confirm Device Assignment

Select Activate.

Validating Product Installation

After activating the Product, you are taken back to the Product List View in the Workspace ONE UEM Console, which is located under Devices > Staging & Provisioning > Product List View.

  1. You may need to click the Refresh button if the shown values are not populated.
  2. Note the number of Compliant devices (the product installed successfully).
  3. Note the number of devices where product installation is in progress.
  4. Note the number of failed product installs.

Note: All the status counts are clickable and display a list view of all devices with that status (for example, Compliant, In Progress, and Failed).

1. Validate Install on Managed macOS Device

  1. Select the Finder icon in the Dock.
  2. Select Applications.
  3. Validate BBEdit is present in the application list.

Summary and Additional Resources

Conclusion

This operational tutorial provided steps to deploy third-party macOS applications in two ways; as internal apps and as products. 

Procedures included: 

  • Enabling macOS software management
  • Preparing and deploying a macOS application as an internal application
  • Creating a custom attributes profile
  • Creating and assigning a product to a device

Terminology Used in This Tutorial

The following terms are used in this tutorial:

application store A user interface (UI) framework that provides access to a self-service catalog, public examples of which include the Apple App Store, the Google Play Store, and the Microsoft Store.
auto-enrollment Auto-enrollment simplifies the enrollment process by automatically enrolling registered devices following the Out-of-Box-Experience.
catalog A user interface (UI) that displays a personalized set of virtual desktops and applications to users and administrators. These resources are available to be launched upon selection.
cloud Asset of securely accessed, network-based services and applications. A cloud can also host data storage. Clouds can be private or public, as well as hybrid, which is both private and public.
device enrollment The process of installing the mobile device management agent on an authorized device. This allows access to VMware products with application stores, such as VMware Identity Manager.
identity provider (IdP) A mechanism used in a single-sign-on (SSO) framework to automatically give a user access to a resource based on their authentication to a different resource.
mobile device management
(MDM) agent
Software installed on an authorized device to monitor, manage, and secure end-user access to enterprise resources.
one-touch login A mechanism that provides single sign-on (SSO) from an authorized device to enterprise resources.
service provider (SP) A host that offers resources, tools, and applications to users and devices.
virtual desktop The user interface of a virtual machine that is made available to an end user.
virtual machine A software-based computer, running an operating system or application environment, that is located in the data center and backed by the resources of a physical computer.

For more information, see the VMware Glossary.

Additional Resources

About the Authors

This exercise was written by:

  • Robert Terakedis, Senior Technical Marketing Manager, End-User-Computing Technical Marketing, VMware
  • Hannah Jernigan, Technical Marketing Manager, End-User-Computing Technical Marketing, VMware
  • Gina Daly, Technical Marketing Manager, End-User-Computing Technical Marketing, VMware

Feedback

The purpose of this tutorial is to assist you. Your feedback is valuable. To comment on this tutorial, contact VMware End-User-Computing Technical Marketing at euc_tech_content_feedback@vmware.com.