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.

The .NET Core based pull service is built using .Net core 2.1. For more information, see https://dotnet.microsoft.com/.

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 are distributed through it. A file is not deleted from the relay server until the associated File Action component is deleted from the Workspace ONE UEM console. Likewise, memory and CPU requirements must increase as the count of devices using the server grows.

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.

Network Requirements

Component Requirement
Outbound Traffic to Workspace ONE UEM console Port 443
Protocol for Outbound Traffic to Workspace ONE UEM console HTTPS

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

See the existing parent topic, Install Pull Relay Service v2.0.

Using the .NET Core Pull Service, Starting and Stopping the Pull Service

  • Start/stop service on CentOS and RHEL.
    /etc/init.d/awpullservice {start|stop|status|restart)
    • Start the pull service.
      service awpullservice start
    • Stop the pull service.
      service awpullservice stop
    • Displays status of the pull service.
      service awpullservice status
    • Restarts the pull service.
      service awpullservice restart
  • Start/stop service on Ubuntu. Run this SH file, which is located in the pull-service/bin folder.
    • Start the pull service.
      sh start.sh
    • Stop the pull service.
      sh stop.sh
  • Start/stop service on Windows.
    • Navigate to Run > services.msc, locate the Airwatch Pull Service, and select start, stop, or restart.

Using the .NET Core Pull Service, Appsettings.json Tweaks

The appsettings.json file settings presented here are the default values which you can change to modify the server's default behavior. The appsettings.json file is located in the pull service\Bin folder.

If the "discoveryText" value is set as null in the appsettings.json, then the pull service assembles and posts a default discovery text. This discovery text is composed of the merging of the pull server's IP address and Mac address in place of the null value.

The pull service must be manually restarted each time you change values in appsettings.json to apply the new settings.

  • "performSystemTaskIntervalMin": "720" (in minutes), the interval when the pull service logs are sent to the content pull endpoint. For more information, see Enable Pull Service Logging.
  • "clientPostTimeOut": "240" (in minutes), the amount of time the connection remains active before timing out. This time frame can increase as the size of your files increase to avoid connection timeouts.
  • "waitTimeOnFailure": "300" (in seconds), the amount of time you allow the pull service to rediscover the relay server if there is a connection error.
  • "logMaxEntries": "10000", the maximum number of log entries in a single log file.
  • "maxLogFiles": "5", the maximum number of logs generated.
  • "maxLogFileSize": "2000000" (in bytes), the maximum size a log file is allowed to get.
  • "enableConsoleLog": "false", for developmental purposes. Enable to activate the console log.
  • "proxyBypassOnLocal": "false", enable/deactivate the bypass proxy server for local addresses.

Migrating to the .NET Core Pull Service

See the existing parent topic, Migrating to the .NET Core Pull Service.

Recovering a Pull Relay Server v2.0 with Custom Discovery Text

See the existing parent topic, Recovering a Pull Relay Server v2.0 with Custom Discovery Text.