Skip to main content
T
THTClient
New Member
December 4, 2025
Solved

Forced Auto Install Issues

  • December 4, 2025
  • 3 replies
  • 0 views

Since mid-November '25, forced auto install is not functional for our organization.  Apps are loaded and installable as work apps but do not progress as an auto install from our policy.

 

Has anyone experienced a similar issue?  No policy changes, no SW updates on the MDM client.  Functionality just stopped working.

Best answer by THTClient

Team-

Just reset our Google  Workspace account and now everything is working again.  We had a former employee  responsible for this and didn't close the gap when they left.

3 replies

C
collin-93
New Member
December 7, 2025

It sounds like a recent change in Android or the MDM server may have affected forced auto-install behavior. Check if there were any backend updates, policy enforcement changes, or Android 15 updates that could impact auto-install. Reviewing device logs and MDM audit reports can help identify why apps are no longer auto-installing, even if manual installs still work.

    Emilie_B
    Emilie_B
    Community Manager
    December 8, 2025

    Thank you for your assistance @collin-93 🤩

     

    @THTClient could you give us a quick update and let us know if you still need help solving this issue? 

    T
    THTClientAuthor
    New Member
    December 9, 2025

    We discovered this morning that our profile was tied to an old G Suite  account that is no longer supported.  Hoping to re-establish this so we can accept the Terms and Conditions in Play to re-enable the functionality.  I will update the thread if this fixes the issue.

      Emilie_B
      Emilie_B
      Community Manager
      December 9, 2025

      Sounds good @THTClient - keeping everything crossed 🤞

       

       

      K
      kirk-467
      Level 1.5: Cupcake
      December 10, 2025

      A few teams have reported similar forced-install issues recently, so it may be a wider backend problem rather than your MDM setup. You can try re-syncing the device and policy, confirming the app is still marked as required, and pushing a small policy update to trigger a fresh pull. It’s also worth checking whether Play EMM services are showing any delays. If everything looks correct, it’s likely not a configuration issue on your end

      Terms & ConditionsCookie settingsAccessibility statement