Zebra DNA Cloud 5.6

Highlights

• Supports alphanumeric characters for app versioning
• Integrates with new backend licensing system, enhancing capabilities
• Streamlines workflow with refresh button in numerous sections
• Additional UI features and enhancements
• Adds support for PS30 devices running Android 14

Device Support

Required minimum LifeGuard software updates for devices running Android 11:

Required minimum LifeGuard software updates for devices running Android 13:

Required minimum LifeGuard software updates for devices running Android 14:

New Features in ZDNA 5.6

• Supports alphanumeric characters for app versioning in My Apps >> My Collection >> Add Apps
  • A new "Version Code” field allows for incremental, alphabetic build numbers for each app.
  • When using the Zebra Storage and Specified Server >> Upload option, the version code is automatically retrieved from the .apk and populates the Version Code field.
  • Keyboard entry in either field is supported when using the manual process.
• Transitioned to new backend licensing server:
  • The CLS ID is now known as "Batch ID."
  • Existing licenses have been transferred to the new system.
  • The 5% overage allotment for purchased licenses is eliminated.
  • The 30-day grace period for license renewal is eliminated.
  • ZDNA device licensing functionality and processes remain unchanged.
• Adds Refresh feature in ZDNA Console
  • ZDNA console pages can now be updated by clicking the Refresh button in the following sections:
    • My Devices
    • Device Settings
    • Listing Page
    • Setting Details Page >> Beside Selected Devices

New UI features and enhancements include:

• OS Build ID column added to Device Settings and My Apps >> Target Devices sections
• Now supports dynamic column adjustments in:
  • New Device Setup
  • Device Settings
  • Device Users
  • My Apps >> My Collection
  • Remote RxLogger
  • Android Updates >> Device View, Deployment, Automation

Requirements

• Refer to the System Requirements section in ZDNA documentation.

Usage Notes

• Zebra Apps in the My Apps collection must support the Android version on the device to which they are deployed.
• Device Location:
  • The feature does not function in restricted GMS mode or on AOSP devices.
  • To obtain the device's location data, Location Accuracy must be enabled.
• Device Presence:
  • For newly ZDNA-enrolled devices, presence icon displays immediately; "Last Connected" status is updated after about 10 minutes.
  • For devices enrolled in a third-party EMM system, device presence is enabled within 24 hours.
  • For existing ZDNA-enrolled devices, presence status is displayed after performing "Update zDNA client" action; “Last Connected" status is updated after about 10 minutes.
  • Presence status is displayed after performing "Update zDNA client” action; “Last Connected" status is updated after about 10 minutes.
  • Devices with an out-of-date "DNA client” (indicated by a yellow triangle ⚠️) must be updated to the latest client to see presence information.
  • The presence for existing and newly added devices running on an unsupported OS displays the presence status only after device is updated to the latest OS (in "Android Updates" section) and updated to the latest ZDNA client.
  • The presence changes from offline to online appear immediately in most cases but could take up to five minutes.
  • If the ZDNA service and/or its dependent components are terminated by the Android system due to a lack-of-memory condition, the system attempts to automatically recover when memory becomes available. Presence information for such devices reappears about 15 minutes after recovery.
• When using Advanced Settings, Stream configuration is NOT supported when exporting as .pdf files. (see UI Configuration > Volume UI Profiles > Volume UI Profile > Stream configuration).
• When first booting (or rebooting from either a cold boot or hard reset), all Zebra devices running Android 13 (or later) must be unlocked (using PIN, password or pattern) before the DNA Cloud client app can launch. Also applies to 6490- and 6375-platform devices running Android 11.

Known Issues

SDM660 devices running Android 11: DNA Cloud does NOT support the following device-OS update packages:

• HE_FULL_UPDATE_11-13-13.00-RG-U26-STD-HEL-04.zip
• HE_FULL_UPDATE_11-13-13.00-RG-U00-STD-HEL-04.zip
• HE_FULL_UPDATE_11-13-13.00-RG-U12-STD-HEL-04.zip

Regarding devices with the BSPs listed below:

• 6490-platform: AT_FULL_UPDATE_11-17-16.00-RG-U00-STD-ATH-04.zip
• 6490-platform: AT_FULL_UPDATE_11-19-15.00-RG-U00-STD-ATH-04.zip
• SDM660-platform: HE_FULL_UPDATE_11-31-27.00-RG-U00-STD-HEL-04.zip

For full ZDNA functionality on such devices:

• If already enrolled, generate a new barcode using ZDNA 3.11 or later, re-enroll and update to the latest BSP.
• If not already enrolled, generate a new barcode using ZDNA 3.11 or later and update to the latest BSP.

• Remote sessions automatically time-out after five (5) minutes of inactivity.
• The "Lock Screen Visibility" feature introduced with OEMConfig 13.3.0.5 is not supported. If enabled on the device, the lock screen appears blank on the ZDNA console during Remote Support sessions.

Resolved Issues - DNA Cloud

• Status now correctly shows as “In-Progress" after reapplying a device-setting or app-setup Profile.
• App Setup Profiles created with DNA Cloud 5.2 (or older) no longer require modification for compatibility with devices running Android 14.

Resolved Issues – Wireless Insights

• Wireless Insights deployment Profile can now be created using the "New Setup” button.
• Device quantities are now accurately shown on the Group Page.
• Assigning devices to a group now functions consistently.

Known Issues - DNA Cloud

• Results when filtering the "Status” column are sometimes reset or displayed incorrectly after navigating to another tab and returning to the filtered tab.
• IMEI info is not immediately displayed in the ZDNA console for devices running Android 14.
  WORKAROUND: Restart the device or wait 24 hours following device enrollment.
• Organizations using cybersecurity solutions such as Zscaler might encounter errors when uploading some .apk files to Zebra Storage.
• The "Update zDNA Client” button is disabled for 65 minutes whenever the user performs any device action from the "three-dots" menu on the My Devices page.
• The Zebra Ping authentication dialog sometimes displays “Unexpected System Error" when double-clicking (or sometimes single-clicking) the "Sign In” button.
• Devices running Android 13:
  • Zebra collection apps are sometimes NOT uninstalled when device(s) are removed from a group.
  • The "Enterprise” Wi-Fi Security Mode is not supported.
• When creating a managed configuration for Enterprise Keyboard, remapping a programmable key requires two backslash ("\\") characters (rather than one, as documented).

Known Issues - EKB Design Studio

• The System Bar in vehicle-mount devices occupies 10-15% more height than is displayed in the device simulator.
• Unchecking "Enable System Bar" and/or "Enable Status Bar" options in the editor page crops the layout on devices not set to a 9:16 aspect ratio.

Known Issues - Wireless Insights

• The Wireless Insights agent in the device sometimes stops sending Wi-Fi analysis events after a period of time. The issue has been observed on ET40, ET45, MC33ax and TC52ax devices.
  • REMEDY: Toggle Airplane Mode on and off.

Important Links

• About Zebra DNA Cloud
• Zebra DNA Cloud Setup
• Zebra DNA Cloud Licensing

About Zebra DNA Cloud

Zebra DNA Cloud integrates our Mobility DNA portfolio solutions into a single, intuitively organized interface. By harnessing our existing software's capabilities, we offer customers and partners secure solutions that help deploy, manage and support every stage of device lifecycles. With Zebra DNA Cloud, organizations can tailor device settings to meet their specific needs by leveraging Mobility Extensions (Mx). Application management and configuration of Mobility DNA tools will ensure users have access to the Zebra applications required to accomplish their work. Administrators can leverage LifeGuard OTA to ensure their devices are always up to date with the latest features and security, all with a single click and without having to touch each device physically.