Forum Discussion
Servicing Profile M365 updates have not started after 4 days.
I continue to have issues with M365 apps updates not starting on patch Tuesday. It is now Friday and none of my systems have updated. I have set Servicing Profile to include all devices, no devices are excluded, I created 3 rollout waves and have a 3 day period between, I am using Azure Security Groups to manage the waves. Almost all of the computers have checked in since Tuesday yet all devices are listed as not started. Any known reason why these updates would not start on time? This is the third month in a row for this issue. The past two months the updates would all start to send at 2PM Wednesday and it would flood the network causing other issues.
10 Replies
Today, 20-July-2022 the Office 365 Servicing Profile of July for our customer is not started after 4 days.
Wave 1 (after 4 days) is not running at all.
However, only 1 system was updated, and that was not a system from Wave 1 , but a system from the "remaining devices" wave.
Also when I checked devices and their builds in Inventory, there is only that single device from the remaining devices taht is updated to the July build.
Is there another issue then described on the "notifications" section?
Hope 365 servicing team can check our customer tenant.
dimehtaMicrosoft
Could you please share your tenantID at dimehta@microsoft.com ? My team and I will look into the specifics and keep you posted.
- manoth_msftIssues should be resolved, please verify. If you still don't see devices getting updated, please submit feedback directly from the Servicing Profile overview page. Include email, so we start investigating your tenant and reach out to you if needed.
manoth_msft The issue is resolved, I paused the rollout for several hours and then restarted and systems started to update. I had to do this for each wave. Are you implying that on 7/12 wave 1 should start and then each of the other waves will start without intervention?
- manoth_msftCorrect, with the bug fixed on our end, waves will start automatically when the specified # of days have passed.
- manoth_msftThanks for reporting. We have our engineering team looking into the issue.
- Hab exakt das gleiche Problem das scheint auch kein Anzeigefehler zu sein, habe einige Geräte im Unternehmen überprüft und die sind alle noch auf der Version 2203
