Wants to get display notifcation message in clients to close any opened Office 365 apps while updates installation started
In SCCM 1610 users are not displaying notification message in clients to close any Office 365 opened apps before Office updates installation started in "Software Center" and even we set forceappshutdown=False switch in Configuration.xml file for Office 365
This is completed in ConfigMgr 1706 production release, publically available soon.
With 1802 getting the notification prompt to close the office app or to Postpone.
If postpone it will wait till 2 hours and close forcefully to install the update.Do we have control over the notification\pop window time control
Why is this still not fixed? It is unacceptable to force close Office applications without any notification! The users should ALWAYS get a warning that Office Apps need to be closed to apply the update, no matter how deadlines are configured.
Todd Miller commented
There are many instances where a client can come into scope for an update when the mandatory time is past due. In those cases, office will close without warning.
Take a professor who pulls out a laptop used once a week and takes it to present a lecture. She fires up the computer and launches Powerpoint. Because the Office 365 update became mandatory during the few days the computer was not being used, it starts downloading during the lecture silently barreling towards doomsday. 15 minutes into the lecture, Powerpoint closes without warning and with no indication of the cause. This is an entirely legitimate scenario and is unacceptable. You must warn users in all circumstances or mark the update to apply on reboot. It is entirely unacceptable to ever close an office application without warning under any circumstance.
It is definitely broken again, upgraded to 1706 last week an bam, all users get is a yellow banner staying an update is available and 5 mins later office just closes without any interaction being taken... for me it was during a Skype for Business call.. not good.
This is broken again in 1706, PLEASE FIX ASAP!!
This broken again in 1706. Deploying 365 updates as required forces all of your office applications to close without any warning. Only when advertised as available and manually installed do you get a software center notification about saving your work. We at least need it work the way that it did with 1702 where the updates respected the restart behavior in client settings.
This seems to behave properly for me in SCCM 1702. O365 updates are applied without force closing any apps, and Software Center prompts the user that a reboot is required to complete the update installation.
Please guys fix this ASAP, we are unable to roll out O365 client updates because of this!
Absolutely a needed feature. Having Skype close with no warning is detrimental.
Pete Nowacki commented
We really need this for folks who are getting their patches during production and for folks who don't finish patching during off hours.
Nick Augello commented
This is vital for customers who patch during production hours but also applies to customers who patch off hours.
The results are Skype meetings/calls being disconnected with out warning and all other office apps closing with out warning. This is an unacceptable design.
The current Cloud auto-updating process will prompted the user to upgrade in the app, if it is open.
Ari Piotrkowski commented
Unbelievable we have to do an "enhancement" request for this behavior. This needs to be fixed ASAP!
Don Pickard commented
We are experiencing the same issues since ConfigMgr 1610. We have opened a case, but it just has been archived: "[REG:117010615141652] ConfigMgr 1610 changed Forced Shutdown behavior O365 Updates".
This was the answer:
By design behavior for SCCM 1610 clients.
We have raised a DCR (Design Change Request) to Product Group in order to change this behavior in a future SCCM version release.
Please note that administratively a DCR is managed as a bug, meaning that all the time invested on this incident will be free of charge. (non-decremented from your contract with Microsoft)
You can also use the UserVoice platform to raise a request related to this subject. Product Group respond often to UserVoice’s requests: https://configurationmanager.uservoice.com/forums/300492-ideas/
If a fix is being found, the 1706 release is the first release where it possible will be available.
There is no nice workaround available, other than use the Application model to update the clients.
It worked for a few months perfectly, and now it's a nasty user experience where we cannot patch the product silently.
please need this feature to be added and fix with next SCCM release