A: The current ZDS agent is implemented as two files:
- Zebra Data Service | Main analytics engine (2 MB)
- Zebra Data Service Plugin | Data collection plug-in (0.2 MB)
Both components listed above must be running and enabled for proper data-collection operations.
A: ZDS uses the servers shown below. Devices running Android 10 (and later) require connectivity with both servers:
ZDS Server #1:
- IP Address:
ZDS Server #2:
- IP Address:
This server uses Certificate-based Mutual Authentication.
Zebra recommends using DNS server names (instead of IP addresses) when whitelisting (aka "allowlisting") to avoid service interruptions and required router changes if IP addresses change in the future.
A: Zebra recommends using ping or a similar network tool to confirm communication between the device network and the ZDS server(s). Once such a connection is verified, all devices on that network should be able to connect to and send collected data to the server(s).
The Zebra Data Service itself uses
connectivitycheck.gstatic.com, which also must be visible on the network for ZDS operation.
A: The default upload frequency is once every 24 hours.
A: No, the upload time is different for each device. It begins when the device is first powered up and cannot be changed or configured to vary by connection or network type. The first upload occurs approximately 24 hours after first boot. Upload times are designed to vary randomly by three minutes (plus or minus) to help spread inbound server traffic throuhgout the period. To view the latest upload time for a device, see Check ZDS Status in the Setup guide.
A: ZDS stores a maximum of 70 KB on the device each day.
A: ZDS sends a maximum of 2 MB of (compressed) data with each upload.
A: ZDS data can be viewed on the Zebra Foresight server.
A: The size of ZDS components can vary, but its maximum download size is about 10MB* in total. The system consists of the following components:
- ZDS Client and Plug-in components (combined size: 2.2–4MB)
- Zebra Common Transport Layer (about 4MB)
- Zebra Life Guard Enablement (LGE) Client (about 2MB)
*Not all components are downloaded with every update.
A: Yes, Zebra updates one or more ZDS components every 3-4 months.
A: ZDS polls Zebra servers for updates once every 24 hours and every time the device reboots.
A: Not directly, but ZDS updates can be prevented by using an enterprise mobile management (EMM) system to lock device apps to a specific ZDS version. However, Zebra recommends keeping ZDS updates enabled to ensure the highest levels of security, stability, feature enhancement and bug fixes.
A: Yes, ZDS allows changes to the following parameters:
- Data collection (On/Off)
- Upload frequency (default = once every 24 hrs.)
- Data collection for certain individual events
A: The ZDS settings on a device can be changed in two ways:
- Through the device UI (see Setup section).
- By scanning a barcode that contains changes to the Analytics Manager CSP.
Contact Zebra support for more information about changing ZDS parameters.
A: The barcode for changing ZDS settings on a device is generated using Zebra StageNow. Learn more.
A: ZDS collects data about device hardware, app info and usage, network communications, location and many other parameters. See the About ZDS page for a complete list of data collected.
A: Most Zebra devices support data collection. See the About ZDS page for the full list of supported devices.
A: Reporting of RUL information is best supported on devices running Android 7, 8 and 10 (and later). On devices running Android 4, 5, 6 and 9, Remaining Useful Life reports are less accurate.
A: Some older versions of the ZDS agent did not display the end-user license agreement screen. To view the EULA, update ZDS to the latest version. Contact Zebra support for more information.