Forum Discussion
chhopkin
Microsoft
MicrosoftConfiguring fallback for Office 365 ProPlus updates in Configuration Manager
Starting with version 1706 of System Center Configuration Manager a new option is available allowing administrators to enable clients to fall back to the Microsoft Office CDN when deploying Office 36...
Regarding the fallback behavior, I recently analyzed a client machine that was set up to receive the latest update for Office 365 ProPlus semi-annual v1708. In the middle of that, one of our support techs disabled the config manager client because the user was having some issues with software installs unrelated to O365. Fast forward about a week and he re-enabled the config man client. The ProPlus client did get an update successfully, but it was for v1803, not 1708 of semi-annual channel. So my questions are:
- Does it seem reasonable that the CDN fallback was used because the config manager client was disabled before the update from SCCM could be completed?
- Is the fallback going to grab the latest version of semi-annual channel from the CDN as opposed to the one we've specified for distribution via SCCM?
Thanks for any assistance,
Doug
chhopkinMicrosoft
MicrosoftHi Doug,
When an update is targeted to a client, the Configuration Manager agent tells C2R to install that specific version. If the Configuration Manager fallback option was enabled and the DP did not have the version then the client would fall back to the CDN to get the version specified by Configuration Manager. If the Configuration Manager agent was disabled on the client then it should have never updated unless the OfficeMgmtCOM setting was not set to True on the client. This setting tells C2R to not check for updates and wait to be told what to do by Configuration Manager. FYI - the OfficeMgmtCOM setting is stored in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration along with the installed version and other C2R settings.
Cheers,
Chris
When an update is targeted to a client, the Configuration Manager agent tells C2R to install that specific version. If the Configuration Manager fallback option was enabled and the DP did not have the version then the client would fall back to the CDN to get the version specified by Configuration Manager. If the Configuration Manager agent was disabled on the client then it should have never updated unless the OfficeMgmtCOM setting was not set to True on the client. This setting tells C2R to not check for updates and wait to be told what to do by Configuration Manager. FYI - the OfficeMgmtCOM setting is stored in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration along with the installed version and other C2R settings.
Cheers,
Chris
