40 votesAnn Sumner commented
If the original option is not a valid one, another option would be to allow the GPO Update Channel to not only apply the change to HKLM:\\SOFTWARE\Microsoft\Office\ClickToRun\Configuration\UpdateChannel but also HKLM:\\SOFTWARE\Microsoft\Office\ClickToRun\Configuration\CDNBaseUrl which it seems is where configuration manager detects the channel version from.
4 votesAnn Sumner commented
There is a workaround:
You can manipulate the default language that will be detected by creating a Configuration.XML file and importing these settings into the wizard.
Copy and paste the following into Notepad and save the file as Configuration.XML to a location that can be accessed, within the wizard select “Import Office 365 client settings from a configuration file:” you can then continue through the wizard without error.
<Add OfficeClientEdition="32" Channel="Current" Version="16.0.7766.2060">
<Language ID="en-US" />
<ExcludeApp ID="Groove" />
<Display AcceptEULA="TRUE" />
<Property Name="SharedComputerLicensing" Value="0" />
<Property Name="PinIconsToTaskbar" Value="TRUE" />
<Property Name="AUTOACTIVATE" Value="0" />
Updated to Noted. We’ve been discussing the same in our planning meetings.
BobMN on behalf of SangeeV for SCCM OS Deployment