System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

How can we improve Configuration Manager?

SCCM ability to change office 365 channel like in GPO Settings

Would like to be able to change O365 Channels for Clients in SCCM,
Like you can in GPO... currently GPO wont honor the channel I want because SCCM is managing the O365 Client.

40 votes
Sign in
Sign in with: Facebook Google
Signed in as (Sign out)
You have left! (?) (thinking…)
Danny shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Sign in with: Facebook Google
Signed in as (Sign out)
  • Stephane commented  ·   ·  Flag as inappropriate

    Hi agree, providing options to change update channel from Monthly to semi-annual or semi annual targeted to semi-annual. We need this because we need an easy to have testers come and go (testers would be on the SA targeted channel) so reverting to semi annual is a must.

  • Michael Klein commented  ·   ·  Flag as inappropriate

    The ability rollback a version and downgrade channels seems to be a BIG miss from Microsoft.

  • Ann Sumner commented  ·   ·  Flag as inappropriate

    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.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Matthew DeBoer,

    I thought GPO is setting that registry key? And then it picked up by SCCM? Is that wrong?

  • Tom Wahab commented  ·   ·  Flag as inappropriate

    Yes this would be a great benefit and ease of administration when deploying O365 Updates with SCCM. If we can administer the Channel native in SCCM, that would be huge Plus, instead of looking for workarounds or reghacks to change the channel.

  • Matthew DeBoer commented  ·   ·  Flag as inappropriate

    It appears that ConfigMgr does not check the group policy location to detect what updates are required. It does however check the CDNBaseURL at HKLM:\\SOFTWARE\Microsoft\Office\ClickToRun\Configuration

    I have tested that deploying a configuration item with the appropriate CDNBaseURL causes the client to detect updates from the desired update channel. These updates also successfully install. I am not certain however if/when these urls change or if this would be supported.

    Here are the current CDNBaseURL options for 2016:

    'Deferred' = '';
    'FirstReleaseForDeferred' = '';
    'Current' = '';
    'FirstReleaseForCurrent' = '';

    You can verify these by comparing them to the content location of an update from the channel you want the client to install.

Feedback and Knowledge Base