Jul 26 2022 08:06 AM
Hey folks,
I experience a strange behaviour when updating my M365 Apps. I initially wanted to switch from the Enterprise Monthly Channel to the Beta channel and set a local GPO (Computer Configuration - ...- Microsoft Office 2016 (Computer) - Updates - Update channel). This did not work.
Then I used the ODT and a customized XML to switch to the Beta channel. This worked perfectly and I am on Build 2208.
However, when I choose to update Office ("Account - Update options - Update now"), updates are found and installed even with this current build and when I re-open Office I am back in the Enterprise Monthly channel.
I am able to reproduce this by starting from scratch (custom XML) and then choose "Update now" again.
Is this a bug or a feature? 😉 Or is there meanwhile an admin option to force users to stay in the channel chosen in the M365 admin center? I could not find anything about this...
Thanks in advance for your replies!
Best regards
Ben
Jul 27 2022 02:19 PM
Solution@Ben-neB if this is due to a policy, you can confirm by checking the following registry locations:
HKLM\SOFTWARE\Policies\Microsoft\office\16.0\common\officeupdate
HKLM\SOFTWARE\Policies\Microsoft\cloud\office\16.0\Common\officeupdate
Jul 27 2022 03:16 PM
@BobClements no, my client is not part of any AD and our company does not use Intune for management either.
The only policy was set by me as mentioned above but it did not change anything.
Jul 27 2022 03:21 PM
Jul 27 2022 03:26 PM
@BobClements Please read my initial post - I already did that.
Jul 28 2022 01:00 AM - edited Jul 28 2022 01:01 AM
@BobClements I took another look at the registry and you were right - I found the other registry key containing settings for Office:
"HKLM\SOFTWARE\Policies\Microsoft\cloud\office\16.0\Common\officeupdate"
(the default path is ...\Policies\Microsoft\office\16.0\...)
There the updatepath value was set to the CDN URL for Monthly Enterprise. I switched that to Beta and now it stays on Beta. I think this has something to do with the MS security baselines which I imported some months ago.
Thanks @BobClements for pointing me into the right direction!
Best
Ben
Jul 28 2022 03:59 AM
Jul 27 2022 02:19 PM
Solution@Ben-neB if this is due to a policy, you can confirm by checking the following registry locations:
HKLM\SOFTWARE\Policies\Microsoft\office\16.0\common\officeupdate
HKLM\SOFTWARE\Policies\Microsoft\cloud\office\16.0\Common\officeupdate