The Office 365 updates behavior in SCCM 1802 still feels off and unpolished
We still see prompts for closing running office applications and while Software Center displays a reboot required, the update doesn't seem to get installed unless manually triggered through the in-app notification.
Agree with Martin and Keith, if officemgmtcom is in use than let SCCM handle the updates & notifications accordingly. This makes it impossible to stagger the content early before the deadline without avoid all of the C2R prompts.
Zeb Smith commented
Glad I'm not the only one. I was wondering if I'd done something wrong.
Benoit Lecours [MVP] commented
Office 365 updates should honour the notifications options set in the SCCM deployment (Hide all notification) and should include a new client setting for Auto-Close (forceappshutdown) and/or others parameter of Officec2rclient (if applicable)
Agree with all of below. We deploy OS and Office monthly updates at the same time. But with the Office In-App notifications it becomes a very inconsistent user experience.
I agree, we need a complete silent installation and intelligent enough to start installation when the apps are closed. We dont want any notification to end user about the maintenance IT configures on the systems.
We have update download issues for especially o365 and other updates are working fine.
Even we have case opened with MS and there is no solution as of now.
Martin Bengtsson commented
Ideally and if possible, I think many would want the old behavior back where we had no notifications from the C2R installer and no notifications in-app. Everything was handled through Software Center