Forum Discussion

StillLearning2002's avatar
StillLearning2002
Copper Contributor
Aug 01, 2022

M365 updates with Servicing Profile hasn't updated in a week, with 1 day install deadline, why?

Have machines that I am testing with M365 servicing profile.  These machines have been set up with servicing profile for probably 3-4 weeks at this point.  A new build of Office 365 Monthly Enterpris...
Microsoft 365 Apps for enterprise
Ruzitko's avatar
Ruzitko
Copper Contributor
Aug 01, 2022
I am experiencing extremely slow rollout in my organizations. I am not even using servicing profile, I have it setup via MEM Device Configuration policy. Semi-Annual going from Version 2108 (Build 14326.21018) to I suppose Version 2202 (Build 14931.20604). In Monitoring I can see only about 300 devices updated since the 12.07.2022. I wonder if MS stopped the rollouts or slowed them down significantly?
  • manoth_msft's avatar
    manoth_msft
    Icon for Microsoft rankMicrosoft
    Aug 01, 2022
    @Rutziko: By default, the rollout of Semi-Annual using MEM is staggered across multiple days. This month an issue was discovered, which delayed further progressing with the initial update from 07/12. On 07/26 Microsoft released a new build which is addressing the issue (link below), you should see more devices updating in the next days with the throttling ramping up.
    https://support.microsoft.com/en-us/topic/error-when-trying-to-open-an-accde-mde-file-created-in-a-different-version-of-access-f4cd36cd-549e-42ba-b75a-dfe964294a81
    • Ruzitko's avatar
      Ruzitko
      Copper Contributor
      Aug 02, 2022

      Hello Martin,
      thank you for reply.

      What I am seeing is about ~300 devices (out of 4k) got some update since 12.07.2022. I would expect they get at least the previous "bugged" update since then. Or does that mean once MS detected the version is bugged, the rollout was stopped by MS of that particular version?

      I am just asking so I know the workflow of the update releases. I need to report this to our customer, as they are worried the integrated Apps patching is not reliable (unlike pushing update via SCCM).

      • manoth_msft's avatar
        manoth_msft
        Icon for Microsoft rankMicrosoft
        Aug 08, 2022

        Ruzitko your assumption is correct. Once we detected the issue with the release from 07/12 (16.0.15225.20356 for MEC) and had a fixed release at hand (16.0.15225.20370), the Servicing Profile stopped triggering updates to the initial release. It automatically restarted to distribute the fixed released (around 07/26). That's why devices which were already flagged as 'completed' reverted to 'not started', as they did not have the latest release. Do you see satisfactory progress for devices which are in scope for the Servicing Profile now?

Resources