Forum Discussion
Managed configuration not getting pushed onto some devices in work profile
My team uses AMA API to managed devices. As part creation of enrollment token we push some applications and managed configuration to those applications as part of the policy. But we are noticing that this is not very reliable. We have many user stories where the app gets installed but the managed configuration is missing. This doesn't happen on all devices but the occurrence of this has been increasing. Is there any known issue or SLA on how long it takes for the managed configuration to be pushed?
We have an Application that is set as Required for Setupin the policy. This Application has managed configuration setup, which is required for App registration. This is missing by the time app launches and app registration fails and consequently the work profile provisioning fails.
FlorianLizzieHas this issue been rolled out across the board?
We are suddenly, as of a week or two ago, and right now, experiencing this exact issue.
Our companion app, set to required for install and setup_action, is stuck on continuing its setup process due to managed configurations not arriving.
We use managedconfiguration rather than managedconfigurationtemplate for this particular app, as its part of every policy a device receives and is our companion app.
We have noticed, that in some cases, the same device will continuously fail to receive the managed configuration even after multiple factory resets.
The only way we have been able to force a device through the process, is to patch its policy with one that does not contain the managed configuration, then patch it again with the managed configuration and this then forces through the managed configuration and the app continues its process as normal.
Happy to raise a ticket, but before i do i just wanted to check what the status was of the fix.Hi Robert, the issue has actually been fixed by the engineering team, but the rollout takes one month to complete. Final ETA is on April 15th, according to the support team.
If you're deeply impacted, you can still ask support to push the fix to specific organisation IDs. It's something they can do as a last resort.
Hope this helps!
Thank you Lizzie, Is it possible to share the ticket so that i can track too.
Same on our side with the AMAPI, for both work profile and fully managed devices. I created a ticket for this a couple of weeks ago. According to the support, the Engineering team is working on it. Let's hope it's getting fixed soon.
