Workspace ONE UEM powered by AirWatch supports provisioning your Windows 10 devices with apps before they leave the factory. You do so by creating provisioning packages using Workspace ONE Drop Ship Provisioning (Offline). Before creating provisioning packages, you must meet the Workspace ONE Drop Ship Provisioning (Offline) requirements. Use the listed component versions, and see the provisioning components the Workspace ONE UEM enables or requires for your deployment type. After meeting the requirements, you must install the Factory Provisioning Service in your environment.

Workspace ONE Drop Ship Provisioning (Offline) requires on-premises customers to install the service onto an application server.

This service exports applications from the Workspace ONE UEM console and converts them into .PPKG files. You create this provisioning package in the Workspace ONE UEM console using a wizard. The wizard covers configuring the package, adding apps, and exporting the package.

Contact Your OEM for Availability

To use Workspace ONE Drop Ship Provisioning (Offline), contact your OEM (Original Equipment Manufacturer) Representative.

Provisioning Packages

You can also create encrypted PPKGs to provision devices yourself. This process does not use Workspace ONE Drop Ship Provisioning (Offline). You can provision devices either using the device OOBE or by running the PPKG on a device.

Workspace ONE Drop Ship Provisioning (Offline) Requirements by Deployment Type

The following tables show the requirements for Workspace ONE Drop Ship Provisioning (Offline) for each type of deployment. Consider these requirements before using Workspace ONE Drop Ship Provisioning (Offline).
  • Workspace ONE UEM v2008 or later
  • Workspace ONE Intelligent Hub for Windows v20.08 or later
  • Software Distribution of Win32 apps released with Workspace ONE UEM v2008 and later
  • Workspace ONE UEM Deployment Software Distribution File Storage CDN
    SaaS Shared Enabled by Default N/A Enabled by Default
    SaaS Dedicated version 2008 and later Enabled by Default N/A Enabled by Default
    On-premises version 2008 and later Enabled by default Required Disabled by default, optional
Note:
  • Any application uploaded before you enable Software Distribution must be uploaded again.
  • If you use the Factory Provisioning Service v20.11 or later, you must use the Workspace ONE Provisioning Tool v.3.1 or later.

Install the Factory Provisioning Service

Before you can use Workspace ONE Drop Ship Provisioning (Offline), you must install the Factory Provisioning Service in your environment.

Prerequisites

This process installs the Factory Provisioning Service into your environment. Only On-Premises customers must install this service. Consider reviewing the VMware Workspace ONE UEM Recommended Architecture Guide before installing the service.

Ensure that the servers the Factory Provisioning Service are installed on can reach and connect to your REST API server. The URL for REST API is set under Groups & Settings > All Settings > System > Advanced > Site URLs > REST API URL.

Use TLS to ensure that the traffic between the Factory Provisioning Service server and the Workspace ONE UEM console is secured. To use TLS, you must install a certificate for the Factory Provisioning Service server and enable HTTPS.

Procedure

  1. Download the Factory Provisioning Service from myWorkspaceONE.
  2. Run the Factory Provisioning Service installer.
  3. In the Workspace ONE UEM console, navigate to Groups & Settings > All Settings > System > Advanced > Site URLs.
  4. Ensure that the correct URL is entered: https://[FPS URL]/FactoryProvision/Package.

The Factory Provisioning Service is now installed. You can validate the installation by checking the communication between the various components used.

Factory Provisioning Service and the following:
  • REST API over HTTPS
  • Device Services over HTTPS
  • CDN (if configured)
  • Network file share access

The Workspace ONE UEM console and the REST API server communicate with the Factory Provisioning Service server over HTTPS.