You can configure a pull service v1.0 relay server using a Windows FTP, Explicit FTPS, Implicit FTPS in Pull configuration (Android only), SFTP, or HTTPS (Pull only) server for use with product provisioning and staging.

The legacy Pull Service v1.0 and its configuration file are not available for download in Workspace ONE UEM console 1908 and later. You must instead use the Pull Service v2.0. For more information, see Configure .NET Core Pull Relay Server, PS v2.0.

If Pull Service v1.0 must be used and is not available for download, contact Workspace ONE UEM support.

Prerequisites

Before you begin, ensure that you have the following.
  • An FTP, Explicit FTPS, Implicit FTPS in Pull configuration (Android only), SFTP, or HTTPS (Pull only) server. Workspace ONE UEM does not support Implicit FTPS Windows-based relay servers.
    • SFTP servers are supported for product provisioning only. Barcode staging clients do not support SFTP.
    • Implicit FTPS relay servers are only supported in a pull configuration and can only be used with Android devices.
  • Only x86 64bit architecture is supported.
  • Microsoft's .NET Framework must be installed on Windows-based servers.
  • The pull relay server requires outbound network access on https 443 to the Workspace ONE UEM console.
  • Each server requires disk storage of 2 MB for the pull server installer and hard disk space for all the content pulled to the server.

Procedure

  1. Configure an FTP, Explicit FTPS, Implicit FTPS in Pull configuration (Android only), SFTP, or HTTPS (Pull only) server.
    You must create a local user with read/write/delete permissions for both the directory and the files used in the HTTPS or FTP-based relay server. This user must have a user name and password for authentication. Note the home directory of the user for use in configuring the pull service.
  2. Navigate to Groups & Settings > All Settings > System > Enterprise Integration > Pull Service Installers.
  3. Download the Windows Pull Service Installer and the Configuration file onto the server using your preferred server management system.
  4. Open the XML config file and update the following.
    1. Set the install directory for the pull service, found inside the libraryPath tags. This location does NOT have to match the root directory of the file server.
    2. Set the FQDN or IP address of your Workspace ONE UEM console server with /contentpull appended to it. This configuration is found inside the endPointAddress tags.
    <PullConfiguration>
       <libraryPath>C:\<FTP_Home_Dir>\</libraryPath>
       <endPointAddress>https://<Console_Server_URL>/contentpull /</endPointAddress>
    </PullConfiguration>
  5. Run the WindowsPullServiceInstaller.exe. DotNet is installed before the MSI is extracted.
    Alternatively, you can run the installer with switches.
    • Silent Install: WindowsPullServiceInstaller.exe /s /v"/qn/"
    • Silent install with logging:WindowsPullServiceInstaller.exe /s /v"/qn/" /l WindowsPullServiceInstaller.txt
  6. Validate the pull service configuration.
    • SaaS Customers (or customers whose Global OG is unavailable)
    • On Premises Customers
    1. For SaaS Customers (or for customers without access to the Global OG), you can skip this validation step. Proceed to Results.
    2. For On Premises Customers, log into the Workspace ONE UEM console at the topmost organization group, Global.
    3. Navigate to Devices > Provisioning > Relay Servers > Undiscovered Pull Relay Servers.
    4. If the new Windows-based Pull Relay Server displays in the listing by its Discovery Text, then you have successfully validated the pull service configuration.

Results

The installer looks for the PullserviceInstaller.config file in the installer execution directory. If the file is missing, the installer prompts you that the file is missing.