Forum Discussion
Christopher Hadwin
Jan 12, 2018Copper Contributor
Office 365 Pro Plus - Closes All Office apps when updates are deployed
We are currently testing Office 365 Pro Plus in hopes to replace the Office 2016 MSI install. We have Office 365 Pro Plus deployed as follows :
<Configuration> <Add OfficeClientEdition="32" ...
Rob Fuller
Sep 17, 2019Copper Contributor
Christopher Hadwin has this been any development, we are experiencing the same issue effecting hundreds of clients.
Christopher Hadwin
Sep 17, 2019Copper Contributor
Rob Fuller, After bringing this to our SCCM DSE, he found that this was hardcoded within SCCM and was being changed in a newer build of SCCM. I believe 1806 or even 1810 might have included the change. Since then, we have not had any issues with Office Pro Plus clients force closing when updates are installed. It behaves very similarly to how the MSI version of Office behaves when installing updates.
update: the last couple of Office 365 patches delivered by SCCM provides a prompt that office applications need to close to apply updates. Once updates are finished applying, the office applications re-open.
- DaveGuenthnerSep 17, 2019
Microsoft
Christopher Hadwin and community, I recently blogged on this topic. It discusses end user behavior and workflow.. just scroll down to the SCCM section. If there is something you would like to see added, let me know and I'll update in FAQ
Understanding Office 365 ProPlus Updates for IT Pros (CDN vs SCCM)
- Rob FullerSep 17, 2019Copper ContributorThanks for the reply and I had a read of your blog post.
I'm delivering updates via the CDN however all my student users are complaining Office is closing without notice or warnings losing all there work. I've yet to see this behaviour myself but I've had many reports from teachers seeing the issue first hand.
What on earth could be causing this behaviour, I want to allow updates but unless I can control the behaviour I can't.
Any advice greatly received.- DaveGuenthnerSep 17, 2019
Microsoft
Rob Fuller A few suggestions:
1. If you suspect there is a custom script calling officec2rclient.exe out of band then use process monitor with filter for process name officec2rclient.exe + drop filtered events to monitor and trap the event to understand who the caller is and turn off the script.
Download latest ADMX
2. You can turn on "Delay downloading and installing updates for Office". This is basically N+Days from Patch Tuesday, for example 5. Roughly five days after build is released updates will be installed. Make the difference in days end up on a weekend.
3. You can turn on Update Deadline. Get buy in from customer on a maintenance window like weekend where installation will take place and users get series of notifications prior to change.
4. Integrate with SCCM with standard Software Update Workflow with restart notifications and so forth. Most customers I speak with include Windows and Office Updates in the same software deployment so there is a single reboot for maintenance window.
5. Make sure this is set or not present, can't be 1. This suppresses the bizbar notifying the user of pending change
HKLM\SOFTWARE\Policies\Microsoft\office\16.0\common\officeupdate
"hideupdatenotifications"=dword:00000000