Switch Office 365 Semi-Channel to Monthly Targeted Channel

By Default, Microsoft Releases Office updates new Features in the three options Monthly Channel, Semi-Annual Channel, Semi-Annual Channel (Targeted).

If your organization blocked Monthly channel and allows for Semi-Annual Channel(Targeted). Ideally, it is good practice to allow only a few peoples to test the new features to pilot before enabling it for complete users.

We also block Office updates from through the Group Policy. If Pilot users allowed in the targeted channel, those users also get blocked from the Update to the Monthly Channel.

The Office 365 ProPlus update model supports 4 production channels;

  • Monthly Channel (Targeted),
  • Monthly Channel,
  • Semi-annual Channel (Targeted),
  • Semi-annual Channel.

In the below steps, we will see how to convert the Semi-Channel to the Latest version.

  1. Launch PowerShell as an administrator.
  2. Navigate to “C:\Program Files\Common Files\Microsoft Shared\ClickToRun\”

3. Run the following command 

.\OfficeC2RClient.exe /changesetting Channel=Monthly

4. Run the following command 

.\OfficeC2RClient.exe /update user

It will start updating the latest version.

6 thoughts on “Switch Office 365 Semi-Channel to Monthly Targeted Channel”

  1. For step 3, the command should be:
    .\OfficeC2RClient.exe /changesetting Channel=Monthly

    It’s missing the leading period. Hope this helps someone 🙂

  2. In step 3, the command is missing the starting period. Rather than “\OfficeC2RClient.exe /changesetting Channel=Monthly”, it needs to be “.\OfficeC2RClient.exe /changesetting Channel=Monthly”

  3. Keep getting the bellow error when entering the navigate to line of
    (your instructions point 2). Not used to powershell so this could be something simple, but would appreciate your help. Thanks, Matt

    C:\Program : The term ‘C:\Program’ is not recognized as the name of a cmdlet, function, script file, or operable
    program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Leave a Reply

Your email address will not be published. Required fields are marked *