Install & Setup

Device Tracker On-Prem 3.0

Overview

Device Tracker On-Prem consists of the following two components:

  • Client – Device Tracker On-Prem client app runs on supported Zebra Android mobile devices. It collects device information, sends presence updates to the server, and provides a remote chirping device finding feature. The client app can play the role of either the tracking device or the device being tracked.
  • Server – Device Tracker On-Prem server is part of the Zebra DNA Visibility Console server solution, a common server software for both Device Tracker On-Prem and PowerPrecision Console. It provides a centralized dashboard that is accessible from a supported browser running on a kiosk, tablet, or PC. The server collects and processes device data for tracking misplaced devices, including tracking status, connection status, and battery status.

Device Tracker On-Prem operates on WiFi networks and does not support WWAN.

Before installing, ensure to prepare additional steps for system setup - consult your local IT department for assistance:

  • Install a server certificate - Supported certificates:
    • SSL certificate - use for secure HTTPS communications. The SSL certificate must be procured and signed from a trusted third-party Certificate Authority (CA), such as Verisign or Thawte, and must contain the complete certificate chain, including intermediate certificates.
    • Self-signed certificate - use for demos and trials. A self-signed certificate is considered as untrusted - use at your own risk.
  • Open specific incoming and outgoing ports - for server communication through the firewall, based on ports specified during server installation
  • Add DNS (Domain Name Server) Entry - an entry is added to the DNS to map the server IP address to the domain

Version History

  • Device Tracker On-Prem 2.3.1 - Self-signed certificates are now supported to help simplify deployment of product demos and trials.

System Requirements

This section provides the server and device requirements. Device Tracker On-Prem supports a maximum of 500 devices per installation.

Server Requirements

  1. Windows Operating System supported:

    • Windows Server 2012, 64-bit processor
    • Windows Server 2016, 64-bit processor
  2. Browsers supported (connect over https):

    • Google Chrome Browser version 66 and higher
    • Microsoft Internet Explorer version 11 and higher
    • Microsoft Edge for Windows 10
    • Safari for Mac version 11 and higher
  3. Software Required (included in server installation):

    • Java runtime
    • Node.js version 6.11
    • PostgreSQL 9.6.3-3 and higher
    • Device Tracker software (server and client)
  4. Network Access Requirements (see Server Setup below):

    • If required, open incoming and outgoing ports for communication between server and mobile devices through the server firewall. Sample ports are:
      • Backend Server: Data port 8080 for Device Tracker On-Prem client to register to the server and transmit device data
      • Web Portal: UI port 8443 for accessing Device Tracker On-Prem web portal

    • If required, perform DNS setup to add server IP address to the DNS server.

  5. Certificate requirement: An SSL Certificate for secure communications or a self-signed certificate for product demos and trials.

  6. Internet Access Required: Internet access is needed during initial setup to download npm package dependencies.

  7. Hardware Requirements:
          ○   Minimum CPU cores: 16
          ○   Minimum memory (RAM): 64 GB
          ○   Minimum available hard drive space: 500 GB

Note: Zebra does not recommend hosting the server in the cloud.

Device Requirements

Requirements for Device Tracker On-Prem client:

  • The ZDVC server is installed and running.
  • The device is connected via WiFi on the same network as the server.
  • Zebra Data Service agent is running on the device. This agent collects data from the device.
  • The server URL, user name, and password is configured in the Device Tracker On-Prem client to communicate with the server.
  • Bluetooth radio is enabled on both devices for proximity tracking with BLE (Bluetooth Low Energy) beacons.

See supported devices on Zebra support portal.

Server Install & Setup

Contact Zebra at devicetracker-onprem@zebra.com for the server download. Install ZDVC server via a new install or an upgrade from an existing install on the supported system that meets the specified requirements. The user must have the appropriate system privileges to install the server. After server installation, further network and certificate setup is required to allow communication between the server and devices via DNS and firewall. Instructions for server installation and setup:

Server Prerequisites

The following are the prerequisites required for the server:

  1. DNS (Domain Name Server) Setup. ZDVC server runs in a domain, for example company.com. An entry with the server hostname and corresponding IP address is required in the DNS server for name resolution. The DNS server and ZDVC server are required to be on the same network. Contact your local IT Administrator to configure the domain to IP address mapping.

  2. Server Certificate. An SSL certificate is required for secure communications or a self-signed certificate can be used for product demos and trials. The certificate must be in .pfx format and set with a password. See Server Certificate for details.

  3. Open Inbound/Outbound Ports on the Firewall. The appropriate ports are required to be opened for inbound/outbound network traffic flow through the firewall for communication between the server and devices. The UI and Backend Server ports are specified during server install. The method to open the ports depends on the firewall software used by the network administrator.

    • Backend Server (data) Port: inbound (e.g. port 8080)
    • Web Portal (UI) Port: inbound and outbound (e.g. port 8443)


Server Certificate

An SSL tool is required to generate the server certificate. Download and install the SSL toolkit OpenSSL. Instructions follow to generate an SSL certificate or self-signed certificate.

SSL Certificate

An SSL certificate is needed for secure connections. Domain level and wildcard certificates are acceptable. Generate the CSR (Certificate Signing Request) with private key and submit it to the trusted CA. The CA issues the SSL Certificate signed with the public key (in .p7b format). Use this issued certificate to generate the SSL certificate with the private key. The final, complete SSL certificate contains the server certificate, any intermediate certificates, the public key and private key. The procedure to accomplish this is separated into two sections below:

  • Procure server certificate (.p7b format) with public key
  • Generate complete SSL certificate (.pfx format) with both public and private keys

If the server certificate with public key already exists, skip to the second section Generate complete SSL Certificate. If the complete SSL certificate already exists, skip to section Server Installation.

Procure server certificate: Create a private key and generate the CSR. Submit the CSR to the CA for signing. The server certificate issued should be in .p7b format. Watch a video demonstration or follow the steps below:

  1. Add a new "openSSL" environment variable to the Windows system and set the value to the location where openSSL is installed (e.g. "C:\Program Files\OpenSSL-Win64\bin\").
  2. Create a folder named "ServerCert". Open the command prompt to this folder path.
  3. Create a private key. It prompts to enter the passphrase - make note of this passphrase, which is used in Device Tracker On-Prem. Run the command:
         openSSL genrsa -des3 -out dtrkdemo.key 2048
    where "dtrkdemo.key" can be replaced with a custom file name.
  4. Create a CSR based on the new private key. Run the command:
         openSSL req -key dtrkdemo.key -new -out dtrkdemo.csr
    where "dtrkdemo.key" (same file name as in step 4) and "dtrkdemo.csr" (new file created) can be replaced with custom file names. It prompts to enter the private key password (created in step 5). Enter in the required fields when prompted (the information entered must match that registered with the CA):
    • Country Name - Enter the two-letter code without punctuation for country, for example: US or CA.
    • State or Province - Enter the full state or province name without abbreviation, for example: California.
    • Locality or City - Enter the city or town name without abbreviation, for example: Berkeley or Saint Louis.
    • Organization Name - Enter the company. If the company or department contains a special character such as "&" or "@", the symbol must be spelled out or omitted in order to enroll successfully.
    • Organizational Unit Name - Enter the name of the department or organization unit making the request. This is optional, to skip, press Enter on the keyboard.
    • Common Name - Enter the fully qualified host name, for example: "hostname.company.com". This is the same name to be used in the Server Installation in step 5 for the Domain name.
    • Email Address - Enter the contact email address.
      When prompted for the challenge password, it is not required - do not supply one.
  5. Submit the CSR created to the CA. They will supply a certificate in .p7b format, e.g. ssl_certificate.p7b.

Generate complete SSL Certificate: Zebra requires the certificate be procured in .p7b format and combined with the private key (.key file) to generate the SSL certificate in .pfx file format. If the certificate is in a different format, use an SSL certificate converter tool to convert to the proper format. Watch a video demonstration and follow the steps below:

  1. Create an ssl_certificate.cer file with the command:
         openssl pkcs7 -print_certs -in ssl_certificate.p7b -out ssl_certificate.cer
    where "ssl_certificate.p7b" is the certificate issued by the CA.
  2. Create SSL certificate "ssl_certificate.pfx" with command (using the private key password created from step 4 in the previous section):
         openssl pkcs12 -export -in ssl_certificate.cer -inkey dtrkdemo.key -out ssl_certificate.pfx
    where "dtrkdemo.key" is the private key generated from step 4 in the previous section and "ssl_certificate.cer" is the file generated from the previous step 1. When prompted, enter the passphrase (from step 4 in the previous section) and specify an export password.
  3. Import the SSL certificate on the server. Double-click the certificate on the local computer and follow the Certificate Import wizard. When prompted for a password, enter the password set from the previous step.
  4. Use SSL certificate "ssl_certificate.pfx" and the private key password for Device Tracker On-Prem server installation and setup in the sections that follow.

Self-Signed Certificate

A self-signed certificate can be used for for product demos and trials. Procedure to generate a self-signed certificate:

  1. Generate a private key:
         openssl genrsa -des3 -out dtrkdemo.key 2048
    where "dtrkdemo.key" is the name of the private key.
  2. When prompted, enter a pass phrase.
  3. Generate a CSR:
         openssl req -new -key dtrkdemo.key -sha256 -out dtrkdemo.csr
    where "dtrkdemo.key" is the name of the private key from step 1 and "dtrkdemo.csr" is the name of the CSR.
  4. When prompted, enter the pass phrase set in step 2.
  5. When prompted, enter information in the fields requested, including the challenge password.
  6. Generate a self-signed certficate:
         openssl x509 -req -days 365 -in dtrkdemo.csr -signkey dtrkdemo.key -sha256 -out dtrkdemo.crt
    where "dtrkdemo.crt" is the self-signed certficate to be used for the client app.
  7. When prompted, enter the pass phrase set in step 2.
  8. Generate the .pfx certificate file:
         openssl pkcs12 -export -out dtrkdemo.pfx -inkey dtrkdemo.key -in dtrkdemo.crt
    where "dtrkdemo.pfx" is the certificate required to install on the server.
  9. When prompted, enter the pass phrase for the private key.
  10. Use self-signed certificate "dtrkdemo.pfx" and the private key password for Device Tracker On-Prem server installation and setup in the sections that follow.

Server Installation

ZDVC Server Installation steps for a new installation:

  1. Double-click on the .EXE to launch the installer.
  2. At the initial window, click Next. img Installation - initial screen
  3. Accept the license agreement. Click Next. img Installation - EULA
  4. Accept the default folder or browse to the destination folder. Click Next. img Installation - destination location
  5. Enter in the server configurations, then click Next:
    • Domain - fully qualified domain name (FQDN) which consists of the hostname and domain name, e.g. "hostname.company.com"
    • Server Certificate Path - location of server certificate (.pfx file)
    • Server Certificate Password - password for server certificate
    • UI port - designated UI port, can default to 8443
    • Backend Server Port - designated server port, can default to 8080 img Installation - server configuration
  6. Set the server authentication and login credentials, then click Next:
    • Super admin and database password
    • Server auth key
    • Server auth password
      Important: Use of the following special characters is not supported for the "Server auth key" and "Server auth password":
                < (less than)
                > (greater than)
                & (ampersand)
                ' (single quote)
                " (double quote)
      img Installation - server authentication and credentials
  7. Review settings. Click Next. Third party applications (such as Postgres and Node.js) will be installed if it does not pre-exist in the system. img Installation - review settings
  8. Installation complete. Click Finish. img Installation - complete
  9. For first time installations, reboot the server. Otherwise, perform one of the following to start the server:
    A. Reboot the server. The ZDVC server services automatically start as scheduled tasks.
    B. Manually start the ZDVC Backend Server and ZDVC WebUI Server scheduled tasks to run the services. Open Task Scheduler in Administrative Tools. For each scheduled task, right-click on the task and select Run from the menu. Run ZDVC service

Server Upgrade

ZDVC Server can be upgraded from a previous existing ZDVC installation. Prior to upgrading, the ZDVC services must be stopped. Procedure to upgrade:

  1. Follow steps to stop the application server.
  2. Run the new installer.
  3. Click Yes when prompted to upgrade.
  4. At the initial window, click Next to proceed with the upgrade.
  5. Once installation completes, click Finish.

Server Downgrade

To downgrade the server, uninstall the previous version, terminate the ZDVC server processes and install the older server version. Procedure to downgrade:

  1. Uninstall ZDVC server.
  2. Terminate the active processes running on specified ports by using one of the following methods:
    A. Reboot the system.
    B. Run the following commands from the command prompt to find the process ID and terminate the specific process ID:
             netstat -aon | find /i "8080"
             taskkill /pid 1234 /f
    Where "8080" represents the specific backend server port number specified during install and "1234" represents the process ID returned from the first command. Repeat these steps for the Web UI port.
  3. Run the installer for the older server version. Follow the prompts to complete installation.

Server Setup

Steps for ZDVC server setup after installation:
     1. Run ZDVC Server Software. Start the server services either manually or by rebooting the server after install. Refer to the last step in the Server Installation section.
     2. View the web portal. Open a supported browser. Enter the default WebUI server URL: https://hostname.company.com:8443/zdvc, where "hostname.company.com:8443" is replaced with the appropriate hostname, domain and port number.
     3. Select app to launch. As part of ZDVC, the server consists of multiple solution offerings. Select "Device Tracker On-Prem".
     4. Login. Enter the login credentials. The default user name is "SAdmin". The password is the super admin and database password entered during server installation. If using an SSL certificate, proceed to step 5.

  • If using self-signed certificate for the first time, permission needs to be granted. Follow the steps below to login depending on the browser:
    • For Chrome, Safari, or Internet Explorer:
           A. In the browser, enter the backend URL: https://hostname.company.com:8080, where "hostname.company.com:8080" is replaced with the appropriate hostname, domain and port number. Enter the username and password. This is the Server Auth Key and Server Auth Password set during server install.
           B. A message appears indicating the connection is not private due to the lack of a secured certificate. Click "Proceed...".
           C. Enter the WebUI server URL: https://hostname.company.com:8443/zdvc, where "hostname.company.com:8443" is replaced with the appropriate hostname, domain and port number.
           D. A message appears indicating the connection is not private due to the lack of a secured certificate. Click "Advanced", then click "Proceed..."
    • For Edge:
           A. In the browser, enter the backend URL: https://hostname.company.com:8080, where "hostname.company.com:8080" is replaced with the appropriate hostname, domain and port number. Enter the username and password. This is the Server Auth Key and Server Auth Password set during server install.      B. Click “Continue to this website”.
           C. Click on “Certificate error” in the address bar, then click “View certificates."
           D. Click “Install Certificate”.
           E. Click “Place all certificates in the following store”, then click “Browse”. Do not rely on the pre-selected option to automatically select the certificate store since this will not work.
           F. In the dialog box, click “Trusted Root Certification Authorities”, then click “OK”.
           G. Click "Finish".
           H. A security warning is displayed. Click “Yes” to trust the certificate.
           I. Reload the page.
           J. Enter the WebUI server URL: https://hostname.company.com:8443/zdvc, where "hostname.company.com:8443" is replaced with the appropriate hostname, domain and port number.
           K. Click "Advanced" and then click "Proceed..."

     5. SSL certificate validation. For SSL certificates, an SSL Tool (such as ssltools.com) can be used to aid in diagnostics and validate the SSL certificate chain.
         A. Open ssltools.com in the browser.
         B. Enter the Web UI URL, for example https://hostname.company.com:8443/zdvc
         C. Click the Scan button. A successful result returns green checks for each step. See screen below.
         D. Enter the backend URL for your server, for example https://hostname.company.com:8080/zdvc
         E. Click the Scan button. A successful result returns green checks for each step: img SSLTools.com results

Stop Application Server

Procedure to stop the application server:

  1. Stop the ZDVC Backend Service and ZDVC Web UI Service from Task Scheduler in Administrative Tools. Right-click on the service and select End. End ZDVC service
  2. Terminate the active processes that are running on specified ports by using one of the following methods:
       A. Reboot the system.
       B. Run the following commands from the command prompt to find the process ID and terminate the specific process ID returned:
             netstat -aon | find /i "8080"
             taskkill /pid 1234 /f
    where "8080" represents the backend server port number specified during install and "1234" represents the process ID returned from the first command. Repeat these steps for the Web UI port.

Client Install & Setup

Install Device Tracker On-Prem client app to register the device and transmit data to the server. The device must be connected to the same network as the server. Client app installation and configuration can be performed either manually or remotely, with Zebra's StageNow or an EMM (Enterprise Mobility Management) system for device deployment.

Installation

Device Tracker On-Prem client application 2.3.1 or earlier cannot be upgraded to 3.0. Prior versions must be uninstalled before installing Device Tracker 3.0. There are two methods for client app installation:

  • Manual installation - manually copy and install the client app to the device.
  • Remote installation - use Zebra's StageNow or an EMM (Enterprise Mobile Management) tool to create a StageNow profile for device deployment.

Manual Installation

Steps for manual client installation:

  1. Download Device Tracker On-Prem client from Zebra Support and Downloads. Extract the files:
         • DTRKClient.apk
         • com.zebra.devicetracker.dsd
         • EnableSelfSigned_DTRK.pdf
         • DisableSelfSigned_DTRK.pdf
  2. Copy and install DTRKClient.apk on the device.
  3. If updating an existing client, reboot the device.
  4. Open Device Tracker On-Prem client app.
  5. Accept the permissions when prompted. For Android 10 or later, select “Allow all the time” for the Location permission: Device Tracker On-Prem client notification
  6. Once the app is opened on Android O or higher devices, a Device Tracker On-Prem notification message is displayed in the device notifications drawer. This notification cannot be dismissed, indicating that Device Tracker On-Prem is running in the background. Device Tracker On-Prem client notification

Remote Installation

For remote installation, create a StageNow installation profile to install and setup the client app on the device using Zebra's StageNow tool or an EMM for device deployment.

To create a StageNow installation profile:

  1. Open StageNow on a host computer.

  2. In the StageNow home screen, click Create New Profile from the left menu.

  3. Ensure MX version 8.0 or higher is selected from the top drop-down selector. The MX version on the device should match this or higher. See MX documentation for instructions how to check the version.

  4. Select Xpert Mode from the list and click Create. Wizard selection

  5. Enter the profile name. Click Start.

  6. If using StageNow to copy the install file to the device, scroll down and click the plus (+) sign next to FileMgr. This adds FileMgr to the Config tab on the right side.

  7. Scroll to AppMgr and click the plus (+) sign next to it. This adds AppMgr to the Config tab on the right side.

  8. Repeat step 7 again. AppMgr is listed twice in the Config tab. Config list

  9. Click Add.

  10. If using StageNow to copy the install file to the device, proceed with this step. Otherwise, skip to step 11.
    StageNow Config 1 - Copy the install file to the device with FileMgr. In the FileMgr screen under the Create New Setting tab, select and enter the desired options to install the APK, for example:
         • File Action: Transfer/Copy File
         • Target Access Method: File in the device file system
         • Target Path and File Name: [enter file path]
         • Source Access Method: [select applicable method]
         • Source File URI: [enter information prompted]
    Click Continue.

  11. StageNow Config 2 – Install the client app. For the first AppMgr, select the following:
         • Action: Install
    Enter/select the desired options for the remaining fields. Click Continue.

  12. StageNow Config 3 – Battery Optimization. For the second AppMgr, enter/select the following:
         • Action: Application for Battery Optimization
         • Remove Application for Battery Optimization: com.zebra.devicetracker

  13. Click Complete Profiles. Profile creation is complete.

Device Deployment:

The device must be connected to the network during deployment. After creating the StageNow profile, use one of the following methods based on the desired tool for device deployment:

  • StageNow: Generate the barcode from the StageNow profile. Open StageNow client on the device and scan the barcode(s) generated from the installation, configuration and/or BLE profile.
  • EMM: Export each StageNow XML file from the StageNow installation, connection and BLE profiles. Do not edit the XML file - it can cause unexpected behavior. Send the XML using either OEMConfig or MX to configure the app and grant all required permissions. The installation profile and server connectivity profile XML files must be used separately.

Uninstallation

The Device Tracker On-Prem app can be uninstalled from the device either manually or by using StageNow. If using StageNow to uninstall Device Tracker On-Prem 2.3.1, scan the barcode in DTRK_UNINSTALL_FOR_2.3.1.pdf, provided with the download package from Zebra Support and Downloads.

Configuration

Configure the client settings either manually or remotely. For information on using CSP for remote configuration deployment, refer to MX documentation.

WiFi sleep policy "Keep Wi-Fi on during sleep" must be set to "Always" on Android Marshmallow devices for Device Tracker On-Prem to work in Doze mode. By default it is set to "Never".

Manual Configuration

Steps for manual client configuration after installation:

  1. Open Device Tracker On-Prem client.
  2. Grant all permissions requested by the app. If using an SSL certificate, proceed to step 4.
  3. If using a self-signed certificate, open the StageNow application. Scan the barcode from file "EnabledSelfSigned_DTRK.pdf" to enable self-signed certificates in the client app. The .PDF file is included as part of the Device Tracker On-Prem client installation package.
  4. Tap the hamburger menu at the top right, then tap "Settings".
  5. Enter in the following information:
    • Server URL - URL for the server with port number and Device Tracker On-Prem path specified, for example: hostname.company.com:8080/zdvc/dtrk, where "hostname.company.com:8080" is replaced with the appropriate hostname, domain and port number. The URL must not contain "https://" nor "http://".
    • Server Auth Key - user name designated during server install
    • Server Auth Password - password designated during server install
  6. Tap the device back button to save the changes and return to the main screen. Device Tracker On-Prem client registers with the server and loads "Devices to be found". If using an SSL certificate, manual client configuration is complete.
  7. If using a self-signed certificate, proceed as follows:
       A. Copy the self-signed certificate .CRT file to folder /sdcard/Android/data/com.zebra.devicetracker/files/cert on the device to establish communication with the server. The .CRT certificate file was generated from step 6 above in the Self-Signed Certificate subsection under Server Certificate.
       B. The message "Connected via untrusted certificate" is displayed in the app: Untrusted certificate message in client app
       C. To disable self-signed certificates in the app, scan the barcode from "DisableSelfSigned_DTRK.pdf" (part of the Device Tracker On-Prem client installation package).

Remote Configuration

After client installation, follow these steps to create StageNow profiles to remotely configure the client:

  1. Start Device Tracker On-Prem Service
  2. Configure Device Tracker On-Prem settings with CSP

Detailed procedures for each follow in the sections below.

When using StageNow or any EMM system for remote configuration, use of the following special characters is not supported (for example, when setting the password):
          < (less than)
          > (greater than)
          & (ampersand)
          ' (single quote)
          " (double quote)

Use of a StageNow profile which combines installation and configuration into a single profile is not supported. Two separate profiles need to be created:

Steps to create StageNow profile to start Device Tracker On-Prem service remotely:

  1. Open StageNow on a PC.
  2. In the StageNow home screen, click “Create New Profile” from the left menu.
  3. Ensure the proper MX version is selected at the top drop-down selector. This should match the MX version on the device. See MX documentation for instructions how to check the version.
    Select “XpertMode" from the table. Click Create.
    img Profile wizard
  4. Enter the profile name. Click Start.
  5. Scroll down and click the plus (+) sign next to “Intent”. This adds to the Config tab on the right side. Click Add.
    img Add Setting
  6. Enter the following information:
    • Action: StartActivity
    • Android Action Name: android.intent.action.MAIN
    • Package Name: com.zebra.devicetracker
    • Class Name: com.zebra.devicetracker.activity.MainActivity
      Due to changes with Android O and above, use StartActivity action to start the Device Tracker On-Prem service. Click Continue. img Configure Setting
  7. Click “Complete Profile."
  8. In the Publish section, select the desired barcode type. Click Test. img Generate StageNow barcode
  9. A window opens with the generated StageNow barcode in .pdf format. When ready to publish, click Publish.
  10. For EMM Staging, continue to section "Steps for EMM Staging" below.
  11. Open the StageNow client on the device.
  12. Scan the barcode generated to start the Device Tracker On-Prem service in the background.

Steps for remote client configuration with StageNow and CSP Plug-in:

  1. Download Device Tracker On-Prem client software DTRKClient.zip from Zebra Support and Downloads. The .zip file includes the following:
    • DTRK_PluginCSP.zip
    • DTRKClient.apk
    • DisableSelfSigned_DTRK.pdf
    • EnableSelfSigned_DTRK.pdf
    • DTRK_UNINSTALL_FOR_2.3.1.pdf
  2. Open StageNow on a PC.
  3. Import the CSP Plugin Library:
    A. In the StageNow home screen, click “CSP Library” from the left menu.
    B. Upload the DTRK_PluginCSP.zip file to the CSP Library by clicking “Choose File” then browsing to the .zip file, or by dragging and dropping the .zip file. Click "OK" in the confirmation message.
    C. Once successfully uploaded, the CSP Library is listed in the Plugin tab.
    img Import plugin into CSP Library
  4. Create a new setting:
    A. In the StageNow home screen, click “All Settings” from the left menu. Click “Create Setting” at the top right.
    img Import into CSP Library
    B. Select the MX version for the device and enter the following:
         • Setting Type: select “com.zebra.devicetracker"
         • Name: enter a name for the setting
         • Server URL: enter the server URL e.g. hostname.company.com:8080/zdvc/dtrk, where "hostname.company.com:8080" is replaced with the appropriate hostname, domain name and port number.
         • Allow edit settings: select the desired option to determine whether or not to allow the end user to edit the setting
         • Server Auth UserName: enter the "Server Auth Key" designated during server install
         • Server Auth Password: enter the "Server Auth Password" designated during server install
         • Enable self-signed certificate: enable/disable based on whether self-signed certificate is in use
    img Create New Setting
    C. Tap Save. The new setting is listed in the Settings screen. img New Setting created
  5. Create profile:
    A. In the StageNow home screen, click “Create New Profile” from the left menu.
    B. Ensure the proper MX version is selected at the top drop-down selector. Select “XpertMode" from the table. Click Create.
    img Profile wizard
    C. Enter the profile name. Click Start.
    D. Click the plus (+) sign next to “com.zebra.devicetracker”. This adds to the Config tab on the right side. Click Add.
    img Add Setting
    E. In the StageNow Config section, click “Re-use Saved Setting” tab. The screen is populated with the information from the setting created in previous steps. Validate all settings and click Continue. img Re-use saved setting
    F. Click “Complete Profile."
    G. In the Publish section, select the desired barcode type. Click Test. img Generate StageNow barcode
    H. A window opens with the generated StageNow barcode in .pdf format. When ready to publish, click Publish.
  6. For EMM Staging, continue to section "Steps for EMM Staging" below.
  7. Open the StageNow client on the device.
  8. Scan the barcode generated to configure the Device Tracker client with the settings specified.

For more information on StageNow, refer to its documentation and download.

Steps for EMM Staging (optional):

  1. Pre-requisite steps:
    • Follow procedure for "Device Tracker On-Prem remote configuration with StageNow and CSP Plug-in" up to step 6
    • Follow procedure for "Create StageNow profile to automatically bypass the device Battery Optimization pop-up message" up to step 11.
  2. Select "Export option for EMM" from the top to export the .xml file. Save the .xml file. img Export for EMM
  3. Push the .xml settings via EMM to the device for the desired client configuration.

See Also