Manage Office 365 Update using SCCM 1706

Jonathan LefebvreSCCM19 Comments

Today, we are continuing our posts about SCCM 1706 improvements. One area that has been updated is how to manage Office 365 updates.

In this post, we will detail the improvements on Office 365 updates with SCCM 1706 on the server side and client side.

If you are looking for how to update Office 365 with SCCM prior to Current Branch 1706, please see our post here, which is still relevant to date.

Important Info
Microsoft as released an Update rollup for SCCM 1710 to address the Office 365 client updates

If you are still running SCCM 1706, we strongly encourage you to go forward to 1710 with latest KB as the changes are working much better than what was available in SCCM 1706.

See our guides to Upgrade to SCCM 1710 and to install latest Update rollup KB4086143

Under SCCM 1710 with Update rollup 2, if an Office 365 product is running, a reboot will be mandatory just like regular Windows Update.

Depending on your deployment configuration, the reboot will display accordingly to SCCM client configuration.

Manage Office 365 Update SCCM 1706

Manage Office 365 Update SCCM 1706

This is much better than having the Office product close without any warning to the user. It doesn’t need to be more complicated than this. With that said, we don’t think this will be the last time we see changes on that front.

Prerequisites

  • SCCM Current branch v1706
    • Our upgrade guide here
  • Office client version
    • Same prerequisites as the previous version of SCCM Current Branch as stated in our previous post here

Manage Office 365 update SCCM 1706

On the server side, the biggest difference is that Office 365 client updates, no longer shows up under Software Library / Software Updates / All Software Updates

Manage Office 365 Update SCCM 1706

To see Office 365 clients updates, go to Software Library / Office 365 Client Management / Office 365 Updates

Manage Office 365 Update SCCM 1706

The deployment method remains the same. If you used Automatic deployment rules, they will still work.

Otherwise, when using a more manual approach, the same applies as any other Software Update, except you begin in the new Office 365 updates placeholder

Manage Office 365 Update SCCM 1706

Office 365 Naming convention

Microsoft announced earlier this year, that Office 365 would match Windows and SCCM semi-annual release (and naming)

Manage Office 365 Update SCCM 1706

Note that this change is not related to SCCM Current Branch 1706. You’ll see this naming also on previous SCCM version as it’s related to Office 365 client updates.

As per Microsoft, the naming change shouldn’t be applied until next January 2018, but clearly, it’s already here!

If you are using Automatic deployment rules for Office 365 client, double check your rule it if you were specifying a Channel.

Manage Office 365 Update SCCM 1706

More details can be found on Microsoft support page.

Office 365 updates end-user experience

SCCM 1706 should bring a better end-user experience.

Unfortunately, it doesn’t seem to work as advertised. We’ve done many tests and didn’t saw any kind of notice as it is supposed to be.

The worst part, it seems to bring back the auto-close / auto-open, of Office products when the deadline is reached, like it was with SCCM CB 1610, with no warning at all!

There is a bug report on Connect, feel free to up-vote and add to it if necessary.

Note
We will update the post when we’ll have more details about this issue

When Office 365 updates are deployed as available, a new warning show up stating that apps will be closed and re-opened as part of this installation.

Manage Office 365 Update SCCM 1706

For more details, see the Microsoft documentation page

Bonus information – Office 365 deployment tool

The Office deployment tool has been updated to reflect the latest naming changes.

You can get it on the Microsoft download page.

The new names also require changes to the configuration.xml file.

Manage Office 365 Update SCCM 1706

See all configuration.xml options on the Microsoft support page.

 

Share this Post

Contributor of System Center Dudes. Based in Montreal, Canada, Senior Microsoft SCCM consultant, working in the industry for more than 10 years. He developed a strong knowledge of SCCM and MDT to build automated OS deployment solution for clients, managed large and complexe environment, including Point of Sale (POS) related projects.

19 Comments on “Manage Office 365 Update using SCCM 1706”

  1. In 1602 there was a “feature” that prevented you from changing the channel of a client managed by CM. The channel set during installation was permanent. Has that been addressed in current versions?

  2. Hi Jonathan,

    Apologies if this is a little off topic.

    I have created an in place TS that will upgrade our Windows 10 1703 clients to 1803 and it seems to work quite well. During this upgrade i would like to also upgrade our Office 365 Client from 1705 Semi Annual to 1708 Annual Channel while keeping the users existing Office 365 set up.

    Our users generally have only the ProPlus installed, however we do have a few that have Visio and Project too. How can i do this during the TS. I have separate Application packages for ProPlus, Visio, Project and Access.

    Something along the lines of just applying the single update that will update all in the TS would be great.

    Hopefully what i have said makes sense

    Many thanks,

    Tony Bailey

  3. Hello Jonathan, any idea whether clients have to be upgraded to v1710 UR2 as well as the servers in order for the latest fix to work?

  4. Hi Jonathan,

    I hope you can help me because I am in need. I have successfully deployed Office 365 ProPlus C2R and it is working as designed. The device based activation is creating Azure device users and all works great…except updates. I am on SCCM 1706 and would like SCCM to deploy updates to my clients, but I feel like I am missing a vital step somewhere in my XML.

    I have been successful in updating from OCDN by removing my UpdatePath, but as I said, I don’t want to go out to Microsoft for updates. I have created an ADR which is downloading the update bits to a network share, but when I apply that UpdatePath to my XML, Office doesn’t think it needs an update. I am currently installing 16.0.8431.2153 in hopes to upgrade to 16.0.8431.2215 just to see if it works. As this is my first attempt and I am new to SCCM, it is entirely possible that my ADR is incorrect in some way, but I’m not sure how to discern if that is the case. All I want to do is deploy the Semi-Annual Targeted channel to a small group, the Semi-Annual channel to the rest of my organization and be able to update them accordingly. If you can be of any help with my multitude of problems, I would greatly appreciate it. Thanks for all you do on your site!

  5. How does this mechanism takes care about different languages? Do i need to download these updates for all languages I need and therefore multyply size?

    1. That is the impression I am getting. We use 10 different languages. It looks to me that that will require 10 ADR’s or 10 separate installs.

  6. Interestingly now with SCCM 1706 i seem to be back to teh old behaviour im not getting countdown timer when deadline set 7 days in advance and silent notifications in SCCM. I get the update now notification but no additional notification within 48 hours of deadline or the countdown timer within 7.5 hours. damn

  7. Pingback: Telemetría Office 365 – JoseMCT

  8. Marc-Andre and I just met with a bunch of people at Microsoft last week to discuss exactly this. I told them how unhappy i have been with SCCM patching for O365 and everyone seemed surprised that we were having issues like this. The issue we are having is exactly what you described in the section about how the end user experience was not improved in 1706 as promised.

    I guess we will just need to update our 6000 endpoints directly online with the monthly branch like Microsoft would want us to do.

  9. As an update to remain compliant with security patches when creating the ADR set the deployment deadline about 7 days and also create a new software update group each tine the adr finds new updates, can be as specific as you need with the criteria but i will break down each channel to have its own ADR.

  10. You wrote: SCCM 1706 should bring a better end-user experience.

    Unfortunately, it doesn’t seem to work as advertised. We’ve done many tests and didn’t saw any kind of notice as it is supposed to be.

    I would like to say that i experienced this at first and was rather annoyed but then i figured it out and you can see the dialog boxes and countdown timers etc

    Go back to this page
    https://docs.microsoft.com/en-us/sccm/sum/deploy-use/manage-office-365-proplus-updates

    Look for the important notice under Restart behavior and client notifications for Office 365 updates.

    The Trick is that you need it to be a required deployment and with a deadline about a week in advance, in any case as you approach the deadline the client will get notifications and countdown timers.

    I found that for our organisation what will work best is that we have the deadline 2 years in advance on the update group, the ADR should be very targeted so it only has teh lastes update to deploy.

    We use a GPO so that update notifications can appear, when the client downloads the update then the notification appears, in the Office Application bar it will say UPDATES AVAILABLE, although a required update, it will be up to the user to update on their own terms, the update completes in less than 30 seconds, the user should save their open files first before the press continue.

    For Monthly Channel that will work nicely

    For Semi-Annual Channel we will use a similar approach but because there could be up to 2 different versions of the channel supported at any stage when a version approaches its end of support we can set a deadline soon so that they will start to be prompted to update using the in-app notification on the taskbar and the countdown timers.

    This is working nicely

    1. Hi Christopher,

      thanks for your comment. I saw the Important Notice on Docs, but that was not up at the time of writing…which was still a couple months after 1706 release…

      Thanks for the details.. Note that enable the GPO is not part of the requirements, but I do think that might be needed.

      I’ll have more test and update the post if needed
      thanks
      Jonathan

  11. What happens if a workstation does not receive the O365 GPO? How will it then receive its updates? Will it go right to MS for the updates?

  12. Hi Jonathan,

    Can you kindly point me to any of your “Configuration Manager Service Manager” explanation posts? I searched but couldn’t find any. Thanks a ton!

  13. For required deployments, because of the new behavior (which they updated the documentation after we opened a premier support case) the best configuration appears to be required 7-10 days in the future, silent. The user will be notified via the ribbon in o365 and you don’t have to worry about the user closing their apps via software center.

    1. Hi Will,

      Thanks for letting us know about the documentation update.
      Seems Microsoft as updated the docs just 2 days before our post 🙂

      I’ll update the post accordingly
      Thanks
      Jonathan

    1. Yes you can by going back to using a gpo which configures the version number and the location of the version you want to push out, we had some of the challenges with the SCCM deployment and went back to using a gpo which targets a specific version and location, filtered by AD groups

Leave a Reply

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