• Device Tracker 4.0 and later is the cloud-based version of the solution.
• Device Tracker On-Prem 3.0 and earlier is the on-premise server-based version. It is discontinued and no longer supported since December 2021.
• The cloud and on-premise solutions are incompatible with one another.
Overview
Device Tracker is a cloud-based scalable solution that easily tracks Zebra Android mobile devices, finds missing devices and helps prevent device inventory shrinkage. Misplaced or lost devices within a facility are tracked by leveraging existing Wi-Fi network infrastructure and utilizing Bluetooth technology and audio chirping to locate devices. When locating a device, Device Tracker identifies the general area where the device is located based on the Access Point (AP) it is connected to within the facility. The visual proximity indicator relies on Bluetooth beacon transmissions to determine the approximate location of the device. Audio can be played on the misplaced device to further pinpoint its location.
Video: Overview of Device Tracker
Main features:
- Cloud-based scalable solution hosted and maintained by Zebra with support for up to 100K devices in multiple locations up to 5K sites.
- Support for central administrator, site manager, and site associate roles.
- Device dashboard for administrator to centrally track devices across multiple sites with ability to view at site-level.
- Device dashboard for site manager to track devices at the site-level and mark a misplaced or at-risk (e.g. low battery) device for retrieval.
- Web portal for centralized administration of system settings and admin and site manager login credentials.
- Registration of:
- Sites and access points with friendly names to easily identify device location.
- Devices to assigned site with user friendly names for simple device identification.
- Simple to deploy – install and configure the mobile application using StageNow and Enterprise Mobility Management tools.
- Easily find a misplaced device with the connected AP location, the Bluetooth-based visual proximity indicator and play sound feature.
- Check-out/Check-in feature to associate users to devices for accountability. (Optional)
Device Tracker Comparison
Comparison of Device Tracker On-Prem and Device Tracker cloud-based:
| Features | Device Tracker On-Prem |
Device Tracker |
|---|---|---|
| Host platform | On-premise server, requires manual install and setup | Cloud-based solution managed by Zebra |
| Maximum Devices Supported | 500 | 100,000 |
| Site support | Single; multiple sites require individual server installation at each location | Multi-site; centralized in-the-cloud supporting multiple locations up to 5,000 sites without any additional install required |
| Server setup required | Yes, Windows server with required software and other system requirements | No, server is in the cloud and managed by Zebra |
| Android platform support | Only supported on select devices up to Android 10 | Only supported on select Android Oreo and Android 10 devices |
| Common Features | • Simple real-time device locationing with connected AP identification, Bluetooth-based visual proximity indicator and remote play sound feature • Registration of sites, APs and devices with friendly names for ease of identification • Misplaced and at-risk device prevention by monitoring low power and disconnection device states • Role-based access to find and manage devices based on administrator, site manager and associate roles • Centralized dashboard |
|
| Device Check-out/ Check-in |
No | Yes, identifies device user |
| Dashboard | Server-based dashboard view | Device-based dashboard view |
| Cost | Free | Licensed subscription service |
Supported Devices
See the supported devices table on Zebra support portal.
Requirements
Device Requirements
Requirements for Device Tracker client:
- Operating System - Only supported on select Android Oreo and Android 10 GMS devices. See Zebra support portal for supported devices.
- Bluetooth must be enabled to find devices using the visual proximity indicator. Zebra provides a tool (StageNow) for EMMs to configure the device remotely to enable Bluetooth.
- WiFi must be enabled and connected to the network to communicate with the server. Zebra provides a tool (StageNow) for EMMs to configure the device remotely to enable WiFi.
- Location services must be enabled on all devices to find devices using the Bluetooth-based proximity indicator.
Network Requirements
Network requirements for communication between the device client app and the cloud server:
Device Tracker client uses HTTPS to communicate with Device Tracker cloud server. All HTTPS communication normally uses port 443 by default, but this may vary based on network configuration. This port designated for HTTPS communication must be open.
The following domains must be allowed through the firewall or proxy.
Domain names accessed by device:
*.google.com(Required for Android to check internet connectivity.)connectivitycheck.gstatic.com(Required for Android to check internet connectivity.)*.googleapis.com(Required for Device Tracker to authenticate device communication and connect with the cloud server.)*.firebaseio.com(Required for Device Tracker to access the cloud database.)*.cloudfunctions.net(Required for Device Tracker to access the cloud server.)[ProjectID].firebaseapp.com(Required for accessing password reset link, where[ProjectID]is supplied by Zebra during onboarding.)
Domain name accessed by the admin on a PC:
- Web portal - supplied by Zebra during onboarding.
If the firewall or proxy does not support wildcards, add the following domains to the allow list:
www.google.com(Required for Android to check internet connectivity.)connectivitycheck.gstatic.com(Required for Android to check internet connectivity.)www.googleapis.com(Required for Device Tracker to authenticate device communication with the cloud server.)firestore.googleapis.com(Required for Device Tracker to access the cloud database.)cloudfunctions.googleapis.com(Required for Device Tracker to connect with the cloud server.)us-central1-[ProjectID].cloudfunctions.net(Required for Device Tracker to connect with the cloud server, where[ProjectID]is supplied by Zebra during onboarding.)[ProjectID].firebaseio.com(Required for Device Tracker to access the cloud database, where[ProjectID]is supplied by Zebra during onboarding.)[ProjectID]-default-rtdb.firebaseio.com(Required for Device Tracker to access the cloud database, where[ProjectID]is supplied by Zebra during onboarding.)s-usc1c-nss-*.firebaseio.com(Required for Device Tracker to access the cloud database, where*represents multiple characters. Since*can change over time, the firewall needs to allow any domain with this pattern for the app to function.)[ProjectID].firebaseapp.com(Required for accessing password reset link, where[ProjectID]is supplied by Zebra during onboarding.)
If the password is reset, an email is sent from zdtrksupport@zebra.com.
Known Issues
Known issues in Device Tracker 4.0:
- When installing the application on a mobile device using an EMM, some EMMs do not grant all the required permissions for the application to run in the background to track the device. Alternatively, an XML file can be generated from the StageNow profile and consumed by the EMM granting all permissions. Refer to the Install guide
- After repeatedly launching the Device Tracker application over several weeks without rebooting the device, the app may become unresponsive. If this occurs, relaunch the application to continue operation. A fix will be provided in the next release.
- When there are multiple pools of licenses with different expiration dates, an incorrect or negative license count is reported when the licenses expire.