You can fine-tune the way your .NET Core pull server works by heeding these tips and to adjust the appsettings.json file.

Best Practices

  • Do not run multiple instances of pull service (old or new versions) on the same machine.
  • Once the pull service is installed, avoid selecting the Regenerate button on the Pull Service Installers settings page. Regenerating the certificate after the pull service is running breaks communication between the Workspace ONE UEM console and the pull service client. If you must regenerate the certificate, then you must rerun the pull service installer.
  • On-premises customers must generate and download the PSinstaller.config file directly from Global OG and not from Customer OG. This configuration enables an easy relay server move from OG 1 to OG 2 without having to reinstall the pull service every time. For more information, see Move an Existing Pull Relay Server from One Organization Group to Another.

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.
    • Stop the pull service.
  • Start/stop service on Windows.
    • Navigate to Run > services.msc, locate the Airwatch Pull Service, and select start, stop, or restart.

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/disable the bypass proxy server for local addresses.