I think with "inventory view" you mean "View devices" or is there something else?

But when i'm there and choose on the assigned device (TC51 with LifeGuard-Update 14) the firmwareupdate i get an error message:

What OEMVersion is the TC51 currently running? It may not meet the minimum threshold of Android N + LG19.

Sorry i missed to dsay that we are using only Oreo in this System on the Zebra TC51. So it's Oreo with LGU 10 or 14.

I have done all requirements. Where i can see if ZDS is enabled? I only found this regarding that:

Is there maybe any Port or IP which should be opened in the network (firewall/proxy)?

Hi Rafael,

Thank you for requesting an answer to this post.

From the documentation, ZDS should be enabled by default:

• Enroll Zebra Devices for LifeGuard OTA Firmware Upgrades (soti.net)
• Zebra Data Service Setup - TechDocs

As long as you are meeting the above pre-requisites then I suggest opening a case with SOTI Support so we can have more of an in-depth investigation. You can open a case by logging it online (Log a Case (soti.net)) or by emailing support@soti.net.

In the meantime you could workaround this by using the .ZIP upgrade method as mentioned by Matt: OS Update (Single Package) Using SOTI MobiControl Mxconfig Script (zebra.com)

Kind regards,

I just know about the possibility to use the package/zip-file solution.

I used that in the past. But i think if FOTA is possible we want to use that, to not upload a very big package to soti.

I saw now following in device details:

Is that something which could help you to say me whats going wrong here?

And i'm bit confused that i don't have to put in a token in the configuration of Zebra Enrollment Manager, is that correct?

And i just saw in your Links following Note: "Bypassing the Android Setup Wizard also bypasses the EULA Setup Wizard"

Would this cause any problem? We used StageNow Bypass Barcode for StageNow Staging. (We just switched few days ago to Zero-Touch enrollment on the Zebra devices too.

I think we (hopefully) get this kind of OS Update for other manufacturers too. So this could be some kind of "getting a feeling" how it could be to them in the future too.

But generally it would prefer not upload every time a big package to the server when there could be a solution which redirects to the server from Zebra and get the files there.

I just took a look again on the device an not it seem to work but we didn't change anything. A bit strange.

Ok, it says it's downloading but it seem interrupt regular.

Is there any Port/Address to be opened on Firewall/Proxy?

Hi Rafael,

Thank you for requesting an answer from us.

I would like to clarify this token requirement as well as your Firewall/Proxy question with our product management team first. If you have any further questions in the meantime please do not hesitate to let us know, but I will aim to get back to you in due course.

Many thanks,

Hi Rafael,

Thank you for requesting an answer from us.

I would like to inform you that you don’t need to enter the Enrollment Token in the configuration of Zebra Enrolment Manager. Just set the “Enable Managed App Config” toggle to “ON” state and select “Action” field value to “Claim Device”. Enrolment token will be automatically picked up from backend during the enrolment process.

Regarding Firewall requirement, Please let us know  if you have any network restrictions on device or on the server where MobiControl is hosted.

I have to ask outr hoster about that but our devices are behind firewall and proxy, so i was just thinking of them not of mobicontrol itself because the device gets announcement that there's an update, you can send an "install update" via mobicontzrol and it seem it's trying to do so but nothing happens.

So i think it could be something regarding "getting the update file".

Is there anything i can trigger the update via script or on the device itself?

I send the command "Update Firmware" from the console but actually nothing happens.

And on a second device:

But it seem not to "retrigger".

Hi Rafael,

When you reproduce the problem, are you seeing any error codes in your MS/DSE Verbose Logs? Could you provide the error lines within your logs and I can cross-reference internally to see what the issue might be.

Also as a suggestion, I recommend you raise a Support Case via support.eu@soti.net. We can then break down the issue and move forward.

Regards,

I have to ask our hoster for that, can take a bit time because there are actual much more important issues to be fixed.