The other day I came across an issue when trying to create and deploy a new firmware update to my Zebra devices in my test tenant. What happened was that when I tried to finalize and clicked on “Create” on the “Create + Review” page, I just got an undescriptive error message and the deployment was never created.
When I tried looking at the Request error details it didn’t really help me either since it just said Bad request.
{“error”:{“code”:”BadRequest”,”message”:”An error has occurred.”,”details”:[],”innerError”:{“date”:”2023-12-27T08:31:09″,”request-id”:”f04329e1-6f28-4db5-9209-56ff14e5b833″,”client-request-id”:”a35a7de7-274b-457e-8d0e-2a00fbab40f6″}}}
The connector was under Tenant Administration -> Connectors and tokens -> Firmware over-the-air update was still functional and looking all healthy.
Solution
After going through the documentation and just making sure I had everything in place to use FOTA updates (which I previously have used in this tenant), I realized that FOTA updates have become generally available and I did not have any licenses for FOTA in this test tenant. During the preview phase of FOTA updates, it was free to use, but when it became GA, it required Intune P2 licenses.
I bought an Intune P2 license and as soon as I did that and tested everything started working as expected. What probably happened was that since I had already configured and used FOTA updates during the preview period, once it became GA and I did not have a P2 license I was no longer able to create new deployments, though the error message did not mention anything like that. I’m just speculating right now, but this is the best conclusion I could come to. FOTA Updates work just fine now once I added the license to my tenant.
That’s it for this time, Don’t forget to follow me on X (twitter) @timmyitdotcom or connect with me on LinkedIn
One comment