跳到主要内容

106: Zebra FOTA

Implementation Effort: Medium to High
User Impact: Medium

Overview​

For Zebra devices used in retail, warehousing, healthcare, and field operations, firmware currency is a major Zero Trust concern because these devices often remain in service for years and operate outside traditional office networks. A modern Zebra update strategy should let you deploy approved OS, security, and device firmware updates through controlled rings, with clear maintenance windows, rollback planning, and visibility into which devices are behind on security servicing.

Implementation Guidance​

  1. Inventory the Zebra models, Android versions, and support contracts in use. Confirm which devices and firmware channels are supported by your chosen Zebra and Intune management approach before designing policy.
  2. Decide whether you will manage updates through Zebra-specific update tooling, OEMConfig, or another supported integration pattern with Microsoft Intune. Document the authoritative source for firmware approval so admins do not publish updates ad hoc.
  3. Create deployment rings for test, pilot, and production devices. Frontline hardware should not all receive firmware updates at once; include at least one validation ring that mirrors the most critical scanner, kiosk, or tablet workflows.
  4. Use maintenance windows that match operations. Zebra devices may be in active use across shifts, so charging state, Wi-Fi availability, battery thresholds, and local staffing should be part of the deployment plan.
  5. Monitor post-update health. Validate scanner behavior, peripherals, line-of-business app compatibility, Wi-Fi roaming, certificate trust, and kiosk restrictions after each firmware wave.
  6. Define a break-glass process for halted or failed updates, including spare-device handling and who can approve emergency rollback or hold actions.

Reference​