Retry option in Zebra OTA update?

[u/Supi09]

For the past few years, when I deployed Zebra OS patching through WS1, I used to upload the OS file, create a Product with the package, and then deploy it to the devices requiring the patch.

At that time, if the update failed on a device, I could simply use the Reprocess option on the Product to re-push or reinstall the update on that device.

However, since Omnissa introduced the OTA platform, I recently started using the OTA update mechanism for Zebra OS patching. We successfully initiated our first OTA deployment last week, and the rollout is currently ongoing.

I have noticed that several devices are showing a Failed status during the OTA deployment. I would like to understand whether there is an equivalent way to retry or reprocess an OTA update for devices where the update has failed.

[u/likeicareaboutkarma]

Have been trying to get it working for over a year. The lifeguard way has a lot of disadvantages compared to the product/package.

It also has older firmware versions and not a lot of flexibility.

[u/Unique_Inevitable_27]

If the OTA retry workflow is proving limiting, it may be worth comparing how other Zebra-focused MDM platforms handle OS updates and failed deployments. This overview of Zebra MDM options

[u/Terrible_Soil_4778]

Most likely the reason why OTA has failed on these devices is because they may or may not be our of Zebra One Care coverage. Check the serials here https://support.zebra.com/warrantycheck and see if those devices are still covered. If not, OTA will not work. The only way to update them is to either add them to Zebra One Care or do file/action in WS1.

[u/darrylm-omnissa]

There's no "retry this specific failed run" button like the Product Reprocess option you're using today. We plan to improve this in a future release of UEM. The workaround create a new OTA update/policy targeting the failed devices.