You can configure a pull service v2.0 relay server based on Microsoft's .NET Core, the open source, cross-platform successor to their .NET Framework.

Prerequisites

The .NET Core based pull service is built using .Net core 2.1. For more information, see https://dotnet.microsoft.com/.
Table 1. Hardware Requirements
Component Requirement
Server 1
CPUs 2 (2.0 GHz Intel Processor, x86 64bit)
Memory 4 GB
Storage* 25 GB

* Required storage size for a relay server must scale with the collective size of the files and applications that will be distributed through it. A file is not deleted from the relay server until the associated File Action component is deleted from the UEM Console. Likewise, memory and CPU requirements must increase as the count of devices using the server grows.

Table 2. Network Requirements
Component Requirement
Outbound Traffic to Workspace ONE UEM console Port 443
Protocol for Outbound Traffic to Workspace ONE UEM console HTTPS

On the client side, the pull service can use any dynamically assigned port, with no limitations, to connect to content pull on the server side.

Currently, .NET Core does not support HTTPS proxies.
Table 3. Software Requirements
Component Requirement
Operating System

Windows 64 bit or RHEL7 64 bit or

CentOS7 64 bit** or Ubuntu 18.04 64 bit**

Workspace ONE UEM

Version 1903 or later.

Customers using versions 1903 through 1907 must enable the PullServiceInstallerFeatureFlag.

Contact VMware Support for assistance in updating the database with this feature flag. The feature is enabled by default in versions 1908 and later.

Install Pull Relay Service v2.0

Procedure

  1. Visit https://my.workspaceone.com/products/Pull-Service and download the .NET Core Pull Relay Server for Windows or Linux installer.
    1. Note: The Linux pull service installer has a hard-coded installation path of "/OPT/". You must configure this directory with sufficient write permissions and the top-most privileges. You must also have sufficient write permissions for the directory where the pull service is configured to download the contents.
    2. Linux Silent Installation Option: You have the option of running the Linux installation without being prompted. The following is an example of the code you might use to install silently the pull relay server for Linux with an NTLM proxy, basic authentication, and custom discovery text.
      sudo ./VmwarePullserviceinstaller.bin -i silent -DPULL_SERVICE_CERT_PASSWORD=Test@1234 -DOUTBOUND_PROXY=1 -DOUTBOUND_PROXY_HOST=192.168.1.100 -DOUTBOUND_PROXY_PORT=808 -DOUTBOUND_PROXY_CREDENTIALS=1 -DOUTBOUND_PROXY_NTLM_AUTH=0 -DOUTBOUND_PROXY_DOMAIN= -DOUTBOUND_PROXY_USERNAME=john -DOUTBOUND_PROXY_PASSWORD=hello@1234 -DIS_DISCOVERY_TEXT=1 -DDISCOVERY_TEXT=og1
  2. On-premises customers using older versions of the console can enable the PullServiceInstallerFeatureFlag. Contact VMware Support for assistance in updating the database with this feature flag.
  3. In Workspace ONE UEM, navigate to Groups & Settings > All Settings > System > Enterprise Integration > Pull Service Installers and select the Download Configuration button.
    The Download pull service configuration screen displays.
  4. Enter and confirm the Certificate password you want to use for the pull service certificate and select Download to save the ZIP file. Save the ZIP file to the same directory as the pull service installer you downloaded in step 1.
  5. Extract the contents of the ZIP file to the directory in which you saved it.
    The ZIP file contains the pull service installer CONFIG file which is a file you require to run the installer. You should have the Windows EXE (or Linux BIN) Pull Service Installer file plus the CONFIG file extracted from the ZIP file together in the same directory. If you are installing the Linux variant, you might also have one of the NTLM enablers from step 2.
  6. Run the Pull Service Installer, supplying the password you entered in step 4 when prompted. Continue with the remainder of the installation.
    1. Select whether you wish to use an outbound proxy and, if applicable, enter the proxy configuration.
    2. Select whether you wish to use Custom Discovery Text. The Pull Service uses Discovery Text to identify itself when communicating with Workspace ONE UEM servers. By default, Pull Service v1.0 and v2.0 use the local IP Address and MAC Address of the server but a custom value can be used instead. This is necessary to identify each Pull Server separately in rare cases where multiple Pull Servers do not have unique and distinct local IP Address and MAC Address values.

      When adding Custom Discovery Text, please note that the value entered in the installer is not the full Discovery Text value. The installer will append it to a unique GUID and store it in the appsettings.json file. This file can be found in the install directory of the Pull Service under the /bin folder.

      The Relay Server configuration in the Workspace ONE UEM console must use this Discovery Text value. For more information, see Configure a Relay Server.

  7. ** If you are installing the Linux version and you want to configure an NTLM proxy authentication, the "gss-ntlmssp" package must be installed. Select the download link that corresponds to your Linux flavor and install it now.
    Option Description
    CentOS

    For CentOS, download the following RPM file.

    https://centos.pkgs.org/7/epel-x86_64/gssntlmssp-0.7.0-1.el7.x86_64.rpm.html