Forum Discussion
MicrosoftConfiguring fallback for Office 365 ProPlus updates in Configuration Manager
Thanks for the writeup, I'm a little late here but have a question I'm hoping you can answer. Is this same functionality available using the ODT or GPO/Intune MDM Policy? I see there is an "AllowCdnFallback" option in the ODT configuration XML (https://docs.microsoft.com/en-us/deployoffice/configuration-options-for-the-office-2016-deployment-tool#allowcdnfallback-attribute-part-of-add-element) but that seems to be for deployment (ODT download/configure modes), but not for updates.
- chhopkinThe fall back option in the ODT configuration XML is for the scenario when you are deploying from a local source (typically via a manual process or a management tool other than Configuration Manager). For both the initial installation or the update process.
If you are using Intune everything comes from the CDN so no need for fall back in this case. - chhopkin
Hi Jeremy,
This is a different fall back mechanism.
The 'AllCdnFallback' option that you use with ODT is specific to the installation of language packs. It allows you to install Office from a local source (like a network share) but if you forgot to download a language pack or MatchOS discovered a language pack that was not downloaded to your local source, having this fall back option on allows the ODT to download the language pack(s) that it needs directly from the CDN. Note: this option is not compatible with Application deployment via SCCM.
The option available in SCCM applies to updates. If a client is told by SCCM to update but the update is not yet available on the distribution point, the client is allowed to get the update directly from the CDN.
Cheers,
Chris
chhopkin- Happy Holidays!
I am using the following lines in my config.xml and deploying during OSD as an Application in SCCM (1806).
<Configuration>
<Add OfficeClientEdition="32" Channel="Broad" OfficeMgmtCOM="TRUE" AllowCdnFallback="TRUE">
<Product ID="O365ProPlusRetail">
<Language ID="MatchOS" />
<Language ID="en-us" />My source files on the local distribution point only contain the installation for en-us. You stated that this not compatibile with the Application method of SCCM? It will not use the CDN to download the missing Languages if the you are deploying Office 365 ProPlus in this manner? Is that documentend somewhere?
I have to manage over 20 different languages of the OS and Office, it would be ideal to have this working instead of having 19 additional deployment types/applications for each Office language.
Looking forward to your response.
- Thanks very much. Can't wait to eventually see this same fallback functionality when using a local share or https for updates (hopefully).
