Get Started

Before installing Device Tracker, perform the following steps to obtain Device Tracker licenses:

1. Follow the steps to procure Device Tracker licenses
2. You will receive a welcome email from Zebra which includes the following:
• Device Tracker web portal link
• First time login credentials. Reset the password for these credentials.
• .PDF file to configure the Device Tracker client app to connect to the Device Tracker cloud server.
• .XML file to mass deploy the Device Tracker configuration
The 2 files supplied are used for mobile client app installation.

Make sure all requirements are met. If a firewall or proxy exists, specific ports and domain names must be allowed; see Network Requirements.
To install Device Tracker mobile app on the devices:

• For manual installation, follow the manual install procedure. This includes scanning the barcode in the .PDF file provided by Zebra to configure Device Tracker with the cloud server settings.
• For EMM installation, follow the install using EMM procedure. This includes deploying the .XML provided by Zebra that configures the server connectivity settings.
• For StageNow installation, follow the install with StageNow procedure.

SSO enables a single login credential to securely authenticate with multiple applications and websites. Integrate with your identity provider (IdP) to authenticate users, ensuring transparent accountability and security during device check-out and check-in, so the appropriate role-based access is given. To integrate SSO with Device Tracker, follow steps to activate and integrate SSO. Then add SSO users and assign admin or manager roles to grant permissions to access the Device Tracker dashboard.

With SSO, user accountability can be enforced to track the user logged into the device by enabling Checkin/checkout. This prevents the user from gaining access to the device until their login is authenticated, in effect assigning that particular user to the device.

Create new user accounts based on role: administrator or manager. No user login is required for end users/associates unless SSO is integrated, in which case the user must login with their SSO credentials. If SSO is in use, follow the procedure to create SSO user accounts, otherwise follow the procedure to create non-SSO user accounts.

Managers and administrators can access the Device Tracker dashboard through the web portal or Device Tracker mobile app. The dashboard is a centralized view of devices, access points, and sites across an organization where action can be taken to track devices.

There are 2 methods to authenticate users:

• Device Tracker users (non-SSO) – In Device Tracker, add manager and administrator users to grant access to view the dashboard. Administrators can view data across all sites, along with other capabilities. Managers can view data specific to their assigned site. (Only managers and administrators need to be added.)
• Single Sign On (SSO) - SSO enables a single login credential to securely authenticate with multiple applications and websites. An existing SSO service is required. To use SSO with Device Tracker, follow steps to activate and integrate SSO. Then add SSO users to the allow list and designate the user as administrator or manager to grant permission to access the respective Device Tracker dashboard.

User accountability can be enforced, tracking the user checked in to the device. This is accomplished by enabling Checkin/checkout to prevent the user from gaining access to the device until their unique user barcode is scanned. When the user barcode is scanned, it assigns that particular user to the device, which can be viewed in the dashboard.

With SSO, user accountability can be enforced to track the user logged into the device by enabling Checkin/checkout. This prevents the user from gaining access to the device until their login is authenticated. After login, it assigns that particular user to the device, which can be seen in the dashboard.

Register sites to allow devices to be assigned to a specific site, for example based on geographical location. Grouping devices based on site location provides visibility of all devices assigned to that site. Data reports can be generated base on site location.

Register APs to aid in locating the device based on the AP friendly name, such as Frozen Goods. This allows a user to easily identify the AP location based on friendly name rather than the mac address when searching for a misplaced device. Additionally, this allows the option for a device to automatically be assigned to a site based on the AP it is connected to, eliminating manual device registration.

Register devices to assign a friendly name to a device to easily identify the device.

Workflow automation allows administrators to automate the task which determines what devices are at risk of being lost and then flag them to be recovered. This avoids the need for site managers to constantly monitor the state of their fleet of devices to determine which are at risk of being lost and then manually flag them to be found. By setting system thresholds, Device Tracker continuously monitors the state of devices and automates the process. To enable workflow automation, specify the conditions and/or thresholds that need to be met for the device to automatically change state. If a device meets any one or a combination of the defined thresholds or conditions, Device Tracker automatically flags that device as lost so that it can be recovered quickly.

Users located near lost or misplaced devices can be notified when the device is located nearby. If the lost device is detected in close proximity, an notification appears on the known device giving the option to recover the lost device and return it to production, allowing for proactive device recovery.

Yes, Secondary BLE allows a device to be located if it is powered off or has reached critically low battery (5% or less battery remaining). Device location is detected based on secondary BLE beacons transmitted, powered by the remaining device battery. Secondary BLE beacons are transmited as long as the battery is not completely depleted. When a device reaches a crtical low battery state, in general secondary BLE beacons can be transmitted for at least a few days - there are multiple factors that can affect this, including battery charge cycles, battery age, operating temperature, etc. Secondary BLE is supported only on select hardware, see device compatibility.

The dashboard provides a centralized view with real-time tracking information to monitor devices anywhere and anytime. This helps to identify devices that are at risk of being lost or misplaced and allows action to be taken to track devices. The dashboard is accessible to site managers and administrators - managers can view devices specific to their site location and administrators can view devices across multiple sites within the organization.

There are 2 types of dashboards:

• Web portal - dashboard viewable through a browser from a desktop or mobile device
• Mobile Client App dashboard - dashboard viewable through the Device Tracker client app

Administrators can generate historical data reports and view device events and utilization, providing actionable information to improve fleet usage and employee procedures. Devices must be assigned to sites in order to get the report data."

To initiate the process to find a lost or misplaced device, the administrator or manager first marks the device for retrieval by setting it to the To Be Found state in the dashboard. This adds the device to the To Be Found list visible to all device users in the mobile app.

To perform the device search, the user taps Start Finding. A Geiger counter-style interface appears a showing a proximity meter that indicates how close or far the user is located from the lost device. The user taps Play Sound to remotely ring the lost device so they can move even closer to the lost device. If the lost device has secondary BLE and is low in battery or powered off, it can still be located provided that secondary BLE is enabled in Device Tracker and the secondary BLE radio is still powered. By repeating this process of playing sound and using the proximity meter, the user continually moves closer to the device until it is located. Once found, tap Device Found to change the device state in the dashboard.

Users located near lost or misplaced devices can be notified when the device is located nearby. If the lost device is detected in close proximity, an notification appears on the known device giving the option to recover the lost device and return it to production, allowing for proactive device recovery.

To optimize the use of Device Tracker, execute or enable the following features:

• AP Friendly Name - Ensure the AP location friendly name is easily understood by users to identify the AP location which the device is connected to, such as sporting goods, when finding a device.
• Device-to-Site Assignment - Automatically assigns a device to a site based on the AP the device is connected to. This helps to automatically register new devices and avoids manual device registration.
• User Authentication - There are 2 methods to authenticate users:
  • Device Tracker users – in Device Tracker, add manager and administrator users to grant access to view the dashboard. Administrators can view data across all sites. Managers can view data specific to their assigned site. (Only managers and administrators need to be added.)
  • Single Sign On (SSO) - SSO enables a single login credential to securely authenticate with multiple applications and websites. An existing SSO service is required. To use SSO with Device Tracker, follow steps to activate and integrate SSO. Then add SSO users to the allow list and designate the user as administrator or manager to grant permission to access the respective Device Tracker dashboard.
• User Accountability - User accountability can be enforced, tracking the user checked into the device. This is accomplished by enabling Checkin/checkout, preventing the user from gaining access to the device until their unique user barcode is scanned, in effect assigning that particular user to the device as viewed in the dashboard.

  With SSO, user accountability can be enforced to track the user logged into the device by enabling Checkin/checkout. This prevents the user from gaining access to the device until their login is authenticated, in effect assigning that particular user to the device as viewed in the dashboard.

• Automation - Workflow automation allows administrators to automate the task of determining which devices are at risk of being lost and flagging them to be recovered. This avoids the need for site managers to constantly monitor the state of their fleet of devices to determine which are at risk of being lost and then manually flag them to be found. By setting system thresholds, Device Tracker continuously monitors the state of devices and automates the process. To enable workflow automation, specify the conditions and/or thresholds that need to be met for the device to automatically change state. If a device meets any one or a combination of the defined thresholds or conditions, Device Tracker automatically flags that device as lost so that it can be recovered quickly.
• Lost Device Nearby - Aids in device recovery by proactively sending alert notifications to a device when a lost device is detected within close proximity, giving the option to recover the device and return it to production.
• Generate Reports - Managers and administrators can generate historical data reports and view device events and utilization, providing actionable information to improve fleet usage and employee procedures.

Yes, Secondary BLE allows a device to be located if it is powered off or has reached critically low battery (5% or less battery remaining). Device location is detected based on secondary BLE beacons transmitted, powered by the remaining device battery. Secondary BLE beacons are transmited as long as the battery is not completely depleted. When a device reaches a crtical low battery state, in general secondary BLE beacons can be transmitted for at least a few days - there are multiple factors that can affect this, including battery charge cycles, battery age, operating temperature, etc. Secondary BLE is supported only on select hardware, see device compatibility.