Just a heads-up that David James re-opened this ask to finally fix it. See Twitter response below:
[image: Inline image 1] On Fri, Jan 19, 2018 at 8:20 AM, Miller, Todd <[email protected]> wrote: > I’m not having trouble getting the O365 patches to appear on my clients. > My trouble is the unacceptable user experience of how they are applied. > There should be no circumstance where ConfigMgr allows an O365 update to > close all Office applications without any messaging. The 1706 ConfigMgr > agent will do just that when applying O365 updates on any client where the > deadline for the O365 update is in the past. This would happen any time > that you turn on a computer that was not on for the 48 hours preceding the > patch deadline. > > I have professors that take laptops they use a couple of times a week to > go give a lecture on Friday and PowerPoint just closes in the middle of the > lecture because the deadline for the O365 patch was on Thursday and they > missed the short notification window since they last used the laptop the > previous Monday, > > I have 1/3 of our computers that are hot seat shared machines. The office > notification becomes like a hot potato. All the users ahead of the update > postpone the notice because they don’t want to be interrupted in their work > on the computer. Then whoever happens to be at the computer when the > deadline passes gets the update without warning and office apps are closed > right out from under them. > > The O365 update process as designed in ConfigMgr currently is only > acceptable in situations where there is a one to one relationship between > computer and user, and that computer is in use every day. Otherwise the > user of the computer at the time the update applies will just have the rug > pulled out from under them. > > I am working with premier on this issue, and so far we have found it is > working as designed and they calling it a product flaw -so trying to figure > out what to do, > > I am leaning towards abandoning O365 and switching to 2016 MSI. The C2R > O365 update process via ConfigMgr needs some rethinking, and the Office > 2016 patch process is the same as it has been for the last 10 years. > > Sent from my iPad > > On Jan 18, 2018, at 11:03 PM, Art Flores <[email protected]> wrote: > > I am planning to start next month in production, got it working in the > test lab using this link. > > > > https://blogs.technet.microsoft.com/askpfeplat/2017/ > 03/23/troubleshooting-office-365-proplus-patching-through- > system-center-configuration-manager/ > > > > *From:* [email protected] [mailto:listsadmin@lists. > myitforum.com <[email protected]>] *On Behalf Of *Miller, > Todd > *Sent:* Thursday, January 18, 2018 11:48 AM > *To:* [email protected] > *Subject:* [mssms] Office 365 updates basically impossible to deploy with > Configmgr > > > > Has anybody started deploying Office 365 updates via Configmgr? > > > > I am finding that they are *really* problematic. Updates seem to just > start applying without warning, and the update will close all the running > Office applications without notification. > > > > The user gets a notification if the update deadline is a couple of days in > the future, but once the deadline is past, the updates just start without > warning and the office apps just close. > > > > In many scenarios, the user will get no notification at all and office > apps will just close without warning. > > > > So a user fires up a laptop that has been off for a couple of days and > opens up Word and Outlook to start her day. Unbeknownst to the user a > patch deadline has past while here computer was off and the update starts > downloading. 10-15 minutes into her day, the email she was just about to > send is lost due to Outlook closing without warning. *And this is by > design…* > > > > There can be *many* instance where a computer comes into scope for an > office 365 update *after* the deadline for that update has passed. > > > > I started looking into this and much to my dismay, it is operating as > intended or at least designed. https://docs.microsoft.com/en-us/sccm/sum/ > deploy-use/manage-office-365-proplus-updates > > This is some kind of sick joke. How can an organization operate like > this? > > - A notification icon displays in the notification area on the task > bar for required apps where the deadline is within 48 hours in the future > and the update content has been downloaded. > - A countdown dialog displays for required apps where the deadline is > within 7.5 hours in the future and the update has been downloaded. The user > can postpone the countdown dialog up to three times before the deadline. > When postponed, the countdown displays again after two hours. If not > postponed, there is a 30-minute countdown and update gets installed when > the countdown expires. > - *A pop-up notification might not display until the user clicks the > icon in the notification area. In addition, if the notification area has > minimal space, the notification icon might not be visible unless the user > opens or expands the notification area.* > - The notification and countdown dialog could start while the user is > not actively working on the device, for example when the device is locked > overnight, so it’s possible Office apps running on the device could be > forced to close to install the update. Before closing the app, Office saves > app data to prevent data loss. > - *If the deadline is in the past or configured to start as soon as > possible, running Office apps might be forced to close without > notifications.* > - If the user installs an Office update before the deadline, > Configuration Manager verifies that the update is installed when the > deadline is reached. If the update is not detected on the device, the > update is installed. > - The in-app notification bar does not display on an Office app that > is running before the update is downloaded. After the update is downloaded, > the in-app notification displays only for newly opened apps. > - *For Office updates triggered by a service window or scheduled for > non-business hours, it's possible that running Office apps might be forced > to close to install the update without notifications.* > > > > > ------------------------------ > > Notice: This UI Health Care e-mail (including attachments) is covered by > the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521 and is > intended only for the use of the individual or entity to which it is > addressed, and may contain information that is privileged, confidential, > and exempt from disclosure under applicable law. If you are not the > intended recipient, any dissemination, distribution or copying of this > communication is strictly prohibited. If you have received this > communication in error, please notify the sender immediately and delete or > destroy all copies of the original message and attachments thereto. Email > sent to or from UI Health Care may be retained as required by law or > regulation. Thank you. > ------------------------------ > > > > > > ------------------------------ > Notice: This UI Health Care e-mail (including attachments) is covered by > the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521 and is > intended only for the use of the individual or entity to which it is > addressed, and may contain information that is privileged, confidential, > and exempt from disclosure under applicable law. If you are not the > intended recipient, any dissemination, distribution or copying of this > communication is strictly prohibited. If you have received this > communication in error, please notify the sender immediately and delete or > destroy all copies of the original message and attachments thereto. Email > sent to or from UI Health Care may be retained as required by law or > regulation. Thank you. > ------------------------------ > >
